yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] kenvan19:
Actually we don't know that it wasn't built to be on both. We know that the next version will merge a lot of the features of honeycomb and gingerbread but we have no idea what Google plans to do with honeycomb or what "features" will be merged. To say otherwise is to make assumptions and that is not something we should be doing. Nor should you be putting down people's development. A lot can be done with SDK.
[Nexus S Android Development] jonjon68:
Actually............ I love guys that get all defensive about someone's opinion and then spew complete BS info in response.

""Features will arrive on phones over time," a spokesperson said, but the operating system, for now, is designed specifically for tablets only."

http://www.mobileburn.com/news.jsp?Id=12764

I'd post multiple quotes and links but the point is made. Google it if you're still unsure.

It may very well make it here for phones. I hope not. My guess would be it would be a trainwreck.
[Nexus S Android Development] kenvan19:
Actually, I don't need to Google it. I read an article that makes the same form of speculation and hey look, I can quote articles too:

Source: http://www.engadget.com/2011/02/04/google-shows-off-fragments-api-for-android-3-0/

And here is the hint to which I believe that article is referring, taken directly from the Android Developers Blog:

Source: http://android-developers.blogspot.com/2011/02/android-30-fragments-api.html

So, as I stated previously, the important thing to note here is We don't have any clue what Google actually intends to happen with Honeycomb in regards to phones.

Not to mention, even your silly quote is completely ambiguous. It says

FOR NOW

meaning that at any point in the future following the exact moment the statement was made Honeycomb could be coming to phones. Its completely ridiculous how daft you are to tell me I'm wrong about the fact that we don't know the truth because someone said that at the moment it is on tablets only. Hey, that's funny because it is currently only released on a single tablet so extrapolating from there it is now only on tablets. Gosh that was tough.

Is your next plan to go to a religious forum and tell them that because there is currently no messiah named Jesus that clearly God doesn't exist? What other unknowns can you stamp out with unsound reasoning in just a paragraph of poorly researched text?

Frankly, what I actually love more than what you previously said is that in the case of indefinites people on these forums are always trying to prove that they are right without actually knowing the whole story and make completely idiotic assumptions about other people's knowledge of the situation which lead them to act like asses and generally make a fool of themselves over what was a completely innocuous comment whose sole purpose was the line

Nor should you be putting down people's development.

And turn it into a personal vendetta. It boggles my mind that someone would feel the need to come on the forums and without any rhyme, reason, or intelligence attack a completely harmless post that was on topic and defending the hard work of a developer.
[Nexus S Android Development] zephiK:
No one is putting down anybody's development. If they want to make a SDK port stable then thats them.

If its something a developer wants to pursue, then I'm happy for them. I'm just saying from another perspective that all of history in Android development, no developer has put the effort and time into making a SDK port a daily driver with full functionality. And the reason is because it's a SDK port. SDK ports are not meant to be a daily driver, its just there as a early preview on what to expect.

It's better off just waiting for "Ice Cream." What is there to Honeycomb that entices you to get it? Just because it's newer? "Ice Cream" is probably not too far away either.
[Nexus S Android Development] :
What this boils down to is gratuitous over posting, Kenvan your causing a lot of members to dislike you at XDA with your spurting of total c**p and showing a "know it all" attitude. JJ is right, its funny how lots and lots of people are having personal vendettas against you?

Maybe you should look closer to home....

I dont dislike you dude, but i think your need to post on every thread, like every other post, enables your maybe valid or not point to descend into BS.

JD;)
[Nexus S Android Development] :
I agree whole heartedly;)

JD;)
[Nexus S Android Development] :
Responses like this are the ones that command the utmost respect.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The truth is no one knows what the big G has prepared, but i have a feeling it will be great whatever they release;)

JD

Sent from my Google Nexus Magic Wand S
[Nexus S Android Development] kenvan19:
I could honestly care less what any random person on the internet thinks of me. I come to xda to find and discuss new and interesting software for my mobile device. Perhaps I missed the announcement that indicated that xda became a social network. If I did I really think a name change is in order; myxda, xdabook, xdaster, or maybe even xdain.

