Yes, please. (Honeycomb) - Nook Color General

Honeycomb SDK preview is out
http://www.engadget.com/2011/01/26/android-3-0-honeycomb-sdk-preview-goes-live/

Amen to that. You know - i ahve seen other phones have semi-working rom builds created from the SDK images. I am sure its just a pip dream, but damn it would be sweet if we could be working on honeycomb now....

it's possible to extract a image, but then it would be slow as hell.
not worth the trouble porting it

cainhunpi said:
it's possible to extract a image, but then it would be slow as hell.
not worth the trouble porting it
Click to expand...
Click to collapse
I dunno.. doubt it would be slower than Froyo on an SD card.

I made a zombie out of the honeycomb preview and one of the nook kernels.
Touch input doesn't work, no hardware acceleration etc.

Well then get to work dblue.....
From the nookCOLOR

If we can get the Nook Color running gingerbread that would beyond awesome, honeycomb and I might just piss myself.
Sent from my LogicPD Zoom2 using XDA App

deeper-blue said:
I made a zombie out of the honeycomb preview and one of the nook kernels.
Touch input doesn't work, no hardware acceleration etc.
Click to expand...
Click to collapse
I love it (and thanks for trying exactly what i was thinking of)! Sure, it isn't fully working, but it provides a TON of hope that with some work, Honeycomb can be made to work.

Once the source code is on AOSP then getting working ROMs for other platforms should be much easier. I think one of the problems we might see is driver support since the underlying kernel for Honeycomb might be different.

It does indeed run very slow so far.
Touchscreen is working now. I'll try to get the graphics acceleration running over the weekend that should help with performance.
(and I think it's stupid that I can't post or reply in the development forum without having more than 10 posts.)

deeper-blue said:
It does indeed run very slow so far.
Touchscreen is working now. I'll try to get the graphics acceleration running over the weekend that should help with performance.
(and I think it's stupid that I can't post or reply in the development forum without having more than 10 posts.)
Click to expand...
Click to collapse
If you get a bootable SD card out of this, you'd become a legend on these forums (At least in my eyes)
If you don't, you still get huge respect for getting this working on your device.

deeper-blue said:
(and I think it's stupid that I can't post or reply in the development forum without having more than 10 posts.)
Click to expand...
Click to collapse
It is an effort to keep people from finding out about XDA on yahoo or something and then coming here and going into the dev section saying make it work for me...NOW!!
Which sadly happens a great deal. Seen it many times in my years around here.
I'm sure that you will appreciate it when you have less of that to deal with when you hit another few posts and can start your first thread in the dev section.
You obviously have something to contribute so just post replies to a few posts in the general section here and you will be on your way.
Looking forward to the work you have started!!

Agreed - please keep up your work, and hit up the dev section after 10 posts. I would LOVE to see work progress on honeycomb!

Awesome. I may be wrong but isn't this the first HC port?

unknownrebelx said:
Awesome. I may be wrong but isn't this the first HC port?
Click to expand...
Click to collapse
I would call it a port. but yes. first hardware to run it

Congrats! You made Engadget!
http://www.engadget.com/2011/01/28/nook-color-earns-its-very-eary-very-unofficial-android-3-0-hone/

Deeper-Blue. hit up 10 posts and start a post on the Development forum. Gived us the code u got and we can help each other

Divine_Madcat said:
Congrats! You made Engadget!
http://www.engadget.com/2011/01/28/nook-color-earns-its-very-eary-very-unofficial-android-3-0-hone/
Click to expand...
Click to collapse
Job in 3, 2 , 1
Done. He is already working for an OEM

Damn, makes me regret returning my NC. Awesome job!
Sent from my EVO using XDA App

Amazing. The OEM still hasn't released Froyo and there are devs working Froyo, Ubuntu, and now Honeycomb. I didn't see Gingerbread, but I bet that has been done as well! Congrats!

Related

Is anyone working on getting Read to Me to work?

