so im sorry for bringing this up (i read the sticky) but i am not sure what the latest update means about honeycomb video drivers from nvidia. does that mean that there are no video drivers that are going to be released for the gtab from now on? does that mean its impossible to port honeycomb to the gtab? i dont know how to interpret their response and that is going to help me decide what to do with it (since i just got it). thanks!
From what I can read into it, nVidia has stated that they will continue dev and support for the gtab for as long as Viewsonic requests them to do so. And Viewsonic has stated that they are going to continue dev and support. So, in short, yes. We will most likely see Honeycomb at some point in the future. We just don't know when.
Sent from my Desire HD using Tapatalk
so their message wasnt saying "f u gtab, u get nothing" ? its only for as long as viewsonic continues to support it?
joshtb86 said:
so their message wasnt saying "f u gtab, u get nothing" ? its only for as long as viewsonic continues to support it?
Click to expand...
Click to collapse
Yes, up until they decide the Gtab is old news and they determine that it would not be cost efficient to do so. After all of those tablets sold on woot (over 10,000) I can't imagine that would be any time soon.
Myself, I could care less if Honeycomb makes it to the Gtab. It would be nice, but CM7 is serving me very well for anything I need to do with it. There is a bit of choppiness in videos using the YouTube app, but if viewed via the web browser (I use Skyfire) they are as smooth as can be over wifi or with a good 3g signal. Native video drivers for even Gingerbread would be very helpful and I feel that we will see them long before anything of the Honeycomb flavor.
I wouldn't dump my Gtab just yet, there's way too many ways to have fun with it considering all of the dev work that's still being done by GoJimi, Calkulin, rothnic, roebeet, clemsyn, pershoot and many others.
MOD Alert! - You may want to move this thread to G-tab General or Q&A since this is not Developmental.
okay. so what exactly did nvidia mean? and if they stop supporting the gtab, what does that mean for the gtab? and video acceleration - is that just video watching, or does that mean 3d acceleration for video games as well?
I can't point you to the exact news release but Nvidia did officially say last week what hitekredneck said about continuing to support the Ginger chip. They indicated that the previous statement about not continuing to support the Ginger was in error by an unofficial spokesman (I think I am remembering this correctly).
I kinda agree with hitekredneck about Gingerbread on the Gtablet. I bet we see those hardware video drivers released by Nvidia for Gingerbread soon making GB a complete ROM.
what exactly do these video drivers do?
Has the Viewsonic Gtablet development become a standstill?
Thoughts?
Opinions?
No.... I believe not.
Now everyone's holding their breath for HC.
Here somewhere is a post about latest development (sorry can't find it now).
HC is already booting on G-tab. Hopefully devs will get everything they need to get it going.
Keep my fingers crossed!!!!
You have a cyanogen tag in your sig and yet you ask that? They are releasing nightlies at least once a week. As far as Honeycomb goes it may be booting but its completely worthless to use.
I think I'll keep my thoughts and opinions to myself as anything negative about the wonderous GTab is not tolerated here
thebadfrog said:
You have a cyanogen tag in your sig and yet you ask that? They are releasing nightlies at least once a week. As far as Honeycomb goes it may be booting but its completely worthless to use.
I think I'll keep my thoughts and opinions to myself as anything negative about the wonderous GTab is not tolerated here
Click to expand...
Click to collapse
LMFAO, you can always talk about the "horrible viewing angle" everybody CAN agree on!
Kenfly, there is actual progress reported that I believe involves a dump of an ASUS Honeycomb box that has been ported to the Adam and there is a picture of it on a G-tab. I just read about actual WPA2 support too.
Here is the thread: http://forum.xda-developers.com/showthread.php?t=1065220
The good news is, Roebeet has taken an interest too, so there are some VERY clever guys working on this!
Yes there is but it is completely unuseable at this point.
I was told the viewing angles are not horrible and to expressing my opinion of that as well
http://forum.xda-developers.com/showthread.php?t=1064775
Follow that thread. Oozura is doing a great job keeping everyone up to date with cm nightlies and releases with bugs and bug fixes. They are making huge progress on major issues right now. It means at some point Gojimi will update VeganGinger as well.
If you follow that thread keep mashing that thanks button for him so people know there is interest and he keeps posting
I see it slowing down as more turn towards the newer tablets on the market. Updates wont be as frequent...
If you have it setup good now then you'll be ok. Its not like the internet, video or audio will stop working because of this.
kenfly said:
Has the Viewsonic Gtablet development become a standstill?
Thoughts?
Opinions?
Click to expand...
Click to collapse
No?
Looks like tons of action to me - pershoot and others have delivered stable overclocked/undervolted kernels in the past week, and the CM7 team has cranked out two stable and about 10 nightly revs in the past week, going from "yes, it sorta works" to functional camera and some hardware acceleration for video playback.
What projects are you working on?
there are more forums to search than the ones here (hint)
There's a lot going on, in early (VERY EARLY) stages.
While some might believe that the Gtab is worthless, I would argue that the hardware itself is not at all. The company that put their name on it, and their "support" might very well be as worthless as a batteries to the Amish.
There are experiments going on utilizing The Notion Ink Adam, and porting it's software to the G-tab. There's a rumor that they are getting an official GB update, and if portable to the G-tab, then we could essentially have an "official" GB Rom (including drivers from Nvidea), without VS needing to get their hands dirty. There are a few comparable (in hardware) tablets out there that are getting the support from their manufacturers that we would like to get from VS. If we can't get VS to update, then the next best thing is to borrow updates from other systems.
If it all works out, it will definitely not be a quick release. Lots of testing would be needed, since the code being worked on is not "made" for the G-tablet.
The reason that it seems like development has halted, or at best, slowed down, is because nothing new is coming from the allmighty VS. Nothing can be developed from the nothing that they are constantly providing. The only development that can be done is using existing Roms, and tweaking them. The bottom line, though, is that unless VS comes out with a GB Rom WITH hardware drivers, the current batch of custom Roms, Vegan-Tab, VeganGinger, CM7, TNT, etc. are dead in the water, and will never have hardware acceleration, since they are all based off of old code, that doesn't include it.
So, simple answer, there are developments that are ongoing, there are tweaks and fixes, possibly additions to some of the existing roms, but there will never be any development on new VS rom, until VS actually releases a new VS rom.
Only one person is building off VS firmware. Everyone else is using Google source and from the commits that Nvidia is making to git. VeganGinger and CM7 are under constant development and CM gets closer everyday to finalizing hardware acceleration. Vegan-Tab is froyo and based off vega firmware and has hardware acceleration as does TNTlite.
Depending on Notion Ink, the king of stretching the truth, for something is knuts
And yes there are some half ass non useful ports of Honeycomb posted on other sites. Nothing works. Its a honeycomb gui hacked into an old kernel
TJEvans said:
While some might believe that the Gtab is worthless, I would argue that the hardware itself is not at all. The company that put their name on it, and their "support" might very well be as worthless as a batteries to the Amish.
Click to expand...
Click to collapse
Great analogy. =)
TJEvans said:
There are experiments going on utilizing The Notion Ink Adam, and porting it's software to the G-tab. There's a rumor that they are getting an official GB update, and if portable to the G-tab, then we could essentially have an "official" GB Rom (including drivers from Nvidea), without VS needing to get their hands dirty. There are a few comparable (in hardware) tablets out there that are getting the support from their manufacturers that we would like to get from VS. If we can't get VS to update, then the next best thing is to borrow updates from other systems.
Click to expand...
Click to collapse
The NI software release, if they do in fact follow through with something for once, will be utilizing the exact same GB-compatible drivers that we already have. We already have "official" GB ROMs with the same level of HW accel that anything from NI would come out with. We already have those drivers from nVidia. =)
But you're right in implying that VS won't have to get their hands dirty. =)
TJEvans said:
Nothing can be developed from the nothing that they are constantly providing. The only development that can be done is using existing Roms, and tweaking them. The bottom line, though, is that unless VS comes out with a GB Rom WITH hardware drivers, the current batch of custom Roms, Vegan-Tab, VeganGinger, CM7, TNT, etc. are dead in the water, and will never have hardware acceleration, since they are all based off of old code, that doesn't include it.
So, simple answer, there are developments that are ongoing, there are tweaks and fixes, possibly additions to some of the existing roms, but there will never be any development on new VS rom, until VS actually releases a new VS rom.
Click to expand...
Click to collapse
Actually.... you're incorrect here. New development is being done completely independent of VS. It's called CyanogenMod-based and AOSP-based ROMs and they are completely different than those based on VS or NI-based ROMs which anything based on those are in fact MODs and tweaks. CM and AOSP ROMs are based on newer code and do include the foundation for hw acceleration.
So to summarize - development is not dead if you're not based on a locked bootloader and stock ROM from VS. If you're based on Google and nVidia then there is definitely development going on. It's all in what your base is.
We already have "official" GB ROMs with the same level of HW accel that anything from NI would come out with. We already have those drivers from nVidia.
Click to expand...
Click to collapse
You'll have to excuse my ignorance on this issue, as all I've used so far is Vegan-Tab. I love it, it's stable, and I've not seen any inherent problems with it, so I figure, why change?
But, I thought that CM7 and VeganGinger had issues with video playback and 3d video acceleration, since Nvidea is "no longer going to support the Harmony Tegra 2 chipset." I don't know much about CM7, but from reading their website, and observing some of the experimental posts, it doesn't seem that they've been able to truly replicate the drivers that, I believe, Nvidea owes us. Nvidea said that they will provide support and updates if manufacturers requested it. As far as I know, Viewsonic only had one update since they made that statement, and it didn't include anything new from NVidea.
I had assumed that since this rumored NI GB update was official from the manufacturer, that they wouldn't have done it without getting official drivers from Nvidea.
I'm sorry, is there something I'm missing? I thought that it was a big deal that NVidea hasn't provided driver updates for true hardware acceleration, and that it can't be achieved without informaiton from them, and that they've decided ot no longer support...
it's a confusing world in the land of G-Tab.
TJEvans said:
You'll have to excuse my ignorance on this issue, as all I've used so far is Vegan-Tab. I love it, it's stable, and I've not seen any inherent problems with it, so I figure, why change?
But, I thought that CM7 and VeganGinger had issues with video playback and 3d video acceleration, since Nvidea is "no longer going to support the Harmony Tegra 2 chipset." I don't know much about CM7, but from reading their website, and observing some of the experimental posts, it doesn't seem that they've been able to truly replicate the drivers that, I believe, Nvidea owes us. Nvidea said that they will provide support and updates if manufacturers requested it. As far as I know, Viewsonic only had one update since they made that statement, and it didn't include anything new from NVidea.
I had assumed that since this rumored NI GB update was official from the manufacturer, that they wouldn't have done it without getting official drivers from Nvidea.
I'm sorry, is there something I'm missing? I thought that it was a big deal that NVidea hasn't provided driver updates for true hardware acceleration, and that it can't be achieved without informaiton from them, and that they've decided ot no longer support...
it's a confusing world in the land of G-Tab.
Click to expand...
Click to collapse
The rumored NI GB update is just that - rumor just like all the other NI rumors. We'll see what happens.
As to nVidia - the 3991 update that was later pulled from VS contained updated GB-compatible libs that were from the Gingerbread Ventana system image from nVidia. Those libs were (and still are) in CM7 and AOSP and VEGAn-TAB. Hacks and mods have been inserted to make CM7 work with them and hw accel is functioning much better after pershoot's kernel overclocking.
thank you for the clarification
I am confused. I have been happily using Vegan 5.1.1, but want to go to Gingerbread. I looked at "VEGAn-TAB GingerEdition STABLE RC1", but the post says:
"what's missing? Nothing except High Definition Video Hardware Decoding... not sure if we will ever get that one working right on Gingerbread."
Reading further in that thread, the gist is that ROM developers can not implement "High Definition Video Hardware Decoding" in GB on the G-Tab because NVIDIA has not released the "Harmony GB drivers."
So, I tried to start a sticky thread (http://forum.xda-developers.com/showthread.php?t=1075728) that would alert all to the anticipated eventual release of these drivers, but my request was denied, because "gb-compatible drivers are already included in cm7 and aosp-based ROMs."
Does this mean that CM7 and AOSP-based ROMS have "High Definition Video Hardware Decoding", which means I can use those ROMS to move to GB without losing video performance?
Or, do we have here a failure to communicate?
havign not used CM7, I can only comment on what I've pieced together from various posts. Apparantly, CM7 does have some level of hardware acceleration/decoding, but it's not from official updates or drivers from Nvidea. From what I've gathered, it appears that they were custom built using what's available from other ports, or reverse engineering.
Of course, I also believe that the reason your request was dienied isn't valid. you want to keep ev eryone updated on the status of OFFICIAL driver releases from Nvidea. We shouldn't stop expecting them to release support drivers for their hardware, just becuase somebody was able to find a workaround to get it "mostly" working.
It seems to me that admins here are very partial to CM7 and it's developers. Certainly no offense to the devs, but admins should be supportive of all efforts to make the G-Tablet the best it can be, and that includes efforts to get official updates from the software and hardware manufacturers.
My example of this would be that CM7 is a good clone of Gingerbread, it's not officially Gingerbread, though. However, there is great work being done on a clone of Honeycomb, but it get's no love BECAUSE it's not officially Honeycomb. Seems kinda confusing to me.
I believe that your request was denied probably because the official libraries for gingerbread were released in march and this information is available on the forums. To anwser your question yes cm7 and some other roms have used these libraries to enable hardware decoding. However they are still work in progress and overall they wok well. Vegan ginger didn't have the time to include the libraries in his release but i would expect he will soon. G-Hrmony Gb just released his version with hardware accelleration so you might want to try that or cm7. I am not sure if Vanilla Gb has it or not,but i believe it does.
rw144 said:
I believe that your request was denied probably because the official libraries for gingerbread were released in march and this information is available on the forums. To anwser your question yes cm7 and some other roms have used these libraries to enable hardware decoding. However they are still work in progress and overall they wok well. Vegan ginger didn't have the time to include the libraries in his release but i would expect he will soon. G-Hrmony Gb just released his version with hardware accelleration so you might want to try that or cm7. I am not sure if Vanilla Gb has it or not,but i believe it does.
Click to expand...
Click to collapse
Thank you for your replies, I will look at G-Hrmony GB and CM7, and may give them a try.
However, even though there is information spread throughout the forums about hardware drivers and accelleration, it does take a lot of time and effort to locate it all, read through it all, and sort it out. NVIDIA's release of official GB hardware drivers is an important functionality and upgrade issue, and it would be nice if we could easily stay updated on that subject by looking in one place.
Ah well, perhaps NBD, but I'm just sayin...
Update April 22, 2013: Great news!
Yesterday, April 21, 2013, the CyanogenMod build system built its most recent (and possibly final) CyanogenMod 10 nightly for Nook Color. Why? Because the 10.1 builds are here! There's a whole new thread about it, so check it out.
If you'd like to try the (now legacy) April 21 build of 10.0, it is here:
cm-10-20130421-NIGHTLY-encore.zip
md5: d6d6c7c6229bae992729db615984f2b8
Otherwise, if you're interested in stepping up to CyanogenMod 10.1, we'll see you over on the new thread!
____________________________________________________________________________________________________
LEGACY STUFF -- STUFF BELOW THIS IS OLD! CHECK OUT THE LINK/INFO ABOVE
____________________________________________________________________________________________________
NookieDevs 2012 Are Engorged with Pride While We Announce
CM10 Nightlies
for Nook Color (aka “encore”)
"CM10 for Nook Now Belongs To the Ages" Edition
WE'VE MOVED TO OFFICIAL CM 10 NIGHTLIES!!!!
That's right. Starting Nov 14, 2012, the official CyanogenMod servers are building a new fresh version of CM10 for encore every evening. This is a milestone in the development. Updates can also now be done automatically using the CyanogenMod Updater in the Settings.
Let's get to the good stuff:
Nightly Changes (starting 12/14/12)
* Here's what's new!
WHAT STILL HAS ISSUES (?)
rare reports of high pitched noise on some hardware versions when coming out of sleep (but not confirmed)
adb w/usb seems to slow down when CPU is under load. To investigate, but not a show stopper.
Overclocking is not in yet
OTG not in yet
You tell us!
---------
older
---------
B5 Changes (11/12/12)
fixed the 600 mhz default for real this time
SmartReflex added (better battery life?)
way better touchscreen responsiveness (all salute Keyodi!)
kernel repository has been renamed
Updated to latest source of upstream CM10
security hardening
B4 Changes (11/8/12)
Updated to today's CM 10 upstream source
cpu clock defaults to 1ghz
a2dp (hopefully) fixed
B3 Changes: (11/6/12)
Updated to today's CM 10 upstream source
Updated wifi firmware to version that seems to fix networking and power issues
N-key wake is back
Fixed double-tap to wake device
power_hal changes
software menu key was fixed
possible SOD fixes for those having issues
More love was given.
B2 Changes (10/31/12):
"Sleep of death" on ES1.2 models- hopefully fixed
i2c commit that caused the black screen on boot has been pulled
the "n" to wake fix that caused ES1.2 SOD is gone too... sorry, but at least it fixed the black screen on boot issue
zram compressed memory added to kernel (see settings/performance)
bfq IO scheduler enabled in kernel (see settings/performance)
B1 Changes:
Based on latest CM10 source code as of 10/30/12
Netflix - works!
YouTube HD- works!
Passes Compatibility Test Suite for hardware (except for camera/GPS- wonder why?!)
Fixed "sleep of death" (SOD) on newer OMAP3 hardware model (ES1.1)
Charger detection issue is fixed
No sound on resume fixed (we think)
Updated PVR version
"N" button is now detected always see b2-- some models will need to use power button for now to wake the device
Fix to kernel to provide serial number
OpenGL now built in and works
CM "expanded desktop" feature turned on
Some notes:
Don't try to play ridiculously high 1080P h.264 video on this thing unless you like stuttering. There's a practical limit to what hardware from late 2010 can do.
That's it! Enjoy (as always, at your own risk and discretion)... and let us know what you think!
The NookieDev Team
:cyclops::cyclops::cyclops:
________________________________________
UPDATE 10/19: SURVEY TIME!!!! Turns out there are a few models of Nook Color that need to be supported. Can you help debug?
Fill out this survey to help narrow down issues. (More info here)
________________________________________
WHAT IS THIS ANNOUNCEMENT?
For a little more than a year now, the NookieDev team (comprised of a floating band of scoundrels and miscreants on XDA, Rootzwiki, Twitter, and other obscure corners of the Internet) has been laboring day and night to bring CyanogenMod 10 (based on Google’s Jellybean Android 4.1.2) to the Nook Color (aka “encore”) devices.
The port has involved overcoming numerous technical hurdles, the least of which was the need to move from a 2.6.32 kernel to a shiny new 3.0.8 kernel. Drivers were modified and (re)-written, large chunks of code from various kernels were backported, forward-ported bits were also shoehorned into place -- all using the open source 3.0.8 OMAP3 code base from Texas Instruments.
A new bootloader menu has also been written, then ported to the Nook Tablet. Improvements from the Tablet were then ported back to the Nook Color version, and over several iterations, the “Cyanoboot” bootloader got better and better. It’s pretty cool now, we think.
Over this past year, instructions for building from scratch were posted, and hundreds of users delved into the dark art of loading virtual machines, installing toolchains, downloading source, and assembling the new OS themselves. This experiment resulted in a new wave of contributors and testers, and we are grateful for their participation as well. The development forum has been full of reports of people building and testing CM10 themselves, but we have asked (and they have respected) that no binaries be posted so that developers, potential developers, and those-who-just-want-to-learn can be the first wave of "guinea pigs".
That brings us to today. Just in time for the BigAndroidBBQ, a gathering of Android developers and enthusiasts in Texas, we are pleased to announce that nightly builds are available -- at no charge -- for testing. If we may say so ourselves, this release is a triumph of the power of open source, collaboration, teamwork, and sharing knowledge for the betterment of everyone. If you’ve used CM7 -- or even one of the test versions of ICS -- on the encore device, you may want to back up your systems and give the nightly builds a try.
WARNING/DISCLAIMER
Understand that there are likely to be bugs, both known and unknown, and that all appropriate experimental-software disclaimers apply, including the fact that by using or attempting to use this software, you assume all risk for fooling with your hardware. We will not be held responsible for any potential loss of data, destruction of hardware, removal or disappearance of limbs, life, or coins in the couch. We do not claim this software is fit for any purpose, etc. Beware of Dragons.
This said, we do feel that the our work is finally “good enough” for interested people with a tolerance for risk to get their hands on.
WHAT IS CYANOGENMOD?
It's an "alternative firmware" that can be used in place of the regular "stock" operating system. See the Wikipedia entry for more info.
IS THIS AN OFFICIAL RELEASE OF CYANOGENMOD?
Starting with the nightlies, yes it is.
WHAT’S DIFFERENT IN THIS BUILD FROM CM7?
It’s anticipated that some users may have not updated since CM7. So here’s a non-exhaustive list of changes:
based on recent CM10 version of Google Android 4.1.2 ("Jellybean")
based on the 3.0.8+ OMAP3 kernel
over-clocking (OC) above 1ghz is disabled for now. This is so we can rule out OC as causing bugs that may be reported. The 3.0.8 kernel is still in development, and OC will be available again later.
non-official CM10 source code has been moved to the NookieDevs account on the Github.com web site. (To get CM10 to work on the Nook Color,minor modifications were made to official CM10 source. So until those changes are adopted “upstream” into the CM10 source, we have made them available on the NookieDevs repository)
WHAT DOES WORK?
Pretty much everything, except where mentioned below, and where we just haven't noticed yet
WHAT DOESN’T YET WORK?
See above announcement
HOW DO I INSTALL THIS ON MY EMMC (INTERNAL STORAGE)?
These instructions assume you are familiar with replacing the firmware on your Nook Color and understand what a “recovery image”, such as ClockworkMod or TWRP2, is used for. If you are unfamiliar with these concepts, or have never replaced the stock firmware, don’t worry. Instructions and additional help are available across the Internet. A simple Google search should help you.
Note: We *STRONGLY* recommend a full data backup and factory reset when installing CM10, no matter what rom you were running previously. In fact, please do not post a bug report unless you did a full wipe.
To install CM10:
(recommended) Boot into your recovery and make a nandroid backup of your current rom and data. This way anything goes wrong, you can always recover your original installation.
Download the latest CM10 nightly .zip (and optionally the google apps from another source, as we are not distributing this software) and place it on your SD card.
Again using your preferred recovery image, do a full wipe of the system as well as a factory reset (data wipe).
Use the recovery to install the .zip (or .zips if you are also installing the Google apps).
Reboot
Enjoy!
WHAT ABOUT A "SD-BOOTABLE" VERSION?
Good news! You can make your very own free bootable CM10 SD card. It’s not hard, and we recommend you get a blank SD card and give it a shot before paying anyone else for a “pre-made” SD card. (If you don’t have a blank SD card, they can be found very inexpensively at most electronics retailers.) To do so, you will need leapinlar’s SD Installer here. It is a modification of verygreen’s famous SD installer, which was used with CM7.
This program will help you turn a CM10 .zip file into an image that can be flashed onto an external SD card.
Note: We strongly advise that you DO NOT overpay anyone for a pre-made SD card. If you have difficulty with making your own SD card, there are plenty of people online who can and will help you. There are unfortunately some unscrupulous people (aka “parasites”) taking advantage of their customers (aka “victims”) who don’t realize how easy it is to make their own SDs. Be wary of hucksters overcharging for this “service”.
We also ask that you please keep discussion of SD-card related install issues in the SD Installer thread referenced above.
WHAT DOES THE “EMMC 01” MEAN IN CYANOBOOT WHEN I START UP?
Note: There is a special forum thread dedicated to CyanoBoot.
When you first boot, you’ll see an “EMMC” or “SD” in the top corner, depending on which you’ve started from. Then “01” refers to the “bootcount”, which is an internal counter that is cleared back to 0 when the boot is successful.
(You can usually ignore the “01”.)
WHY ARE SOME OPTIONS GREYED-OUT IN THE BOOT MENU?
CyanoBoot should auto-detect which forms of boot are possible (ie, you can’t boot off SD card if there’s no SD card installed!) and grey them out for you.
HOW DO I BUILD CM10 MYSELF FROM SOURCE?
The build document for cm10 has been updated to reflect the newest instructions for building yourself. The build document is now a bit old and will be replaced soon... stay tuned.
Please keep all questions about building and developing on the [DEV] thread. This thread you are reading is intended for those who are using the nightly builds.
AND WHY WOULD I WANT TO BUILD MYSELF EXACTLY?
To quote myself:
You never, ever have to wait for a nightly
You can add or remove as-yet uncommitted features with ease.
You learn how Android works under the hood
You learn how to use Linux
You'll learn how to use git
You may, even accidentally, pick up a little C, Java, C++, and learn about the build system.
You can personalize Android-- make your own tweaks, replace kernels, modules, graphics, add or remove projects, overclock, underclock etc. In other words, you have control over every aspect of your device's functionality. Your build is custom to you.
You can audit the code for potential security issues such as back doors or trojans (as opposed to just trusting a random person who posts a build). Since CM10 source is open, you can examine every commit, and there are many eyes looking at the code. (does not apply to proprietary blobs, but these are pulled from your device, so you have and are using them already)
You can contribute features/fixes back upstream
You can start ports to other as-yet-unsupported devices (start by copying folders from similar devices to devices/manufacturer/model)
You come to really understand that Android phones and tablets are full-fledged general-purpose computers just like laptops and desktops.
AAAAND....you get huge bragging rights
The extent to which you delve into the above is entirely up to you. The walkthrough is just an introduction to that world. Some people will build once and never do it again... but others will start to tinker and make changes to their own build and want to share them with others, and soon some will start making contributions back to official CM10 upstream... or port to new devices... and by fixing bugs and all this... everyone benefits.
Plus...
It's fun.
(Here are some little bits that resulted from the nexus 7 thread quoted above.)
Dealing with build errors
What's where in the CyanogenMod source folder
A little about make clean and make clobber
I’M HAVING PROBLEMS! WHERE DO I POST PLEAS FOR HELP?
You have many, many options for seeking help!
See the Nook Color forum on forum.XDA-Developers.com to ask the community questions, please be mindful to post in the appropriate forum. General jellybean discussion and user help should be in the USER thread in the general forum - not in the development forum. If you think you have found a bug that hasn’t been reported yet, then post that in this thread.
You can also visit #nookcolor on IRC (freenode server) by clicking on:
http://webchat.freenode.net?channels=nookcolor
Additionally, you may find more information about the Nook Color at www.nookdevs.com as well as on Android-friendly blog sites such as liliputing, RevTV, and many more.
HOW CAN I HELP DEBUG AN ISSUE I’M HAVING?
Great! We hate it when people post “hey guys.. *this* doesn’t work” and go on their merry way. Where possible, we may try to reproduce the bug. But sometimes, we can’t.
The best way to discuss an issue you are having is to include a “log cat”. A logcat is a special log that Android will give you using the “adb” program mentioned above that helps to determine what is going wrong and why. To include a logcat, simply download adb to your computer, connect your computer to the Nook Color with a USB cable, and then type “adb logcat” on your computer so that the log begins to scroll in the window. Copy and paste this log to a site such as pastebin.com, and post a link to the log when you are reporting the problem you are having.
You can read more about logcat and how to get one in this thread.
WHERE DO I SEND MY MONEY?!
Every developer on this has their own motivation for participating in the project, but it’s pretty obvious money isn’t one of them. Some members of the team may have set up methods for making donations, but speaking overall, NookieDevs isn’t about money. It’s about the fun of hacking this amazingly versatile device.
BIG NOTICE FOR YOU NOT TO MISS: As mentioned, one place to NOT send money is any company that is overcharging for this free port. Many of these companies are, to say the least, douchey. These parasitic businesses may gouge their customers for free software without making it abundantly clear that they can easily download and install it themselves. How these scamsters sleep at night, we can only speculate -- probably on a pillow stuffed with cash.
WHO DO I THANK?
Oooh boy, this is going to be a long list ... You can thank the "NookieDev" core folks, but you also need to thank the random people who stopped by, contributed some small thing, then disappeared. There’s also the developers that made CM7 possible (some of whom worked on CM10 too). Then there’s the forum moderators (inc. Divine Madcat, thanks!), upstream CM team, and their contributions on top of the Google code. Of course Google deserves big thanks, and so does Barnes and Noble and the subcontracted engineering team that made the NC, including the designers at Yves Beher’s fuseproject. Which certainly means we also owe Texas Instruments a huge debt of thanks, not only for making the OMAP devices, but for its world-class developer community support. And then there’s the people who developed the various languages, platforms, compilers, linkers, and coding practices that made Android possible... We can’t forget the Linux kernel coders... and it goes on and on. We’d like to give a special shout out to James Clerk Maxwell, who really doesn’t get enough credit in these “thanks” lists. Quick ups also go to Ada Lovelace, Alan Turing, Benjamin Franklin’s key maker, and the late Dennis Ritchie.
All that said, here are the more-or-less core members of the team.
fattire - @fat__tire on Twitter
krylon360 - @krylon360 on Twitter
eyeballer - @eye_baller on Twitter
keyodi
sluo
Other people who have worked on related projects such as CM7 and CyanoBoot include dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, and many more.
The above are in no particular order, and as we say -- massive, necessary contributions have come from every corner of the Internet. As the inventor of the Fig Newton reminds us-- we all stand on the shoulders of giants.
I HAVE A NOOK TABLET (OR NOOK HD). WILL THIS STILL WORK?
There is an experimental version of CM10 available for Nook Tablet available in another thread. If you have a newer Nook, do not expect an alternative rom any time soon. The newer Nooks are expected, like the new Kindles, to have locked bootloaders.
IS THAT IT?
Sure for now. Enjoy, and remember... if something screws up, don’t blame us!
(check this thread again for updates)
--------------------
Want a nightly builds? Look here!
Download (beta 5): cm-10-encore-b5-barelybuggy.zip
MD5 Checksum: f22e826f637b57245250ca7aa9de147d
Download (beta 4): cm-10-encore-b4-notsofullofbugs.zip
MD5 Checksum: 45cd0b04c0f9c6bc4b3be684cebd4b22
Download (beta 3): cm-10-encore-b3-stillsomebugs.zip
MD5 Checksum: cd6dadefa2087a005b5d47e758e7cf59
Download (beta 2): cm-10-b2-encore-fullofbugs.zip
MD5 Checksum: 9f0c6ca00c72ca944c2193dab1501dc1
(UPDATE: I appreciate the "thanks", but be sure to scroll down and thank the others too!)
CM10 nightly mirror (get.cm seems to be having issues)
http://techerrata.com/browse/cm/encore/nightly
Please make sure you're using the correct gapps:
Download gapps: http://techerrata.com/file/gapps/gapps-jb-20121011-signed.zip
Mirror: http://goo.im/gapps
By default with the current gapps picasa sync will not be an option, if you would like to sync your photos with picasa then you'll need to also flash this (after you flash the full gapps package): http://techerrata.com/file/gapps/gapps-jb-picasa-20121011-signed.zip
Alpha1 Download
Download Link
http://techerrata.com/file/cm/encore/alpha/cm-10-a1-encore-fullofbugs.zip
MD5
d5345b886d9825ef7a8fd8a36f70acb2
Local Manifest used to build Beta1.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/" name="gh" />
<project name="NookieDevs/android_device_bn_encore" path="device/bn/encore" remote="gh" revision="jellybean" />
<project name="NookieDevs/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="gh" revision="encore-omap3-3" />
<project name="eyeballer/proprietary_vendor_bn" path="vendor/bn" remote="gh" revision="jellybean" />
</manifest>
About Nook Color hardware revisions ...
In our efforts to debug problems people are seeing with our ROMs, we've encountered several different hardware revisions of the Nook Color floating around. We're not entirely sure how many different variants there are or what exactly the differences are, but it's very possible that these differences are relevant to bugs that only some people are seeing.
With that in mind, I'm looking to collect some data. If you could provide the following information from your device, whether or not you're experiencing a problem with CM10, it'd be very helpful. (I'll try to summarize the data received below as well, for reference.)
eyeballer has kindly set up a survey form for you to fill in, so that it's easier to sort through all the data: http://tinyw.in/I4OJ (if this doesn't work, try https://docs.google.com/a/teamw.in/...mkey=dHFhRDR5dzdVd3hfSTBvSnpjYVpna3c6MQ#gid=0). The instructions on how to get the requested information are in this post.
All of the lines below which look like
Code:
# command
are commands to be typed into a root shell, without the leading #. You can get a root shell in two ways: (1) connecting your tablet to a computer with adb installed and running "adb shell" from the computer, or (2) opening a terminal emulator on your tablet and typing in "su" (you may need to enable root access under Settings->Developer options first).
Motherboard serial number:
Code:
# cat /rom/devconf/MainboardSN
[you'll get a code [STRIKE]starting with "QI",[/STRIKE] such as QI13M9H72ZY (my device)]
Manufacture date:
Code:
# cat /rom/devconf/DateManufactured
[you'll get a date in American MM/DD/YYYY format, like 03/26/2011]
The motherboard SN and manufacturing date will help us establish when each variant might have been manufactured, and might eventually (with some luck) help us distinguish between variants.
CPU revision: The OMAP3621 chip at the heart of the Nook Color has gone through a handful of revisions to fix design defects (as nearly all CPUs do). We have to work around some of these defects in software when they're present, so it's helpful to know which variants are out there.
Code:
# dmesg
You will get a lot of output, but somewhere within the first 25 lines or so, you should find a line which looks like this:
Code:
<6>OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
(If you don't see it, reboot your Nook Color and try again -- if your device has been on for a while, older messages in the log will be dropped to make room for newer ones.) The code starting with "ES" is the revision number (1.0, 1.1, and 1.2 are documented).
(Shortcut: if you don't feel like sorting through all the output, you can run (on the tablet)
Code:
# dmesg | fgrep OMAP
which should show you the line above without some of the other noise.)
Touchscreen type: We know of two different types of touchscreen controllers shipped with Nook Colors, the Cypress Semiconductor "cyttsp" controller and the FocalTech "ft5x06" controller. Both should work, but they use different drivers, which probably have different bugs.
Code:
# dmesg
Some considerable way down from where you saw the OMAP chip revision, you should find output from both touchscreen drivers trying to load:
<6>cyttsp_init:Cypress TrueTouch(R) Standard Product
<6>cyttsp_init:I2C Touchscreen Driver (Built Oct 8 2012 @ 04:18:16)
<4>cyttsp:Reseting TMA340
<4>cyttsp:Start Probe 1.2
<4>
<4>cyttsp::found BL, Overriding maxx & maxy
<6>cyttsp_initialize:cyttsp-i2c: Register input device
<6>input: cyttsp-i2c as /devices/platform/omap/omap_i2c.2/i2c-2/2-0022/input/input2
<6>cyttsp_initialize:Setting up interrupt 259
<6>cyttsp_initialize:cyttsp_initialize: Create sysfs_group successfully!
<4>cyttsp:Start Probe PASS
<6>ft5x06_init() - FT I2C Touchscreen Driver (Built Oct 10 2012 @ 01:24:32)
<3>can't get ft5x06 xreset GPIO
Click to expand...
Click to collapse
Obviously, the driver for the chip you don't have will fail to load. (In this example, the ft5x06 driver fails to load, so I have a cyttsp touchscreen controller.)
(Shortcut: You can also run
Code:
# dmesg | fgrep ft5x06_probe
You'll get a bunch of log messages if you have the ft5x06 touchscreen; if you have cyttsp, you'll get no output at all. Thanks to bowguy for the tip.)
What we know so far (we think):
About 75% of devices out there have OMAP36xx revision ES1.2, with the rest (so far, early-production models built January 2011 or earlier) having ES1.1. (Not all devices built in that timeframe have ES1.1 cores, though.)
The vast majority of devices have the cyttsp controller (present on devices built through at least mid-2011), but more recently built devices have the ft5x06 controller (also used in the Nook Tablet), as do some earlier builds which were later refurbished. Most of us who hack on the device have cyttsp touchscreens, so our kernel isn't as well-tested on ft5x06 devices -- feedback is much appreciated!
Motherboard serial numbers appear to all start with QI and are roughly sequential; no other structure seems apparent as of yet. There appear to be at least two different motherboards -- "QI", which most devices have, and "A6", from some devices made after mid-2011.
First non dev? Can't wait to flash this, great work fellas!
:good:
Fantastic guys! This is a big day in the life of Nookie...
I would install right now, BUT, is the download link correct? Doesn't look right, and gives an error.
Thanks to you all.
Derek
Sent from my ASUS Transformer Pad TF700T using xda premium
thanks fellas, cant wait to flash this tonight and check out all the hard work thats gone into this.
derekr said:
I would install right now, BUT, is the download link correct?
Click to expand...
Click to collapse
Fixed!
derekr said:
Fantastic guys! This is a big day in the life of Nookie...
I would install right now, BUT, is the download link correct? Doesn't look right, and gives an error.
Thanks to you all.
Derek
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
-somebody- said:
thanks fellas, cant wait to flash this tonight and check out all the hard work thats gone into this.
Click to expand...
Click to collapse
Butcher98 said:
First non dev? Can't wait to flash this, great work fellas!
:good:
Click to expand...
Click to collapse
Link is fixed on Post 3
Downloading. Can't wait to try it out. Thanks guys!
Flashed immediately. No problems at all so far. Very exciting! Thanks for putting this out!
Works great! Comparable to my N7 sometimes. Just got to get the SOD's worked out. Any tips on reducing them?
Sent from my Nexus 7 using xda premium
Waiting for my NC to charge! Very excited!! And I must say...HANDS DOWN the best, most thoroughly sell explained OP I have ever seen...well done!!!
Sent from my SPH-D700 using xda premium
:highfive:
Great stuff thanks.
Just a quick question, since Opengl is off does that mean that flash player won't work, or is it only Opera that will like in CM9?
Thanks again.
In the OP thanks:
..."Quick ups also go to Ada Lovelace, Alan Turing, Benjamin Franklin’s key maker, and the late Dennis Ritchie."...
Well said, on Ada Lovelace Day (Oct. 16) celebrating women in science and technology. She's a heroine of mine
They are all heroes! Well, the timing missed by about 90 minutes here, but it was Oct. 16 in other parts of the world...
I just realized that because my Nook has a real flaky power button, I'll have to wait 'til the "n" button works for wake-up.
It takes about 20 presses to turn on right now. Bummer.... was so looking forward to CM10.
derekr said:
In the OP thanks:
..."Quick ups also go to Ada Lovelace, Alan Turing, Benjamin Franklin’s key maker, and the late Dennis Ritchie."...
Well said, on Ada Lovelace Day (Oct. 16) celebrating women in science and technology. She's a heroine of mine
They are all heroes! Well, the timing missed by about 90 minutes here, but it was Oct. 16 in other parts of the world...
I just realized that because my Nook has a real flaky power button, I'll have to wait 'til the "n" button works for wake-up.
It takes about 20 presses to turn on right now. Bummer.... was so looking forward to CM10.
Click to expand...
Click to collapse
There's a setting in CM10 for volume button wake. Enable that, and you're good to go
bcvictory said:
Works great! Comparable to my N7 sometimes. Just got to get the SOD's worked out. Any tips on reducing them?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Which touchscreen do you have?
Thx!
Good thing I recharged last night. Downloading now!
Update01: Finally works with an ICS hotspot out-of-box without having to run terminal ping on the background! Huge thanks just for that!
GREAT WORK guys!!!
On another note, will this be the same thing as my own builds from cm source plus fattire's local manifest changes?
Once again, respect!