Regardless, the fact that you find it necessary to attempt to dishearten or insult me at every possible turn is ironically ending with you doing exactly what you accuse me of. In the most hilarious fit of irony yet you used a post where I stated that no one, myself included, knew the actual truth as evidence of me being a, as you say, "know it all".

@zehpik: the reason I'm so interested in honeycomb and it's related development here has nothing to do with newness and everything to do with curiousity. I see so many people saying why we can't have honeycomb but I find myself wondering we can't we have honeycomb. If I were a more intelligent man I would work my hardest to answer that question myself but as I've tried my hand at coding and found myself quite lacking in the necessary mindset I seem to be unable to do so.

I do, however see what you mean by the sdk port but I don't find myself bothered by not being able to use it as a daily driver.

Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
[Nexus S Android Development] :
How about xdatalknonsense?

You come to XDA trying to own this site and you fail. You need to understand 1. Your not a Mod so stop telling people what they can post and where. 2. Give people respect and they will respect you back. And 3. Over zealous posting doesnt make you an authority on Android, it just negates your credability.

I hope you take some of these points on board, but judging your character and past posts i think you wont.

XDA is for everyone, and everybody has a right to speak and push the community forward;)

JD

Sent from my Google Nexus Magic Wand S
[Nexus S Android Development] dogguns:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

agreed

guys please lets get this thread back on topic

A Honeycomb 3.0 Full sdk port sounds pretty cool :)
[Nexus S Android Development] :
It will be cooler when the source code is released and we can create a full working port;)

JD

Sent from my Google Nexus Magic Wand S
[Nexus S Android Development] Trinitronik:
And as I know, It happens, when XOOM will be released, right?
[Nexus S Android Development] mazodude:
xoom has been released
[Nexus S Android Development] DroidRC1:
This is what kmobs said on twitter today...

@kmobs:

We've been talking to someone that works on GoogleTV. Massive update to honeycomb based, Market, potential aosp merge in late may/early July
[Nexus S Android Development] :
Jesus,

So we will have to wait ages;( Probably forcing us to wait for Ice Cream;(

JD
[Nexus S Android Development] jroid:
The source would make this alot easier. Progress has been kinda slow, lots of help from steve who helped bypass with the N1 port. I'm still trying to get the egl libs called properly which has been a pain in the ass the way samsung has their libs setup for NS. Once i'm successfull I should have screen flickering and hw acceleration fixed.
[Nexus S Android Development] :
Thanks mate,

Look forward to your progress;)

JD

Sent from my Google Nexus Magic Wand S
[Nexus S Android Development] jroid:
made great progress tonight, finally found where system starts the binary needed to call the egl libs :) testing tomorrow after work
[Nexus S Android Development] ping33tx:
Great News

Great News and thanks for the hard work,look forward on running .
[Nexus S Android Development] leyvatron:
I'm really excited to use this without the flicker.....
[Nexus S Android Development] SwollenMonkey:
Sweet
[Nexus S Android Development] brrip:
this is really something to be excited about! whatever i've seen of honeycomb is so... maemo. loving it and waiting to experience it. big thanks to all the devs working to make this possible!
[Nexus S Android Development] jroid:
touch screen flickering has been fixed! however, now the color has borked to an amber :/
[Nexus S Android Development] Andrew421:
What's the difference between a tablet os and a phone os? The only thing i can see is the size of the screens and the processing power.
[Nexus S Android Development] nbeebe24:
Your amazing man! Wish I could contribute. I'm in the process of learning this stuff

Sent from my Sexus yeS
[Nexus S Android Development] bratfink:
Great news! Will you be posting the version with the flickering issue fixed soon?
[Nexus S Android Development] DJ_Steve:
i think hes waiting to post it for a bit as the colors are well off at moment and we are still working on fixing hw accell (im the steve he has referred to :)
[Nexus S Android Development] jaker.the.skater:
could you possibly post the version with the borked colors? I'm itching to mess around with some honeycomb!
[Nexus S Android Development] jroid:
Here's where we're at in progress.. Me and steve have discovered the egl issue is kernel related due to a driver, complaining saying that the driver is bad.Once we crack this, we're good on hw acceleration. Other issues are up in the air until we get this outta the way.
[Nexus S Android Development] kenvan19:
Well the first step is always to know the problem, and know whats causing it. Now all thats left is the most fun step which is figuring out how to stop whatever is causing it. :) Altogether though I'm just happy you guys have so much figured out! Seems to be moving at a great clip!
[Nexus S Android Development] ping33tx:
Keep it up :)