I have Gingerbread working nicely thanks to this wonderful forum, but sadly I am scared that my kids will kill me without the Read to Me option. Is anyone working on this?
not that i'm aware of. there are lots of folks on xda that want the B&N stock apps to be ported, but i haven't seen that anyone is actively working on them.
thanks was just reaching out to find out so I could have an idea, would be nice though. Thanks again for the info.
buffalosolja42 said:
thanks was just reaching out to find out so I could have an idea, would be nice though. Thanks again for the info.
Click to expand...
Click to collapse
There are two problems facing us:
1) The Nook app is not open source, so B&N can slap us around with a cease and desist, if devs go posting a modified version of it. This is the same reason that all the other non stock OS builds modified the boot image.. it's B&N's.
2) Even if that weren't a problem, the special nook app relies on the heavily modified framework of their Eclair build. So, while it is not impossible, it is unruly, and combined with #1, doesn't make for a project worth undertaking..

Alright need community's help. Need some kernel work and driver modification.update!

If you guys follow dj-steve on twitter then you will know he got honeycomb to boot on the s7. Great news. But to get it stable we need too have the kernel ported too 2.6.36. And maybe have the touch driver modified if that wasn't addressed in 2.6.36.
If you guys can ask around and see if anyone is willing to help with this you will be that much closer to hc. His twitter is @DMonsterProd follow him. And if you have any further questions regarding what needs to be done ask him through twitter he will respond.
Lets get some honeycomb small little step holding us back atm. Thanks peoples
http://www.youtube.com/watch?v=zrt8qGax91U&feature=youtube_gdata_player
sent from a tower
Hellzya said:
If you guys follow dj-steve on twitter then you will know he got honeycomb to boot on the s7. Great news. But to get it stable we need too have the kernel ported too 2.6.36. And maybe have the touch driver modified if that wasn't addressed in 2.6.36.
If you guys can ask around and see if anyone is willing to help with this you will be that much closer to hc. His twitter is @DMonsterProd follow him. And if you have any further questions regarding what needs to be done ask him through twitter he will respond.
Lets get some honeycomb small little step holding us back atm. Thanks peoples
sent from a tower
Click to expand...
Click to collapse
i have been trying hard myself , without trying to bugg dj-steve to much lol but its hard since he seems to be the only one willing
Reach out to your phone kernel devs its what I'm going to do. We need to start some kind of bounty to get some interest in porting the kernel.
sent from a tower
well we need to find whoever is basically working on hc ports already but we might need to send another device to someone in the xoom threads
I think pershoot is the man to ask since he is the kernel king in the game imo. The only problem is he can't do much without a device to try it on.
Sent from my HTC Vision using XDA App
Beta testers my friend pass the word on
sent from a tower
Booted the hc earlier and I must say its awesome. Lack of screen scrolling and such but it looks so good
sent from a tower
Already write to faux123. Lets see!
Sent from my HTC Glacier using XDA App
Yep folks contact as many users as pos. Throw it out on twitter etc. remember we have a near unbrickable device here so reflashing after a failed kernel attempt is as simple as hitting reset and loading into fastboot. And as hellzya said above the most critical issue preventing me releasing a prealpha build is touch screen driver being a bodgejob and not working properly. So if anyones got c coding skills that could be a place to start. Remember im working on 3 tabs and the ni adam is the base for my hc port which works accross most tegra 2 devices it would appear so updates are coming thick and fast.
Sent from my Dell Streak using Tapatalk

Best Version of Honeycomb Port

