There is a semi working port of honeycomb for the g-tablet available from the below link. I looked through the threads and could find no mention of this.
http://rom-honeycomb-for-gtab-12.com/
brainyjd said:
There is a semi working port of honeycomb for the g-tablet available from the below link. I looked through the threads and could find no mention of this.
http://rom-honeycomb-for-gtab.com/
Click to expand...
Click to collapse
Most of the threads regarding this are in the G tablet General forum...
brainyjd said:
There is a semi working port of honeycomb for the g-tablet available from the below link. I looked through the threads and could find no mention of this.
http://rom-honeycomb-for-gtab-12.com/
Click to expand...
Click to collapse
You need to look harder.
The thing is, because its not being developed/released on xda its not mentioned in the Development section.
sorry - It makes sense that this is not in the dev thread
It makes sense that this is not in the dev thread but it is big news and I skim for new post every day in the dev section and did not see any. Sorry I wish I could delete this post.
brainyjd said:
There is a semi working port of honeycomb for the g-tablet available from the below link. I looked through the threads and could find no mention of this.
http://rom-honeycomb-for-gtab.com/
Click to expand...
Click to collapse
It's actually still in ALPHA not Beta
Not development. Moved to general.
It's here, and looks great but some features dont work.. still great
http://forum.xda-developers.com/showthread.php?t=1065220
theimpaler747 said:
Not development. Moved to general.
Click to expand...
Click to collapse
I'm curious about this since the project obviously IS development, but is being moved to General every time a thread references it.
Is this happening because Roebeet is now, for some reason no one has shared, persona non grata around here?
I mean, I guess it makes sense if he is no longer part of the XDA "family" but it still seems kind of silly.
I believe it is because the DEVELOPMENT is happening elsewhere.
Sent from my Xoom using Tapatalk
nunjabusiness said:
I'm curious about this since the project obviously IS development, but is being moved to General every time a thread references it.
Is this happening because Roebeet is now, for some reason no one has shared, persona non grata around here?
I mean, I guess it makes sense if he is no longer part of the XDA "family" but it still seems kind of silly.
Click to expand...
Click to collapse
It's not that at all..
Development is for the actual development of something and by the developer of that something, not the discussion of things being developed elsewhere regardless of who is developing it.
A good example.....CM7, the primary source tree for all Gingerbread built ROMs on the Gtablet is discussed in General as well because CyanogenMod is not posting their development and issues....it's others just talking about it.
The easiest way to think of it is that the development forum section is for a developer to post on their work and get feedback.
If it's not your work and you aren't doing the "developing" on it.....post it in General.
This really makes me want to punch whoever that drove roebeet away. Seriously, the guy is as dedicated as you can expect any dev who's doing this out of pure hobbyist enthusiasm.
The guy actually spent his valuable time to give us honeycream. Whoever that accused roebeet of any ill intention and effectively drove him away, shame on you. You should go and buy an ipad and leave us gtabbers alone.
When you think about it viewsonic made this all possible by releasing the 1.2 bl. In the end they have given us honey creams...
The honey comb port is from another device that uses a compatible or similar bl.
Roebeet is simply ironing out the gtab specific bugs. But therew are numerous bugs, so his work is much appreciated.
I definitely hate following the development on an outside site from xda. Because I love this community. But it is what it is.
Sent from my ADR6300 using Tapatalk
goodintentions said:
This really makes me want to punch whoever that drove roebeet away. Seriously, the guy is as dedicated as you can expect any dev who's doing this out of pure hobbyist enthusiasm.
The guy actually spent his valuable time to give us honeycream. Whoever that accused roebeet of any ill intention and effectively drove him away, shame on you. You should go and buy an ipad and leave us gtabbers alone.
Click to expand...
Click to collapse
Well said goodintentions !!
I don't agree with some of your posts,
but this one I can't agree more.
goodintentions said:
This really makes me want to punch whoever that drove roebeet away. Seriously, the guy is as dedicated as you can expect any dev who's doing this out of pure hobbyist enthusiasm.
The guy actually spent his valuable time to give us honeycream. Whoever that accused roebeet of any ill intention and effectively drove him away, shame on you. You should go and buy an ipad and leave us gtabbers alone.
Click to expand...
Click to collapse
You can find him on slate droid and he is working on honeycomb.
Last edited by jerdog; Today at 02:00 PM. Reason: Against XDA rules to direct traffic to another tablet/forum site
Click to expand...
Click to collapse
Really Jerdog?
I think you take this too far. Just being a jerk now.
I guess you will be removing all links to CM7 huh? Isn't that another tablet/phone/forum site? Those DEV's don't post/host their projects here.
I've never really taken sides in this little spat, but I think this is childish.
It's not like this is just one of many CM7 derivatives. It's the only bootable HC image I know of for the G-tab at this moment. Whatever flaws, issues, malfunctions it may have, many in these forums would like to play around.
This is an amazing rom for an alpha!
Sent from my GTablet-HC using Tapatalk
Zaphod-Beeblebrox said:
It's not like this is just one of many CM7 derivatives. It's the only bootable HC image I know of for the G-tab at this moment. Whatever flaws, issues, malfunctions it may have, many in these forums would like to play around.
Click to expand...
Click to collapse
Don't worry its all over the General section right now
XDA is merely reaping what some of its members/mods have planted (see: roebeet vs. XDA regarding 1.2 bl), and the more they continue to make a big issue about it the more the members will be trafficking and directing others traffic outside XDA.
Zaphod-Beeblebrox said:
It's the only bootable HC image I know of for the G-tab at this moment. Whatever flaws, issues, malfunctions it may have, many in these forums would like to play around.
Click to expand...
Click to collapse
Thats not the issue here (IMHO), the thing is , everyone who wants to try this ROM needs to load 1.2bl, this just proves that 1.2bl was the way to go (as suggested a month or two ago). The 1.1 <-> 1.2 switch just to try honeycomb will drive many users (at one point or another) to keep using the semi-backed, still alpha, HC release to avoid the overhead of the switch (especially given the rate of advances made in the HC port and bricking risk involved in jumping back and forth). Now all the current ROM developers (in clear contradiction to what XDA advocated) will need to either release 1.2 compatible ROMs or risk loss of interest.
Now all the current ROM developers (in clear contradiction to what XDA advocated) will need to either release 1.2 compatible ROMs or risk loss of interest.
Click to expand...
Click to collapse
I originally thought that they didn't want to do this becuase they will then have wasted all that time on the 1.1 Roms that are still in development...but then something dawned on me. Roebeet was able to port 3 existing Roms, all that he worked on, to 1.2. One based on TNT lite, one based on Gadam, and one (and probably best Rom I've ever used) based on Vegan. Keep in mind, he had all 3 of these up and running in about 2 days. He's actually been working on all of those, the HC port, and general 1.2 tools all at the same time. He's created direct and simple processes to flash to 1.2, a revised CWM for it, has Pershoot and Clemsyn on board with kernels.
Call me a fanboi, etc...but the man has really put in some major time on the 1.2 projects.
aasoror said:
Don't worry its all over the General section right now
XDA is merely reaping what some of its members/mods have planted (see: roebeet vs. XDA regarding 1.2 bl), and the more they continue to make a big issue about it the more the members will be trafficking and directing others traffic outside XDA.
Thats not the issue here (IMHO), the thing is , everyone who wants to try this ROM needs to load 1.2bl, this just proves that 1.2bl was the way to go (as suggested a month or two ago). The 1.1 <-> 1.2 switch just to try honeycomb will drive many users (at one point or another) to keep using the semi-backed, still alpha, HC release to avoid the overhead of the switch (especially given the rate of advances made in the HC port and bricking risk involved in jumping back and forth). Now all the current ROM developers (in clear contradiction to what XDA advocated) will need to either release 1.2 compatible ROMs or risk loss of interest.
Click to expand...
Click to collapse
TJEvans said:
I originally thought that they didn't want to do this becuase they will then have wasted all that time on the 1.1 Roms that are still in development...but then something dawned on me. Roebeet was able to port 3 existing Roms, all that he worked on, to 1.2. One based on TNT lite, one based on Gadam, and one (and probably best Rom I've ever used) based on Vegan. Keep in mind, he had all 3 of these up and running in about 2 days. He's actually been working on all of those, the HC port, and general 1.2 tools all at the same time. He's created direct and simple processes to flash to 1.2, a revised CWM for it, has Pershoot and Clemsyn on board with kernels.
Call me a fanboi, etc...but the man has really put in some major time on the 1.2 projects.
Click to expand...
Click to collapse
The whole 1.1/1.2 bootloader thing is stupid and melodramatic. There is little difference, and no real reason to use one vs the other. As builds from Malata get released, this will likely be a non-issue. sooner or later a 'standard' will emerge. Time takes care of this.
As for this 'overhead' between switching, its a fairly simple process to nvFlash. I think we forget that this is an enthusiasts and developers site. There are plenty of threads/articles explaining how to do it. This ain't Viewsonic Tech support. If you can't read these threads and learn how to do this, you really shouldn't be toying with the firmware to start with.
Zaphod-Beeblebrox said:
The whole 1.1/1.2 bootloader thing is stupid and melodramatic. There is little difference, and no real reason to use one vs the other. As builds from Malata get released, this will likely be a non-issue. sooner or later a 'standard' will emerge. Time takes care of this.
Click to expand...
Click to collapse
At the moment there is a few good reasons to use 1.2. The main one is HoneyComb . But it has been found that the 1.2 for the Adam is interchangeable with our 1.2. The adam developers have said they are working on a gingerbread release which means that 1.2 will be the way to get acceleration on a gingerbread rom.
Sure at the moment, if you don't feel like playing around with Honeycomb which is only partially working (I can't believe how much progress has been made in the last 2 days), there is no real reason to switch today. But, it looks like the best of what will come out in the near future is on 1.2 which can only be found on a different web site currently.
Related
SLOW THE %&*$ DOWN!
Just Kidding... but in all seriousness, the variety of roms for the Cappy is amazing. It all comes down to preference; however, I must say that with all of the updates, and new roms, I'm flashing at least twice a day and sometimes even losing track of what I'm running. (Although I know I'm currently running Andromeda and it is by far the best I've had on my Cappy. Awesome GPS lock in seconds, fast, stable.)
The point is... can we consolidate, or come up with a legit thread/wiki that clarifies the pros, cons, features, and specifications on roms. Reading 20 pages of forum after a new ROM is released is getting tiring.
Theodor911 said:
SLOW THE %&*$ DOWN!
Just Kidding... but in all seriousness, the variety of roms for the Cappy is amazing. It all comes down to preference; however, I must say that with all of the updates, and new roms, I'm flashing at least twice a day and sometimes even losing track of what I'm running. (Although I know I'm currently running Andromeda and it is by far the best I've had on my Cappy. Awesome GPS lock in seconds, fast, stable.)
The point is... can we consolidate, or come up with a legit thread/wiki that clarifies the pros, cons, features, and specifications on roms. Reading 20 pages of forum after a new ROM is released is getting tiring.
Click to expand...
Click to collapse
Well you shouldnt have posted in the DEV section.... See here
But since you have. Just be glad that we have all of them to chose from. Not long ago it was slow here. And no. That thread idea has never worked.....In all the time i have been here.
smokestack76 said:
Well you shouldnt have posted in the DEV section.... See here
But since you have. Just be glad that we have all of them to chose from. Not long ago it was slow here. And no. That thread idea has never worked.....In all the time i have been here.
Click to expand...
Click to collapse
I agree, it will never work. XDA is here for a reason. lets just keep doing what were doing. Also, where the hell have you been Smoke?
Theodor911 said:
SLOW THE %&*$ DOWN!
Just Kidding... but in all seriousness, the variety of roms for the Cappy is amazing. It all comes down to preference; however, I must say that with all of the updates, and new roms, I'm flashing at least twice a day and sometimes even losing track of what I'm running. (Although I know I'm currently running Andromeda and it is by far the best I've had on my Cappy. Awesome GPS lock in seconds, fast, stable.)
The point is... can we consolidate, or come up with a legit thread/wiki that clarifies the pros, cons, features, and specifications on roms. Reading 20 pages of forum after a new ROM is released is getting tiring.
Click to expand...
Click to collapse
If you look at the feature sets, most of them are the same, just different skins, apps, etc included...
everything is pretty common knowledge since we are all running the same mods... additional apps, skins, etc are just fluff, which is why I personally don't include that kinda stuff. I will leave that to the theme and app section and the person running the rom to make it look how they want.
as far as all of us working together, I respond to all the devs who ask for help, I have joined up and help the team efforts, as well as individuals putting roms out that have asked how to do various things.
Putting it all into a wiki? No thanks, that stuff changes to much to want to deal with updating a wiki with 20 different variations on how to do a smali edit for X feature.
If you take donations, in a community based team, this always becomes a stress point, best not to take donations at that point. I won't accept a cut of team donations, someone will ***** about it if they get less or more, not worth it. (just noticed adam sent me a donation, KNOCK THAT OFF! lol)
As far as you not liking to flash a lot, get help, you are a flash addict
I wont be slowing down anytime soon, get used to it
/random thoughts
designgears said:
If you look at the feature sets, most of them are the same, just different skins, apps, etc included...
everything is pretty common knowledge since we are all running the same mods... additional apps, skins, etc are just fluff, which is why I personally don't include that kinda stuff. I will leave that to the theme and app section and the person running the rom to make it look how they want.
as far as all of us working together, I respond to all the devs who ask for help, I have joined up and help the team efforts, as well as individuals putting roms out that have asked how to do various things.
Putting it all into a wiki? No thanks, that stuff changes to much to want to deal with updating a wiki with 20 different variations on how to do a smali edit for X feature.
If you take donations, in a community based team, this always becomes a stress point, best not to take donations at that point. I won't accept a cut of team donations, someone will ***** about it if they get less or more, not worth it. (just noticed adam sent me a donation, KNOCK THAT OFF! lol)
As far as you not liking to flash a lot, get help, you are a flash addict
I wont be slowing down anytime soon, get used to it
/random thoughts
Click to expand...
Click to collapse
I feel the same. So many roms are including everything everyone else is. Just skinning and a few differences. I stick to a select few toms and just go frombthere because there is just too much to keep track of right now.
DG you are an idol of a great developer.
It would be great if more.devastating would get together to lighten the load and make it a little easier on all involved, but then again I am excited to.see so.many great revs making a rom all their own.
Sent from my SAMSUNG-SGH-I897 using XDA App
I think its just crazy that this thread even got other post
I would have thought it was over with mine. But oh well. I have been in the shadows adam
Im always here. Or kinda.... haha
i think a wiki would be convenient in some ways but more trouble than its worth. I mean who would wanna volunteer to keep up with every single rom, and update it daily?
It might help a lil with noobs trying to learn, but honestly reading through 100s of pages in one thread usually ends up helping you learn more than just the rom itself. When i first registered on this forum all i did was read for the first few months before even making a post
Guess I will jump on the bandwagon before this gets moved to the general section.
There was a point in time not so long ago where there were only about 3 ROMs for the captivate and a lot of drooling over what the other SGS variants had going on.
I for one am very happy to see the Captivate community grow and put out some good stuff. The variety and choices really help enable the end-user to get their phone to look and work how they want, end-user empowerment tends to make people happy.
Taco Bell has maybe a dozen individual ingredients but it's the way they are combined that makes each product special.
As for having to read the threads of each ROM, yea it can be a pain, but it is good for you. You are informed, can make the best choice, and know what to expect from what you are about to put on your phone.
designgears said:
If you look at the feature sets, most of them are the same, just different skins, apps, etc included...
everything is pretty common knowledge since we are all running the same mods... additional apps, skins, etc are just fluff, which is why I personally don't include that kinda stuff. I will leave that to the theme and app section and the person running the rom to make it look how they want.
as far as all of us working together, I respond to all the devs who ask for help, I have joined up and help the team efforts, as well as individuals putting roms out that have asked how to do various things.
Putting it all into a wiki? No thanks, that stuff changes to much to want to deal with updating a wiki with 20 different variations on how to do a smali edit for X feature.
If you take donations, in a community based team, this always becomes a stress point, best not to take donations at that point. I won't accept a cut of team donations, someone will ***** about it if they get less or more, not worth it. (just noticed adam sent me a donation, KNOCK THAT OFF! lol)
As far as you not liking to flash a lot, get help, you are a flash addict
I wont be slowing down anytime soon, get used to it
/random thoughts
Click to expand...
Click to collapse
The note you made about the themes and such is exactly why I love Andromeda. I personally do not like the 2.0 theme, but the fact that there is an unthemed version as well as a themed version makes me the happiest panda in the world, and I think more ROM cookers should adopt this policy.
What I'd love more than anything else though, is a ROM that supports the hardware voice processing of the Captivate, as well as any custom kernels/modems the user wants. That would be the ultimate ROM in my opinion. Oh, and the 4 lockscreen mod is a must as well. I do not like the glass lockscreen
chrisz5z said:
i think a wiki would be convenient in some ways but more trouble than its worth. I mean who would wanna volunteer to keep up with every single rom, and update it daily?
Click to expand...
Click to collapse
FYI-
Captivate Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897
Looks like it is not too far out of date.
People complain too much....
I understand your post OP but as mentioned it won't work. What get's the me the most is when people ask, "what's changed?"...
There are CHANGE LOGS ON EVERY THREAD FOR EVERY ROM.
xcaliburinhand said:
FYI-
Captivate Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897
Looks like it is not too far out of date.
Click to expand...
Click to collapse
maybe i interpreted the OP wrong, but it sounds like hes talking about a wiki with more detail than the one we already have
xcaliburinhand said:
Taco Bell has maybe a dozen individual ingredients but it's the way they are combined that makes each product special.
Click to expand...
Click to collapse
Taco Bell.. I'm hungry.
It really cracks me up that this thread is still going
Every ROM is made for a handfull of people. AS it seems. So to really make a wiki and save all the Info from a few thousand users is just nutz. even to have a WiKi just for the ROMs is kinda nutz as others have said. Just so much changes daily it would be so hard to keep up with
So i guess....Like all the others. We can let this thread die now
I agree with you Smoke. With the way updates come out sometimes daily for fixes or depending on an issues hourly a Wiki would just be too hard to maintain. If some one is up for it then go for it. I just see it as a way for people not to have to read the roms thread and doing research before they flash a rom to their $500 device.
Thread closed
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.
So does this mean that the devs will be able to strip honeycomb out of the xoom easily for us g-tabers?
http://www.droid-life.com/2011/02/2...ckablerelockable-bootloader-for-development/#
That would be my assumption. Great news!
Edit:
I just saw that announcement as well. Seems like good news. I'm a little shocked honestly.
Sent from my HTC Glacier using Tapatalk
I'm sure its only a matter of time before someone yells at us for talking about honeycomb in a forum, but I too am curious about that. I know that Roebeet was answering some questions on another honeycomb thread, which I really appreciate. Seems to me, now that honeycomb is right around the corner, that some discussion about what must be done to get honeycomb on our g tabs would be useful.
Is anyone who checks this forum getting a Xoom? It would be great if a developer could let us know what might be needed from a xoom to begin work on a gtab honeycomb rom (if it is even possible). Im much more hopeful now after learning about the unlockable bootloader. I'm not asking for honeycomb tomorrow by any means, but am very curious about what steps would need to be taken to get honeycomb on the gtab. Thanks for any help!
Guys, our dev community here is one of the best. Roebeet and Rothnic are already active on the Xoom forum and inquiring/waiting/stalking for a system rom dump. ..gotta luv 'em.
See here for the Xoom forum on xda
When you start seeing threads about roms and the like on those forums, Honeycomb for the Gtab won't be far behind.
Thanks for the update!
atakapa said:
Guys, our dev community here is one of the best. Roebeet and Rothnic are already active on the Xoom forum and inquiring/waiting/stalking for a system rom dump. ..gotta luv 'em.
See here for the Xoom forum on xda
When you start seeing threads about roms and the like on those forums, Honeycomb for the Gtab won't be far behind.
Click to expand...
Click to collapse
Thanks for the info. Maybe a mod should post a sticky like your post to cut down on honeycomb threads.
Thanks again \oo/
Sent from my Froyo Leak...thanks Kaos \00/
neo4uo said:
Thanks for the info. Maybe a mod should post a sticky like your post to cut down on honeycomb threads.
Thanks again \oo/
Sent from my Froyo Leak...thanks Kaos \00/
Click to expand...
Click to collapse
Exactly what I was thinking. If anyone in the know could explain whats the approximate timeline for Google's releases of AOSP in relation to the release of flagship device with the corresponding update.
cjackxiii said:
Exactly what I was thinking. If anyone in the know could explain whats the approximate time line for Google's releases of AOSP in relation to the release of flagship device with the corresponding update.
Click to expand...
Click to collapse
Read in another post here that Google has 30 days from the release of the first device running an OS before they have to release it to AOSP. again this is from a post I read and can't locate at the moment (too many Where's honeycomb threads to deal with looking through) so take it for what its worth.
Even so, would you like a rom that is a port of another device or a rom built from source using the same version of android?
I say our very own honeycomb will do!
brutusbucknuts said:
I'm sure its only a matter of time before someone yells at us for talking about honeycomb in a forum, but I too am curious about that. I know that Roebeet was answering some questions on another honeycomb thread, which I really appreciate. Seems to me, now that honeycomb is right around the corner, that some discussion about what must be done to get honeycomb on our g tabs would be useful.
Is anyone who checks this forum getting a Xoom? It would be great if a developer could let us know what might be needed from a xoom to begin work on a gtab honeycomb rom (if it is even possible). Im much more hopeful now after learning about the unlockable bootloader. I'm not asking for honeycomb tomorrow by any means, but am very curious about what steps would need to be taken to get honeycomb on the gtab. Thanks for any help!
Click to expand...
Click to collapse
I'm getting a xoom tomorrow and i'm pretty adventurous so if there's anything I can do to help just let me know.
Legacy2385 said:
I'm getting a xoom tomorrow and i'm pretty adventurous so if there's anything I can do to help just let me know.
Click to expand...
Click to collapse
I am also getting a Xoom tomorrow but definitely not throwing out the gtablet as it is one of the best learning development tools I have owned. I will probably be a bit more cautious with the xoom out of the gate just because of the cost, but guaranteed I will be testing Honeycomb ROMS on the gtablet as soon as they are available.
I don't care what kind of flaming I get from this blah blah blah, yada yada yada
Ummmm.......team eos is Roach2010 (plus some others)
Strange person
Is the droid in your avatar breakdancing or did he trip up and land on his head??
scottyf79 said:
Ummmm.......team eos is Roach2010 (plus some others)
Strange person
Click to expand...
Click to collapse
I'm not strange, I am sick and tired of wiping and installing some wanna be rom and have my tf101 reboot every single time the Wireless tries to startup. Testing is key when releasing something you hope others will use...and that is just not being done.
TeamEOS is not Roach2010...he only just starting developing with them. Until I seem a full on, tested, release from them with his Stamp of Approval. I won't believe it.
All the others are amateurs, noobs, and don't bother testing on every model or documenting the fact that they only tested on model a, model b, or model c.
I tried all of the AOSP roms yesterday and none of them had any issues with wifi. They all had excellent stability. But my TF is B70 sbk 1.
gVibeR said:
All the others are amateurs, noobs, and don't bother testing on every model or documenting the fact that they only tested on model a, model b, or model c.
Click to expand...
Click to collapse
Develop your own then, or quit complaining. You flash these at your own risk, even a thoroughly tested ROM can brick your particular device..also, how do you think the devs TEST these on every device type? They release it here so WE can HELP by reporting bugs back to them and then they FIX them. ICS has been out for barely a month, and the STOCK ICS is full of bugs as it is, why do you expect devs who do it on their own time to be any better than Asus is when they are a corporation?? Wow that was a disrespectful post...
horndroid said:
I tried all of the AOSP roms yesterday and none of them had any issues with wifi. They all had excellent stability. But my TF is B70 sbk 1.
Click to expand...
Click to collapse
Thats super great and I am very happy for you. That doesn't help me. I have a B60, and none of them work on it. My main complaint is that none of the devs bother to report which models their rom is tested on.
They are such noobs that they just compile and release and claim the blanket "oh we are not responsible for .... " crap. When they are responsible when they don't document which models they have tested on. They are responsible when they don't give all possible information to people so they can make educated decisions.
This I am not responsible crap is just a way of saying I may or may not be a ****ty developer, and if you find out I suck...its not my problem.
Its no wonder so many people flock to XDA and other site and beg for donations...because they could never make it in the real world as a developer where making quality software was how they eat and pay bills.
I think XDA should vet any developer before just letting them on the forums to release whatever. Sorry, but with all the phone/tablets out there...the room for crappy devs is just growing. Now is the time to start qualifying people.
Anyway...who cares right. "Oh mine works" sorry yours doesn't!
So you expect all of the devs to have every available hardware versions of TF101? That's ridiculous. Maybe send them your TF if you want them to test their ROMs on it?
They do this for FREE. If the ROMs don't work for you, too bad. Not sure how you can complain about something that is completely free. No one is forcing you to use the ROMs.
Think this thread is just to create drama.........
If the op had a sensible case to argue then it would be interesting.
Like its been said before - i have a b40 and ive tried them all with no issues - so theres a 40 & 70 tried and tested........maybe porking the micro sd slot isnt doing your tf any favours.
Going to test out the ignore feature again bet it works as well.
Thread needs binned.......its even in the wrong sub section
horndroid said:
So you expect all of the devs to have every available hardware versions of TF101? That's ridiculous. Maybe send them your TF if you want them to test their ROMs on it?
They do this for FREE. If the ROMs don't work for you, too bad. Not sure how you can complain about something that is completely free. No one is forcing you to use the ROMs.
Click to expand...
Click to collapse
Exactly. It's just a hobby for most developers, and none force you to use them. Get another tablet if you're seriously going to complain about the developers work you choose to use.
I've tried AOKP, CM9, Revolver, and Android Revolution, and other than flashing non-stock overclock kernels (which don't work with wifi, apparently) I've had no more problems than stock ICS (Sleep of Death, etc etc)
Also, where is OP's magic ROM that works on every version of the TF101, TF101G, and SL101??? I'd love to give it a shot!
gVibeR said:
This I am not responsible crap is just a way of saying I may or may not be a ****ty developer.
Click to expand...
Click to collapse
I say again, if it's so easy, why are you even flashing ROMs other people made..make your own and shut up.
gVibeR said:
I think XDA should vet any developer before just letting them on the forums to release whatever. Sorry, but with all the phone/tablets out there...the room for crappy devs is just growing.
Click to expand...
Click to collapse
First point, they are called 'recognized developers'. Don't download anything that isn't from a recognized developer..sounds like a failure on your part there..
Second point..crappy devs = every dev when they start. It's called a learning curve. This is where we learn. You want polished software, stick with a stock ROM. They have the money to put into PAYING developers to FIX EVERY SINGLE BUG before they release it, oh, and they also EMPLOY BUG TESTERS..
Get off your soapbox. And close this thread already..you are wrong, and being rude. XDA isn't for you, that's obvious. Stick with stock ROMs and you will be happy (LMAO).
So if youre so much better than all the current rom devs, why dont you cook up a completely bugfree rom, tested on all TF models, in your free time, without getting paid?
If asus themselves, who have the resources and hired coders, cant sort out the random reboot issue, why the hell do you expect a group of enthusiast, who code in their spare time mostly for fun, to magically sort it out?
Get down to earth and get a grip on how coding works before flaming.
i normally wouldn't bother giving such post a thought. but its ridiculous to be complaining about something you are getting for free. these devs put in TIME and EFFORT to make something. SO what if there are bugs here and there. almost every piece of software out there has bugs. even the paid ones. And its certainly not an easy task to test every combination of a software.
Yes it can be frustrating having a ROM give you so many issues. But unless you are going to hire them as your personal programmer dont complain. or maybe give up some of your own time to read through their source code and help find the bugs.
XDA is a forum where people HELP one another. We know what it means to have an OPEN environment. We should be appreciative that there are devs willing to make ROMs for our devices and SHARING it with everyone.
off course your solution is to sell your TF and get an iCrap
gVibeR said:
I don't care what kind of flaming I get from this, but I am just sick and tired of taking a chance on the current list of developers for the TF101 only to find that my pad ends up in a continuous boot loop with constant Wireless module issues.
I think that if you haven't tested your rom on every possible model of transformer that you should note that, and make it very clear that anyone with a model not tested should take caution.
Yes..I am talking to you sportstart89, ricardopvz, teameos, timbit123, and whoever else thinks that by just compiling a rom, adding Superuser is all it takes to make it in this scene.
I have tried all of them on my B60 transformer...and every last one of them has a crashing Wireless with constant reboot loop.
THE ONLY ROM THAT IS STABLE ON MY PAD IS STOCK WITH VIPERMOD ROOT.
I'm done with all you amateurs.
I want my Roach2010 back!!
Click to expand...
Click to collapse
Yeah, and we all know how stable YOUR ROM is, huh? Oh wait, you haven't released a ROM, have you??
Hmm, there is a thought- create the 'perfect' ROM yourself if it's so easy!
Unbelievable.... I cannot believe how un-appreciative and immature some of the people are around here!
gVibeR said:
I don't care what kind of flaming I get from this, but I am just sick and tired of taking a chance on the current list of developers for the TF101 only to find that my pad ends up in a continuous boot loop with constant Wireless module issues.
I think that if you haven't tested your rom on every possible model of transformer that you should note that, and make it very clear that anyone with a model not tested should take caution.
Yes..I am talking to you sportstart89, ricardopvz, teameos, timbit123, and whoever else thinks that by just compiling a rom, adding Superuser is all it takes to make it in this scene.
I have tried all of them on my B60 transformer...and every last one of them has a crashing Wireless with constant reboot loop.
THE ONLY ROM THAT IS STABLE ON MY PAD IS STOCK WITH VIPERMOD ROOT.
I'm done with all you amateurs.
I want my Roach2010 back!!
Click to expand...
Click to collapse
Hi there I own a B60 and have 3 different roms that will work on it and 1 that has no reboots at all also found an oc kernel that is playing nicely for now.
You can't put issues down to what model you have if the same car is manufactured 5 years in a row not to much is gonna change and base parts can usually be swapped.
I mean I have the same model as you but I may just be able to tweak a rom to work on mine where on yours it has issues or visa versa.
You seem to forget that icys is new and that even completely stock TF101 icys has issues at the moment. I think if anything the devs here are trying to find solutions and actively working quicker than the Asus company themselves also they dont have to go through all the stuff Asus has to to get an update out. Most of the devs here have done great work and have continued to support and develop from honeycomb they could of just left when icys arrived. I mean some are new but a few are not and are well respected.
1st You have a B60 tried a clean NVflash ?
2nd With your wireless are you using the right kernel on the right Rom? Are you doing things correctly?
3rd If its just compile and done do you think cm9 would be making progress?? Do you think modified stock would be as quick or have etc?
4th Kernels are not exactly an easy thing to build or improve on so you cant expect rock solid with everything at the moment its to early!!!!!!
5th Most of these guys have day jobs or university the fact they even do this is huge!!!!!!!!!!!!!!!!!!!!!!!!!
I think maybe you should calm down have a rethink and suss it out or ask for help or maybe move away from custom and rethink what hardware/software you want to use
Sorry for the long post guys but had to answer such an insulting set of comments
Sent from my Transformer TF101 using XDA Premium HD app
Hah everyone and their mom taking a shot at the OP because he made it just too easy and irresistible. This could be a very subtle troll.
This is just rude and obnoxious!
This is basically a devoper site. They make it, you test it.
And get your facts straight! There's an issue in the kernel that not everyone experiences. The source is out and people are trying to pin down the reboot issues.
If ya don't like to test and contribute to finding the issue, then go to some other site and whine there. Make your own damn kernel from the source and find the issue yourself!
Sent from my SGH-T959 using xda premium
IT IS OVER/UNDER time.
I say this thread will be closed by 2:00pm (14:00)pm US Eastern time.
NOW Go!!!!!
Woodrube said:
I say this thread will be closed by 2:00pm (14:00)pm US Eastern time.
NOW Go!!!!!
Click to expand...
Click to collapse
You lose. It's closed now.
gVibeR said:
I don't care what kind of flaming I get from this, but I am just sick and tired of taking a chance on the current list of developers for the TF101 only to find that my pad ends up in a continuous boot loop with constant Wireless module issues.
I think that if you haven't tested your rom on every possible model of transformer that you should note that, and make it very clear that anyone with a model not tested should take caution.
Yes..I am talking to you sportstart89, ricardopvz, teameos, timbit123, and whoever else thinks that by just compiling a rom, adding Superuser is all it takes to make it in this scene.
I have tried all of them on my B60 transformer...and every last one of them has a crashing Wireless with constant reboot loop.
THE ONLY ROM THAT IS STABLE ON MY PAD IS STOCK WITH VIPERMOD ROOT.
I'm done with all you amateurs.
I want my Roach2010 back!!
Click to expand...
Click to collapse
Blasting people who do what you are seemingly unable to do is wrong, and does not belong at XDA. We exist for the developers, and if you don't want to provide a decent amount of respect, you can leave.
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!