We are rooting for ya Keep up the great progress guys.:D
[Nexus S Android Development] bkfresh1:
Pun intended? Lol

keep up the good work
[Nexus S Android Development] Serious_Beans:
Can't wait until this is usable as a daily driver, awesome work so far!
[Nexus S Android Development] Trinitronik:
You know guys what I have discovered? Hardware buttons are also working! You can open search, settings, go home, by tapping the buttons below the screen!
[Nexus S Android Development] solrac.dc:
WOW

I'm REALLY liking the whole concept of making this operational for the NS. Really lookign forward to the Stable version!!!! :cool:
[Nexus S Android Development] jaker.the.skater:
darn... :( hopefully google will release it to help move this along faster.

http://gizmodo.com/#!5785466/google...from-the-public-over-user-experience-concerns
[Nexus S Android Development] zephiK:
You know the reason why they don't want to release it is because of reasons like this? Honeycomb on a phone.

Your post contradicted what the article said.
[Nexus S Android Development] jaker.the.skater:
ok well maybe some people want to mess around with honeycomb on their phone. I'm obviously not gonna use this as a daily driver but its fun to play around with. jeez.
[Nexus S Android Development] kenvan19:
I would try to use it as a daily driver. Definitely. I wouldn't care if it was awkward I would try to show it off as much as possible.
[Nexus S Android Development] jaker.the.skater:
well I would definitely try. if it could do what I need it to do then I would I guess haha
[Nexus S Android Development] Waza_Be:
I wish I could help....

I really hope you can go on and provide us something. Seem that Google doesn't want to help: http://thegadgets.net/technology-ne...o-android-honeycomb-source-code-indefinitely/
[Nexus S Android Development] ghost010:
you guy's might want to RE-read what google said.

they said honeycomb isnt ready yet(the honeycomb we saw can be marked as a BETA).not for phone nor tablet.

the source code will be released once honeycomb meets the wishes of google.
[Nexus S Android Development] :
So if its not ready, why are tablets being shipped with BETA software? And why are these tablets more expensive than the proven ipad line? Lots of questions have to be asked here...

JD

Sent from my Google Black Neolithic Slab Of Wonderment S
[Nexus S Android Development] Waza_Be:
SInce i got my HTC Hero nearly 2 years ago, I got use to try each SDK port to my device.

Developers are giving us the opportunity to try some stuff before the official release of the Source!

I don't understand why tht (maybe stupid) habit should change for Honeycomb.

We all know that will be buggy and unstable, but we don't care.

Let us have fun, please!
[Nexus S Android Development] adewey234:
I've been using on Android on my G1 since it was released (October 22, 2008). The original firmware that I was using on it was like android .9, it wasn't even the full Android 1.0. Now since you are so 'fond' of asking questions, why would T-Mobile, Google, or HTC release a phone that had beta software? The answer is simple, for money and development. Lucky for us all, people here actually develop these ROM's for free. Now if you don't want to be a part of the community, either by developing or at least helping the developers with bug reports or any sort of feedback, stop trolling and keep your useless opinions to yourself.

Now for the 'iPad' comment...I work @ Best Buy and to be completely honest, I see at least 3 iPads a day getting returned. The Zoom; I have only seen 1 to date, and that was from a customer who 'could not figure Andoid out.' Now if that isn't a clear enough sign of how consumers pick the devices that work best for them, I don't know what is. The Zoom is the first of many tablets that are going to form how Android is used and how much more versatile it is that anything Apple can concoct.

Back on topic...I love how far even this Alpha release has come, and I would certainly love to contribute once my computer is 100% set up for development again.

~adewey234

#Honeycomb #FTW
[Nexus S Android Development] BraydenJames:
How far the Alpha release has come? Are you talking about just the Alpha 1 release with the flickering screen? Or am I missing something here? I'm dying to provide test reports for this :) haha.
[Nexus S Android Development] jroid:
Update- it appears spacemoose from the honeycomb on galaxy tab port has gotten hw acceleration working. This is great news as I will be using this to build into this port and hopefully achieve the same results. How many of you are interested in a video of it running without flickering? I wanna get some more time in and fix rotation as well, day job is leaving me with no time weekdays for dev.

Sent from my Nexus S
[Nexus S Android Development] BraydenJames:
Instead of a video, you should give us an alpha 2 release to play with :)
[Nexus S Android Development] jaker.the.skater:
I second this :)
[Nexus S Android Development] kid1da:
Agreed