Who in anyone’s opinion makes the best Honeycomb port for the Nook Color?
I know CM7 is out there and I use it for my phone, I think it’s awesome on my phone and will probably be great on the Nook as well.
Are their any other good ports for 2.3 or especially 3.0?
Right now, we have:
an official CM7 rom.
and HC rom from madcat & deeper blue.
I am endlessly happy that we have such awesome devs working on so few roms. I got sick of the G1 threads blowing up with roms that tended to break more things than they fixed.
Just look for the most recently updated threads in the dev section.
HC is based of sdk, btw.
ace7196 said:
Right now, we have:
an official CM7 rom.
and HC rom from madcat & deeper blue.
I am endlessly happy that we have such awesome devs working on so few roms. I got sick of the G1 threads blowing up with roms that tended to break more things than they fixed.
Just look for the most recently updated threads in the dev section.
HC is based of sdk, btw.
Click to expand...
Click to collapse
Do you prefer one to the other? I was looking to install Honeycomb any advice one which one is most preferable?
IMO since BC is not officially released, you will always be dealing with a not fully ready version. The dev's are doing great work with it but it is not a daily driver unlike cm7
myers022 said:
Do you prefer one to the other? I was looking to install Honeycomb any advice one which one is most preferable?
Click to expand...
Click to collapse
Sent from my NookColor using Tapatalk
I would stick with CM7.
CM7 all the way. HC is amazing for what they have to work with, but for daily driver, cm7 is awesome. Wait for the next nightly, and all will be well
ace7196 said:
CM7 all the way. HC is amazing for what they have to work with, but for daily driver, cm7 is awesome. Wait for the next nightly, and all will be well
Click to expand...
Click to collapse
Why, what's happening in the next nightly, something new?
myers022 said:
Why, what's happening in the next nightly, something new?
Click to expand...
Click to collapse
Yes do tell.
I Am Marino said:
Yes do tell.
Click to expand...
Click to collapse
Yeah. Seems the more recent nightlies are having trouble with wifi. Should be fixed.
Also, so everyone is on the same page, the bootloader will be flashed as well, so that should help a lot of people out.
Also audio and video hiccups will be fixed.
It's all here. Bookmark and read along!
http://cm-nightlies.appspot.com/?device=encore
I liked DB's HC version, and the version before the recent release of madcat's where the SD card stopped working personally, I couldn't get used to the softkeys from the other versions.
I'd like to echo the responses above that suggest sticking with CM7 as a daily driver for now. HC is coming along nicely, and I do install the latest on an SD card every now and then to check out the progress, but it's really not "done" enough to use every day. CM7 is. The occasional nightly hiccup aside, it's definitely feature-complete enough for daily use.
ace7196 said:
Yeah. Seems the more recent nightlies are having trouble with wifi. Should be fixed.
Also, so everyone is on the same page, the bootloader will be flashed as well, so that should help a lot of people out.
Also audio and video hiccups will be fixed.
It's all here. Bookmark and read along!
http://cm-nightlies.appspot.com/?device=encore
Click to expand...
Click to collapse
so its cm_encore_full-86.zip that has all these issues fixed? thanks
nolook said:
so its cm_encore_full-86.zip that has all these issues fixed? thanks
Click to expand...
Click to collapse
Theoretically, yes......However it is still a "nightly" build and hasn't been labeled as stable....Some things could be fixed and other stuff could have broken in the process (don't know that's the case, just saying it's a possibilty.)

Moderator:please close this thread