if the skies the limit, where's the urgency.
[Nexus S Android Development] :
Your the troll here pleb, I was just giving a point of view and a very real document of what kind of software we are dealing with. I have been beta testing since cm5 and designing and producing themes for the n1 nightly cm6 a few months back, What have you done for the community best buy boi? so kiss my behind pleb. And another thing, before you attack another member for speaking there opinion, find out their history on xda. You total idiot....

You being a best buy worker says it all...

Honeycomb is a beta device and really should not have been rushed, It will eventually be better than anything apple can offer, so we will just sit tight and wait;)

JD

Sent from my Google Black Neolithic Slab Of Wonderment S
[Nexus S Android Development] jroid:
Nothing other than the flickering has been fixed with the color being way off. Still want? I want no complaints about color..

Sent from my Nexus S
[Nexus S Android Development] :
WANT DUDE,

Colour problems are better than constant flickering;)

About time for a Alpha 2;P

JD
[Nexus S Android Development] jaker.the.skater:
color don't bother me. just want to mess around a little. bring it on!
[Nexus S Android Development] adewey234:
Lol, Ok now I am trolling. I work @ Geek Squad, and I've been developing ROM's since the beginning kid. Now shut up about looking @ peoples profiles because I've been a member since what, 2007. Yea, tongue my crack m8. Also, FYI Honeycomb is a revision of an OS, not a device. Also if you feel like looking @ my profile, you will see what I've posted and what I've done for the community. Or if you're feeling ambition you can utilize the search feature and look up Hero Revolution if you're ever perusing the G1 Developers forums...
[Nexus S Android Development] :
Ok so we both have done stuff for the community;) Just reign in your instant perception of posters as we are not all trolls. I made an observation that 3.0 is still in beta, and questioned that they should even release beta products, that does not make someone a troll.

Honeycomb in my belief should have been held back 6 months until they had everything right, I think Google rushed it out to take a bite out of the market before the impending release of the ipad2. While in the short term I think they have achieved this, it may be to the long term detriment, as first generation 3.0 users may get pissed with an unfinished feel to there OS. But I must say, even an unfinished 3.0 is miles better than an IOS4.x release...

JD

Sent from my Google Black Neolithic Slab Of Wonderment S
[Nexus S Android Development] :
Tongue my crack, lol... that's a new one on me, haha, that made me giggle;)

JD

Sent from my Google Black Neolithic Slab Of Wonderment S
[Nexus S Android Development] BraydenJames:
Thank you so much for the Alpha 2 release! It's really cool to play with it without the flickering. :). I can definitely see real potential in this! Thanks for your hard work :).
[Nexus S Android Development] Waza_Be:
jroid, is that possible to follow the progress you make on Twitter or an RSS feed?
[Nexus S Android Development] jroid:
I have a twitter but it's mostly personal, don't use it for dev purposes. All progress is posted here
[Nexus S Android Development] Waza_Be:
The problem with xda is that we have already 150 posts in this topic and your updates are lost in a feed of useless posts.

Reading the OP everyday is kinda useless too..

But btw, thank for your great work from Belgium!
[Nexus S Android Development] jroid:
Currently I'm still trying to get the driver working in order to call the egl libs to start. Spacemoose from the hc to galaxy tab port said I can use it, but I need his kernel source.
[Nexus S Android Development] adewey234:
Do you have the Graphic drivers for the NS, is that how you were able to solve the flickering? HW drivers for Honeycomb that is...
[Nexus S Android Development] jroid:
The hw libraries are merged in and are working correctly (lights, touchscreen, buttom keys) however the egl libs which are for the gpu aren't able to be called because the driver in the kernel is bad. Once I get that working, hw accel should be working as I have everything setup for it to init properly.