My own Project was already in the works for another TEAM:
http://www.aedesign.cn/bbs/forumdisplay.php?fid=6
DOWNLOAD of THEIR work:
http://u.115.com/file/bh5z76gp#AED_Legend_5.0.0.RC3_exp.zip
good to see
Good to see someone else to make something new for the legend comunity. Keep going!
By the way, what is your ROM base? The video is too blury...
ogo2 said:
Good to see someone else to make something new for the legend comunity. Keep going!
By the way, what is your ROM base? The video is too blury...
Click to expand...
Click to collapse
I would say this rom:
http://www.aedesign.cn/bbs/viewthread.php?tid=316&extra=page=1
Looks cool, looking forward to this rom. Gj so far
Sent from my Legend using XDA App
I am glad as well to see someone else step up to the plate. I think this will give the CyanogenMod developers some more motivation to make a stable release.
LiViD said:
I am glad as well to see someone else step up to the place. I think this will give the CyanogenMod developers some more motivation to make a stable release.
Click to expand...
Click to collapse
Yeah, I know we are idiots. All of our releases have been unstable, full of bugs and missing nearly every feature one could wish for. Please excuse us, but we really can't do any better. The fact that all ROMs that are not based off RUUs are CyanogenMod rip-offs should clearly tell you that we just can't get anything right at all.
Very MIUI like.. Looks pretty much like my new Desire... Great job seeing similar running on the Legend..
Sent from my HTC Desire using XDA Premium App
great job!
LiViD said:
I am glad as well to see someone else step up to the plate. I think this will give the CyanogenMod developers some more motivation to make a stable release.
Click to expand...
Click to collapse
i suggust u say sorry for your arrogance to the CyanogenMod tea
btw awsome work!
dilip007 said:
i suggust u say sorry for your arrogance to the CyanogenMod tea
btw awsome work!
Click to expand...
Click to collapse
You guys don't pay attention to the experimental thread do you? Seriously, over 160 attempts at a nightly build and still nothing that performs up to par with ogo2's 2.3.3 Sense UI ROM. Sure his is lacking WiFi AP functionality, but I can live with that.
I love how you call everyone elses' ROM a rip-off of a CM ROM. Get a life guys, no one would attempt to use your builds unless said person was extremely lazy.
LiViD said:
You guys don't pay attention to the experimental thread do you? Seriously, over 160 attempts at a nightly build and still nothing that performs up to par with ogo2's 2.3.3 Sense UI ROM. Sure his is lacking WiFi AP functionality, but I can live with that.
I love how you call everyone elses' ROM a rip-off of a CM ROM. Get a life guys, no one would attempt to use your builds unless said person was extremely lazy.
Click to expand...
Click to collapse
Damn.. Where have you lived your life? 2 versions of stable ROMS is what we have.. original from HTC is 1 - CM is 2.. All roms worth mention is variations of one of those.. (for Legend that is)
Sent from my HTC Desire using XDA Premium App
LiViD said:
I love how you call everyone elses' ROM a rip-off of a CM ROM.
Click to expand...
Click to collapse
I know I'm wasting my time here and I really don't care anyway.
Still I think I have to clarify that I'm not talking about people using some "builds". I'm talking about the source code.
If you want to build a ROM for the Legend (and nearly every other device out there) you've got two choices: Push some files from official releases (RUUs) around and zip them, or compile from source.
As a matter of fact there's no project out there that releases working source code (for anything but Google's official devices) except for CyanogenMod.
Video encoding or decoding? msm* support? Backported code for ancient libcamera, libril and framework support for said ancient libraries? GPS backport or implementation? Kernel backports for Gingerbread? Yeah, good luck finding that somewhere else (no, I don't mean the CAF repositories where we are copying from and giving credit of course).
LiViD said:
Get a life guys, no one would attempt to use your builds unless said person was extremely lazy.
Click to expand...
Click to collapse
"Get a life"? Come on, don't be ridiculous.
MD5-sums can be quite revealing by the way. Or boot messages (like "Welcome to CyanogeMod" in MIUI). Some people were even charging for shady rip-offs – that's why the CM team ultimately decided to close down development and switch to "release when it's done".
LiViD said:
Seriously, over 160 attempts at a nightly build...
Click to expand...
Click to collapse
Sorry, but you didn't understand the concept of a nightly build? There are no "attempts at a nightly build" and they are not even meant for users. Nightly builds are there to see if current code in the repositories still compiles. Nothing else.
whitetigerdk said:
All roms worth mention is variations of one of those.. (for Legend that is)
Click to expand...
Click to collapse
Unfortunately not only for the Legend but for most other devices too.
Android was said to be open but in fact it's just proprietary crap again. No developer wants to spend months doing the work of forty CM devs, so they either join CM – or sometimes steal their work declaring it as their own – or use (or combine) binaries from official releases.
If you didn't care, you would be in other developers threads attacking their attempts at making something that just may work better than what you're pushing out.
Face the facts; People want more choices other than CM. I am willing to admit that CM 6.1 was a damn good ROM when it came out, but I can't for life of me figure out why you guys can't live up to the same expectations with CM7.
I have been testing the NewSense 1.0 RC's (HTC Salsa ROM) for some time, and I as I said; Without the lack of AP support, it works well and does not have the crash prone problems that I have seen with 7.0.3, and 7.1 RC1.
ali ba said:
Unfortunately not only for the Legend but for most other devices too.
Android was said to be open but in fact it's just proprietary crap again. No developer wants to spend months doing the work of forty CM devs, so they either join CM – or sometimes steal their work declaring it as their own – or use (or combine) binaries from official releases.
Click to expand...
Click to collapse
Oh Sorry.. Didn't know much of other devices.. Recently bought the Desire and currently using MIUI. Must admit that I believed the MIUI to be a completely rewrite of the Android framework..
Sent from my HTC Desire using XDA Premium App
LiViD said:
I have been testing the NewSense 1.0 RC's (HTC Salsa ROM) for some time, and I as I said; Without the lack of AP support, it works well and does not have the crash prone problems that I have seen with 7.0.3, and 7.1 RC1.
Click to expand...
Click to collapse
You can thanks for that to HTC, because i haven't written a single line of code in NewSense. Only some crappy hacks.
Really, our community is too small and we have a lack of devs, but that's not all. HTC provide to us just ****ty sources. It just sucks!
Btw: this rom here is based on cm7...
Edit: I commented on the wrong ROM. My bad.
I still think Blayo's rom's are the best for Legend!
Been using them for quite a while and I never have had any complain!
whitetigerdk said:
Must admit that I believed the MIUI to be a completely rewrite of the Android framework..
Click to expand...
Click to collapse
Their earlier releases certainly used CM sources with modified framework and apps. I don't know what they are doing now – but as they don't release their sources I can accuse them of using modified CM source code as much as I want without ever being able to prove it so I refrain from doing that.
If you are interested, the UltimateDroid soap opera is a good read by the way.
ogo2 said:
You can thanks for that to HTC, because i haven't written a single line of code in NewSense. Only some crappy hacks.
Click to expand...
Click to collapse
That doesn't make your work worth less than anyone else's and certainly not "crappy".
ogo2 said:
HTC provide to us just ****ty sources.
Click to expand...
Click to collapse
I'd be happy if they provided the real sources for the binaries they are releasing but as a matter of fact HTC continuously violates the GPL and we can't do anything about that.
LiViD said:
If you didn't care, you would be in other developers threads attacking their attempts at making something that just may work better than what you're pushing out.
Click to expand...
Click to collapse
Where exactly did I attack emiliano7's work? I'm actually very glad that someone is developing for the Legend and I never stated anything else.
You obviously on the other hand couldn't resist showing your arrogant attitude by addressing the CM team in this thread making false accusations. You can't take a discussion off-topic and then blame others for taking the same train.
LiViD said:
...the crash prone problems that I have seen with 7.0.3, and 7.1 RC1.
Click to expand...
Click to collapse
Instead of making vague accusations you could have filed bug reports a long time ago. CM is a community project and nothing without its community.
It sometimes still makes me sad that for some people whining doesn't seem to be a problem but as soon as it comes to writing a good bug report they come up with various excuses.

HTC Tattoo and CM9?

So CM7 was a stellar success for our tiny lil device called Tattoo.
Now that CM7 is over, we'll are eagerly waiting for CM9. I posted this thread to know if Tattoo is going to be supported in the CM9 builds. If anyone of you has an idea of what is going on, you can reply here. Also you can use this thread for dev purposes.
Others here, you can list out what features you want to see on out Tattoos running CM9. This can come of great help to the devs until the actual thread comes up.
So when many devices have got early CM9 builds, why not us? arco68 and KalimochoAz, you there?
The CyanogenMod team already announced that one phone which will not get the upgrade is the Motorola Droid because of it's outdated hardware. You know, Droid is really similar to Tattoo specwise. Same CPU specs, same RAM amount, same internal memory.....
You draw the conclusions.
pretty bleak future for us indeed. but the hero and the G1 are running early builds of it already. so if G1 can do, why not Tattoo?
sunitknandi said:
pretty bleak future for us indeed. but the hero and the G1 are running early builds of it already. so if G1 can do, why not Tattoo?
Click to expand...
Click to collapse
Any hope for us. Be patient. They only write about Droid1: http://www.cyanogenmod.com/blog/cm9-progress-update
BilboPC said:
Any hope for us. Be patient. They only write about Droid1: http://www.cyanogenmod.com/blog/cm9-progress-update
Click to expand...
Click to collapse
This blog post pretty much confirms that we won't be getting CM9.
Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One.
Click to expand...
Click to collapse
Our device is MUCH less-powerful than the QSD8250, which is a 1.0-1.2GHz CPU and Adreno 200 GPU System-on-a-Chip.
if that is true, wildfire wont get it too.
My guess it it will run. But should be optimized heavily for a smooth experience.
Sent from my HTC Tattoo using XDA App
I'm afraid the low resolution will be the show stopper there.
Maybe possible but it will be light version of ICS a few of the ingredients may be removed.
The screen is 2.8" n this is maybe the drawback...
I have installed ICS on G1. Its horrible ROM, Very Laggy and still needs lot of development for smoother experience. They haven't fixed the rotation problems yet. It looks to me Tatto0 will have a hard time with CM 9 because of its lower quality hardwares.
Tattoo is a 2 years old phone
Once we made it 2.1/2.2
It great already
And now we even have 2.3
What are we still asking for
As google told before
4.0is for high end
So let's enjoy the extra bonus that we get
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
There was a Christmas gift to buzz community from Arco
http://forum.xda-developers.com/showpost.php?p=20639586&postcount=61
which i think is a good news for Tattoo as well in terms of CM9
i still have hope!
it might not be a perfect version of android 4, but at least we can try and have fun a little bit while we wait for next year's christmas for a new phone!!
Look at this
http://www.youtube.com/watch?v=Ym4A82ft5pw
It's ICS running on htc g1, the first android phone! I hope we can run it also on our tattoo
mattia29 said:
Look at this
http://www.youtube.com/watch?v=Ym4A82ft5pw
It's ICS running on htc g1, the first android phone! I hope we can run it also on our tattoo
Click to expand...
Click to collapse
Yes, it's running, but as you can see it's too slow, really.
Yes but tattoo has a little better specs than G1
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
arif-ali said:
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
Click to expand...
Click to collapse
That's awesome, man. I would done it if I had knowlege
arif-ali said:
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
Click to expand...
Click to collapse
Please do it if u have time.
Update on compilation
Hi all,
Everything I do is all open, so you will see what I have done; this also gives others the chance to contribute
If someone wants to see my progress, then you can go to the following git repo
https://github.com/arif-ali/android_device_htc_click
and when I have a build it will be located here
http://cyanogenmod.arif-ali.co.uk/rom/test
So far quite a bit compiles, working on the wpa_supplicant part now. Looks like it may be a hack or need to look somewhere else.
I've had the Tattoo for 2 years now, but don't really know the HW much, so much research will be required. I've just installed nfinityGB, as and when arco built it.
If someone can give any input, it may speed up my work; and it will be appreciated.
Edit 1:
* Got passed the wifi, just got the drivers from gingerbread (for my notes)
Code:
cd system/wlan
git clone git://github.com/CyanogenMod/android_system_wlan_ti.git -b gingerbread
mv android_system_wlan_ti ti
sed -i s/LOCAL_MODULE_TAGS.*/LOCAL_MODULE_TAGS\ :=\ optional/g system/wlan/ti/sta_dk_4_0_4_32/config/Android.mk
* Need http://forum.xda-developers.com/showpost.php?p=20737947&postcount=27 for compilation as well
Code:
unzip ../webrtc.zip -d external/webrtc/
Edit 2:
Good News; first compile done.
Bad News; it's 4am in the morning, and I can't be bothered to test
I have no idea if it is going to work or not, and if someone is really adventurous, then feel free to try flashing the file from the following URL in about 20 mins i.e. better to try 04:30 GMT to be on the safe side
http://cyanogenmod.arif-ali.co.uk/rom/test/update-cm9-click-20120101.zip
system is going to be 162M, and gapps can be downloaded from http://cyanogenmod.arif-ali.co.uk/misc/gapps-ics-20111128.zip
Personally, I won't be able to test until tomorrow now
Edit 3:
NVM, this won't work, our system is only 150M; I will give it another go later

Categories

Resources