btw, flickering was fixed by pushing in gralloc.default.so from 2.3.3 however, idk what the problem with the color is.. if i push the lib from 2.3.2 it flickers but color is correct
[Nexus S Android Development] sloppy1:
every day is a step closer keep up the good work
[Nexus S Android Development] leyvatron:
Alllllright...... This is getting interesting.
[Nexus S Android Development] OuncE718:
Thank God. Your like the only dev who's actually working on a port for the NS. I hope you continue to bring us some more ports in the future.
[Nexus S Android Development] kenvan19:
Dude it looks great. Very nice work! Its of course not fully usable but I made a backup so I can hop over to it and play around lol

Sent from my MIUI Nexus S from the XDA Premium app.
[Nexus S Android Development] BrokenWall:
Too bad you can't merge in the Voodoo sound and color fixes into the kernel, then you can keep the new driver and we can manually change the color as we see fit for our needs.
[Nexus S Android Development] Zehlek:
I can't wait for a full release or at least stable
[Nexus S Android Development] twiztidhavok:
I just tried this rom and now for some reason I cannot boot into my bootloader to access my recovery and restore my previous rom. Any ideas on what might have gone wrong?

Thanks

EDIT: Nevermind, I figured it out.
[Nexus S Android Development] dario3040:
Its interesting, but clearly google didn't want honeycomb on phones, it might have worked out though.

Beside the wrong color hue its just kind of laggy.

But its funny anyway.

Hope there is more development on this in the near future
[Nexus S Android Development] jroid:
I can confidently say this won't go stable nor any of the hc to phone ports out there. Hc is for tablets, and after buying my xoom 2 weeks ago I can clearly understand Google. I just did this for fun and since nobody else did it I gave a shot at it. Andy Rubin said ice cream will get most of hc's features and UI which we can already see in the leaked Google music 3.0 app that works flawless on my ns. Furthermore, Andy said hc and ice cream source will get merged together before releasing the source, so getting hc to fully work on a phone is pointless. That's what ice cream is for. After fully knowing how the source code will be handled and what ice cream will be, I don't plan on really working on this much. I intended to hopefully get a full working port somehow when I first started, but now there's no ploint. So with that said, dev will halt for the most part. I'll still try fixing some stuff for fun but that's it. However, expect an ice cream rom built from source as soon as we get it, with some extras as always :D depending on what Google merges from hc to ic, I most likely will do a hc / ic fusion but we'll see. Thanks for all the kind words and support guys it was fun while it lasted.

Sent from my Nexus S
[Nexus S Android Development] dario3040:
Heh, so you are building a new rom after the source is released then.

Have you tried to port any sense or arc roms?

It could turn out pretty interesting.
[Nexus S Android Development] Azure465:
I would also much rather see a Sense port or something. That could actually be usefull :)
[Nexus S Android Development] dario3040:
Be nice, that sound kind of rude :o
[Nexus S Android Development] Waza_Be:
That sound kind of stupid...

If you prefer Sense, you have just to buy A HTC... Seriously, did you complain to your BMW dealer that you wanted a red Ferrari?

Porting Honeycomb is something that can be done in a better and cleaner way than a Sense port.
[Nexus S Android Development] Azure465:
ok sorry. but this is not very useful and he said himself that it never will be
[Nexus S Android Development] jroid:
I have no interest in other vendor UI ports to the nexus S. Yes it would be fun but, its more trouble than its worth. I stick with aosp. Waiting for ice cream.

Sent from my Nexus S
[Nexus S Android Development] dario3040:
Hmm, I don't really have any interest in that either, but some features they have are nice.

Like: Touchwiz has the codec support, HTC Sense has a ton of nice widgets and apps, and many smart solutions otherwise.

Those things might get ported though.
[Nexus S Android Development] j0hnZ:
Stupid analogy. If your against development, which you obviously are because you made a dumb ass post, then why are you in the development section. Go back to general where you belong so you can make everyone there dumber.