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!
Related
Good news guys!
Jerpelea announced the eminent release of Cyanogen RC2 for the X10.
http://forum.xda-developers.com/showpost.php?p=7370940&postcount=91
So to keep the dev only thread clean, please post your questions, problems or comments here.
Update 2010-07-28:
jerpelea said:
with actual state of spl it boots then crashes
you can play a lil with the new kernel included into package
build 0005
http://hotfile.com/dl/57983756/408a452/0005.rar.html
Click to expand...
Click to collapse
Great news and great work by the devs!
I think that this release will be internal i.e. devs only. We never got RC1 so why should we expect RC2?
you got that wrong guys
Froyo is ready in RC2 for X10 this is not equal to : "the bootloader is finally hacked"
So stay calm please
Regards
Bin4ry
Man i got excited for a minute there. Looks like back to waiting.
Sent from my X10i using the XDA mobile application powered by Tapatalk
Damn it!
Still good news that it'll be ready for when it does get hacked.
no more wet dreams.
ill stick it once it gets useful fr all...
its nice to see progress at least, I thought they hit a brick wall a couple days ago as they stopped posting in the dev thread. It may be a while till we see a bootloader hack thats friendly for us but its hard to determine since we're not devs. As I understand it, the actual ROM is partly ready but it'll have a number of bugs etc still and only devs who can actually load it on through manual code will be able to test it out I think. It may be that its actually just a virtual rom to be loaded onto the SDK under the same conditions as the x10 to be tested by the developers. I THINK. As I said I'm not a developer so take my words with a huge grain of salt because I might be completely wrong.
PLS Can we get a little more detailed information.
instigator008 said:
I think that this release will be internal i.e. devs only. We never got RC1 so why should we expect RC2?
Click to expand...
Click to collapse
PLS Can we get a little more detailed information.
If the RC2 will be ready tomorrow then it means that RC1 was launched on the device?
irkkso said:
PLS Can we get a little more detailed information.
If the RC2 will be ready tomorrow then it means that RC1 was launched on the device?
Click to expand...
Click to collapse
what is the meaning of rc1 and rc2
RC = Release Candidate
irkkso said:
PLS Can we get a little more detailed information.
If the RC2 will be ready tomorrow then it means that RC1 was launched on the device?
Click to expand...
Click to collapse
No no no... you got it all wrong.
RC2 is the latest release of CyanogenMod and work has been carried out on this to "Port" it over to the x10. There wasnt any point in working on RC1 if CM RC2 was out.
rc = release candidate
a software enters rc usually after testing phase(alpha-beta-etc...)....
j4mm3r said:
Good news guys!
Jerpelea announced the eminent release of Cyanogen RC2 for the X10.
http://forum.xda-developers.com/showpost.php?p=7370940&postcount=91
Click to expand...
Click to collapse
So Jerpelea made a edit on the post... which is something pretty much expected as the bootloader is not cracked. So my guess is that this is going to use the spl loader module to boot into the CM kernel which has been ported for X10? Just a guess...
Can somebody explain to people like me who are new on android what does the cyanogen mod, is it just a firmware ?
What is called "kernel" in android and is it "modable" and if yes, why would it be ?
The answers...
Vilam said:
Can somebody explain to people like me who are new on android what does the cyanogen mod, is it just a firmware ?
What is called "kernel" in android and is it "modable" and if yes, why would it be ?
Click to expand...
Click to collapse
Hi Vilam, those are interesting questions, let me see if I can address those to your satisfaction.
The term "firmware" being distinct from "software", in my view is rapidly loosing its ability to be distinguishable from the latter. Essentially it refers to those parts of the executable code on a computing machine which remains unmodifiable or rather "burned in" to the circuitry. With the advent of modern flash memory storage, which is rather malleable compared to the earlier variants which existed, it is rather easy to change and update the machine code which is stored therein.
In other words, you might still refer to firmware to be part of the "software" which runs on a computing device which is not modifiable at run-time. In terms of a smart phone (which are rapidly becoming general purpose computing devices anyways), the firmware forms the basis of the software execution environment which affords the so called "apps" to run and provide either ever so innovative and useful functions.
Coming around to the point about Cyanogen mod... its a combination of firmware and software (if you still want to make that distinction that is). It in conjunction with helper pieces of code like the bootloader et. all. can completely replace the components that your phone was originally shipped with. Since these are Android phones that we are talking about, Cyanogen is derived from the same code base that Google officially uses for their various releases of Android. It is important to note that Android is a mobile application and phone platform rather than something which can easily be classified as "firmware" or "software"
Next question of yours about the "kernel". Not knowing what your level of familiarity of Linux or its derivatives is... let just say that Android is essentially like a distribution (or distro) of Linux designed specifically to run on mobile devices. As is the case with other Linux distros, they are formed around a core known as the "kernel". The "kernel" forms the core of the operating system which provides a homogeneous execution environment for the execution of various applications, which are in-turn pieces of software which are designed to provide the functionality which can be useful to the end-user. So all the so-called "apps" require the kernel to provide some services which are abstracted out enough so that the application programmer does not need to care about the really really low level stuff that actually has to go down if you actually want your device to do something. Hence the application programmer concentrates on the "high level" stuff, which is the functions that are actually going to be useful to the end-user!!
Like all modern computing platform, Android is a layered architecture and the "kernel" forms one of the most inner most parts of it (hence the name "kernel").
The linux kernel running Android for the X10 is already modifiable. People have been successful in compiling software modules called "kernel modules" which can be added to a running kernel and add functionality to it (this of course requires super user privileges or "root" access on the phone).
With the future pointing towards the capability of running mods like Cyanogen and the likes, the possibilities of modding and hacking are endless. Cyanogen, like the original releases of Android from Google are completely open source, so one can tweak almost all aspects of the phone functions. The possibilities are only limited by ones own imagination.
PS: I think I had too much beer and it makes me practice my English composition skills... hic!
Thank you very much for this clear explaination !
Please let me explain in newbie wordings. This is for ppl who can't understand what's going on at all.
1. A firmware likes an OS, if not exactly is. Windows, Linux, DOS, OS X are all OS. In android phone, there is merely one OS, which is Android.
2. Android is Linux.
3. Linux has a kernel, which is the main program. Without this, your machine can't run. On top of kernel, there is other software (movie player/web browser). Kernel + other software = distro (distribution).
4. Windows has different distro like Home, Professional, Ultimate... Linux has also different distro, so does android. One of them is CyanogenMod. The other could be Xperia X10 original.
5. Android is open source, so everyone can mod it. But that does also means someone can remove functions from it, one of them is Sony Ericsson, which locks your Xperia X10 for professional use.
6. While it is easy for us to upgrade Windows XP to Windows 7. It is difficult to install OS X from Windows XP. This is the same case for Android, it is easy to upgrade our Xperia X10, but it is not that easy to install CyanogenMod. There are honorable person working on this issue.
7. Why CyanogenMod? Because it is faster or it does not lock function like original Sony distro.
8. Just like installing OS X on regular PC, installing CyanogenMod may brick your machine. Much worse, Sony will definitely don't get your X10 repaired. So think if you need that extra function.
This thread is meant for discussion of the in progress Kit Kat port for the Nook Color.
Updates
If you want updates on the progress you can check this post and fattire's post immediately folllowing this. We'll both be posting updates periodically here.
You can also follow me on twitter @dalingrin
You can follow fattire @ fat__tire
Please don't ask me for ETAs or status updates. I will post them as I post them
Source code
Device source code will be temporarily hosted on fattire's github @ http://github.com/fat-tire/android_device_bn_encore
Things to expect
Nothing
Things not to expect(for now)
*Fully accelerated composition of the UI - this is not likely and may be dependent on 3rd party closed source EGL libs getting updated
*Accelerated video playback and overlay - This has changed quite a bit and may take some time to get working
*Polished release soon - Don't ask, don't tell
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE 11/24/13 -- So CM 11.0 is out and building nicely on Nook Color. Look here for the link to the build instructions. If you are building CM 11, you will probably want to use cm-11.0 as the name of the branch when initializing.
STATE OF THE UM, STATE OF THINGS
So I was curious how many noob types, who always beg for nightlies and builds and stuff-- I wondered if they (you?) could be encouraged to learn and get involved in the process of building Android. Which, as I've expressed in an infamous ramble, I think is important to the future of our culture and how it it deals with technology-- and who will control it. So I asked normal non-dev people to try building-- to give it a shot.
I think the experiment, which quickly became OUR experiment, has been a massive success. Far beyond what I'd imagined. Hundreds of people have gotten off their asses-- many of whom had clearly never touched Linux or a compiler before, and most were successful in building CM9/ICS from scratch.
That is not a small deal. And no, it's not just following a list of instructions by rote. People had to think about and solve a million different problems-- installing VMs, updating packages, choosing linux distributions, understanding the command line, etc. Scary stuff if you've never done any of these things before.
So it's been a month or so now, and I think we've reached the stage where aside from minor enhancements and fixes, the build looks pretty sweet. The major stuff is there and working. Yeah, DSP/hardware-accelerated video is something we're going to have to wait for TI to add to their omap3 repositories, and there are likely other things wrong. I've heard rumors of sleep-of-deaths or quicker-than-usual battery consumption, etc. There are numerous things to be fixed, but these are all issues that may or may not be worked out over time... As major new enhancements come to the CyanogenMod project, they will come to the encore version, and your build, automatically.
No secret links this time. As before, I'll spell out the bottom line explicitly for ya here in the middle somewhere. And I'll even underline it.
I hereby decree, in so far I am able, my humble request for "no posted builds".... is ended.
Back to your regularly scheduled forum. Go to it.
I encourage you to pass any valuable improvements you make to the code "upstream" via the gerrit review system at review.cyanogenmod.com for inclusion in the main CM project. You already know how it works. And some, God love ya, have already started. Not everything you submit will get accepted, but it's a good way to "pay it forward". And in the same vein, consider helping someone on IRC. Or be a big brother or big sister. Or donate blood. And to quote Steven Soderbergh, or whomever, you don't have to brush ALL your teeth, just the ones you want to keep.
Thanks as always to dalingrin, keyodi, nemith, verygreen, arcee, deeper-blue, unforgiven512, the gang on irc, and the CM Team generally for keeping this fun. And thank YOU for the lulz, Internet.
ft
Remember, there's NOTHING quite like running your own build, piping-hot, and fresh from the oven.
----
I am also releasing a first pass at a how-to-build walkthrough. It is available here:
walkthru (rough draft)
This doc will be updated and evolve with your input. It is meant to help people feel confident that they can build an operating system from scratch, and hopefully encourage them to participate, learn, and even make contributions.
If you need assistance, you must rely on each other.
Here is an equally unreliable clockworkmod, v5.5.0.4:
uRecRam
You may be asking, where is the issue queue? There is no issue queue. You are on your own here.
Recent automated builds (unofficial, unsanctioned, untested, uneverything else) from Forum member Samiam303 is here.
-----------everything below this line is sorta old and outdated--------------
So there's apparently been some bit of controversy related to my request that people try to build themselves rather than someone posting a pre-made update.zip file. Let me go more into detail about what this experiment is about, at least from my perspective. But first, I do want to thank everyone for respecting the request so far-- I know it's not the traditional way of doing things, but I think it's been very fruitful and personally rewarding to see so many people who have never built jack before take on a project like this and be successful. I've received an enormous number of messages, both PMs here as well as in IRC, to the effect that this finally got them to try to build for the first time. It's introduced many people to actually using Linux, others may be having their first encounters with the command line, or git, or looking at source code, or learning about the build process in general. Whether or not the majority go on to become "devs" is irrelevant-- what I have been trying to encourage is curiosity and experimentation, and most of all a deeper understanding that your phones and "ereaders" are in fact full-fledged computers, not "appliances" or limited-purpose devices that others get to control. It's your property, and it can do a lot. There is an effort underway to discourage people from thinking of their devices this way or discouraging them from experimenting and learning with them. This IMO is an extremely harmful practice-- take a look at Cory Doctorow's recent speech on this subject. I could go on and on, but it seems important enough to me to make this request, and hopefully some of you are even subconsciously appreciating the awesomeness of what potential these general-purpose gadgets will have on society. So that's a lot of philosophizing, but there you go. And while I'm not naive enough to think that plenty of people aren't trading the file "under the table" at it were, for a variety of reasons, I do think that in a way they're cheating themselves; those who give building a shot are finding that learning is a reward unto itself. Those who are persistent, who pay attention, who don't give up, not only get a build at the end, plus the experience of doing it, plus the knowledge they picked up along the way-- they also discover things in the most unexpected of places, as in the link in the period at the end of the third sentence in this post. And while there's been some discussion of what a "dev" is and whether or not this is a gateway to bigger and better things, all I can assume is that if 5-10% of the people who built are intrigued enough to take it a step further, and maybe a step further than that... then we might end up with some new devs who appreciate the value of open source and whose contributions we can look forward to with eagerness in the future. Plus-- it's more fun this way.
I do hope this sounds good to everyone. If you understand what this post is about- no need for long, drawn-out elaborate responses... a simple "I got it" will do.
More source is forthcoming... Thanks to dalingrin, arcee, keyodi, nemith, Scepterr, unforgiven512, etc. Oh, and shh.
--------------------------
update-cm-9.0-0-encore-emmc-sneakpeek2-fullofbugs.zip
md5: 536d589c59ea5711a17a3d976f0638fa
update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip
md5: 85294ad91e2601beb737cf723b9fb9d6
(note this URL is likely to change)
Note: You are advised NOT to try to install this. This update.zip will **overwrite** as in erase whatever data you have on your emmc, so if you are trying this, you are advised to back it up first so you can recover. Install entirely at your own risk, and do a factory wipe first. This software is likely to be terrible and cause problems including permanent data loss, hair loss, and/or the destruction of your property and the death of your pets. You assume all risks involved in your use-- or even attempted use-- of this file. I disclaim any and all responsibility for your decision to try it.
*** Really. This build is buggy. It is a work-in-progress. It is only a snapshot of where things stand right now, and it's possible it'll never go further. ***
here's what's working:
* bluetooth (pairing/file transfer only confirmed)
* wifi (full it seems but it's brand-new to the kernel so who knows how stable anything is)
* backlight
* accelerometer
* improved stability (but not perfect)
* gapps
* setcpu/overclock
* real data usage info (not stubbed out)
* battery levels/charging
* physical menu button
* touchscreen
* 3d games
* usb gadget in kernel (ie, mounting your sdcard to your computer)
* screenshots
* build system (to auto-create update.zips)
* sound
(note: for all the above features, you must build yourself! See below for rationale & more)
For sure not working yet:
* video
* full 2d acceleration (esp on complex web pages)
* and much much more
These things may/may not be added at some point in the future. You should have no expectations that they will. Anyone who asks for an ETA for something or other gets collectively stoned by the crowd.
I'm sometimes on #nookcolor in freenode.
Thanks to keyodi, unforgiven512, arcee, toastfch, d0nk`, dalingrin, nemith, the rest of the cm team/TD, and anyone else who I've forgotten. We stand on the shoulders of giants.
MUST READ:
Why there have been no additional zips posted lately.
How to use Gerrit (the CM9 review system)
how to make an update.zip
[*]beagleboard patches
Again, don't install this. And please don't "rom" this (as in change the font or background) and then ask for donations for your "hard work". This is a preview of a work in progress, not a final product, and it's not meant for people to use day-to-day. Don't be a ****. Thanks.
--------------------screenshots---------------------
About screen, wifi scanning, & bluetooth....
I'm no dev so can't help.
But thanks a ton. You'll give a new life to the NC!
this device looks sexy, how is performance(compared to the first honeycomb port) and any ideas on how we can get off the legacy hack?
luigi90210 said:
this device looks sexy, how is performance(compared to the first honeycomb port) and any ideas on how we can get off the legacy hack?
Click to expand...
Click to collapse
Performance is hard to tell without any apps on it really and with the legacy hack being goofy. Dalingrin's going to fix the ts driver tomorrow he says. It needs to be updated for anything close to usability. I think though it's not too far off from cm7 but again *REALLY* hard to say without having something to run on it.
I did notice that if you put a background on the screen it only stays for like second before disappearing. No idea what that's all about.
Update:
So update on progress tonight
* misc fixes
* got wifi working for keyodi
* got glx working for keyodi
* fixed bluetooth pairing again. Ran into trouble trying to send a file connection refused (111) or something like that.
* got freecpu working, needed to chmod 4755 /system/xbin/su and also add Superuser.apk-- but now overclocked to Dalingrin's cm7 settings. It feels pretty good.
(that's actually set to highest stepping but it's not currently maxed out)
* quadrant runs-- looks fast to me-- but bombed out on the network part at the end:
E/c*.a*.q*.c*.c*.Abstrac*( 4126): Failed to retrieve benchmark score
E/c*.a*.q*.c*.c*.Abstrac*( 4126): java.net.SocketException: socket failed: EAFNOSUPPORT (Address family not supported by protocol)
So I don't have a score. Not that Quadrant is particularly valuable. but the staircase works, the planets spin, etc.
Prolly won't work on it most of tomorrow.. just sayin'. Dalingrin will tho hopefully and keyodi too.
BTW, dalingrin-- temporary fix for wifi: assuming you use WPA-PSK, push this into /data/misc/wifi/wpa_supplicant.conf as the default in the device needs to be fixed manana:
Code:
ctrl_interface=tiwlan0
update_config=1
network={
ssid="your_ssid"
psk="your_password_in_plaintext"
key_mgmt=WPA-PSK
priority=1
}
Finally, if recovery.c tanks out, it's the last commit I made tonight. Sorry. I didn't think it was going to build it. Just back out changes to that file.
Yay!
Ian
sent from my ereader
Fantastic work. Didn't thought quadrant would run fast this soon. If wifi, touchscreen and 3d work, we have the most important things working (save for ui acceleration). I don't even care much about sound.
Looking forward to the first kangs =)~
Sweet! Lookin' pretty good. I hope the binaries for the UI acceleration get updated. Has the nook tablet source and files dropped yet? I seem to remember the NC and nook tablet having similar video hardware. Could be wrong. Are those binaries in that tablet as well?
dalingrin said:
Things to expect
Nothing
Click to expand...
Click to collapse
Noted, but that said I love this kind of technical tinkering and knowing this is being done is awesome. Looks pretty slick, I look forward to seeing how this develops.
no test zip? I would like to test, Im not one of those people that wont reprt back, i will tell what i find wrong
just wondering, will this truetouch driver update (https://github.com/martinezjavier) be incorporated and will it improve the screen sensitivity, esp. around the edge, for the nook? thx.
i'm excited!!
thanks in advance for all the hard work!!
I've only just started noticing the lack of activity in this device's community, so while I would love to tinker around with ICS on my Nook I understand how it may not a very big priority for developers. Do what you guys can with the knowledge, technology, and time you have and maybe I'll get new software to play with, but maybe I won't. This device has already been made a far better device than B&N intended it to be anyway.
Thanks for all the current and future work you guys devoted to this device
Sent from my NookColor using Tapatalk
Whoareyou said:
no test zip? I would like to test, Im not one of those people that wont reprt back, i will tell what i find wrong
Click to expand...
Click to collapse
Finding whats wrong isn't a problem right now, which is exactly why they didnt release flashable zip file. They did however post a link to the source, which if you know how to compile that, you know how to get it running on your device and may actually be of some use to the devs in getting other things working.
gamer.pro.2000 said:
Sweet! Lookin' pretty good. I hope the binaries for the UI acceleration get updated. Has the nook tablet source and files dropped yet? I seem to remember the NC and nook tablet having similar video hardware. Could be wrong. Are those binaries in that tablet as well?
Click to expand...
Click to collapse
The nook tablet uses an OMAP4 es ("enhanced security") from Texas Instruments that has a signed bootloader, which is checked on boot at the hardware level. The signed bootloader (u-boot) in turn checks the signature of the kernel and the ramdisk. Which means, fwiw, that you can't easily replace the bootloader or kernel (or basic startup sequence in the ramdisk) without it being signed by Barnes & Noble.
That said, people have run stuff "around" the existing kernel/ramdisk as nemith has done with cwm. Or you can just run apps you want within userspace (ie, using their kernel/ramdisk) by rooting Android with Zergrush and then installing the market or sideloading or whatever as several threads on this site tell you how to do. There were also several articles on this recently.
Interestingly, the signed kernel does load unsigned kernel modules, meaning a specially-crafted module can theoretically be written to "kexec" (ie, run) a 2nd, unsigned kernel/ramdisk "from the inside" of the kernel. That "second boot" possibility would facilitate the running of alternate OSes, and there have been attempts to do this with the Motorola Milestone. And finally, if anyone finds an exploit in uboot (such as improper validation of input, say while it reads bootcnt or bcb files or something), this too might also be another way to get a "normal", unsigned kernel/ramdisk to run, and therefore ICS would be a lot easier and control would be restored to the owner of the hardware.
That said, a philosophical opposition to DRM has lead a lot of people I've talked to to just say "F the nook tablet" and not purchase one in the first place. Dunno.
unsivil_audio said:
Finding whats wrong isn't a problem right now, which is exactly why they didnt release flashable zip file. They did however post a link to the source, which if you know how to compile that, you know how to get it running on your device and may actually be of some use to the devs in getting other things working.
Click to expand...
Click to collapse
I know how to, but my new laptop (HP Pavilion G6) dosent like linux well, and i cant get wifi to connect, networks show up, but it never connects So, i cant d/l the source ((
Great work so far.
Umm... is there a donation address set up so I can send a touch of... encouragement? Stimulus? Call it what you want. Beer fund.
fattire said:
The nook tablet uses an OMAP4 es ("enhanced security") from Texas Instruments that has a signed bootloader, which is checked on boot at the hardware level. The signed bootloader (u-boot) in turn checks the signature of the kernel and the ramdisk. Which means, fwiw, that you can't easily replace the bootloader or kernel (or basic startup sequence in the ramdisk) without it being signed by Barnes & Noble.
That said, people have run stuff "around" the existing kernel/ramdisk as nemith has done with cwm. Or you can just run apps you want within userspace (ie, using their kernel/ramdisk) by rooting Android with Zergrush and then installing the market or sideloading or whatever as several threads on this site tell you how to do. There were also several articles on this recently.
Interestingly, the signed kernel does load unsigned kernel modules, meaning a specially-crafted module can theoretically be written to "kexec" (ie, run) a 2nd, unsigned kernel/ramdisk "from the inside" of the kernel. That "second boot" possibility would facilitate the running of alternate OSes, and there have been attempts to do this with the Motorola Milestone. And finally, if anyone finds an exploit in uboot (such as improper validation of input, say while it reads bootcnt or bcb files or something), this too might also be another way to get a "normal", unsigned kernel/ramdisk to run, and therefore ICS would be a lot easier and control would be restored to the owner of the hardware.
That said, a philosophical opposition to DRM has lead a lot of people I've talked to to just say "F the nook tablet" and not purchase one in the first place. Dunno.
Click to expand...
Click to collapse
there have been talks about kexec on the nook tablet but from last i read is that kexec was disabled in the kernel so they were looking into 2nd init
ON TOPIC: i would donate if there is a donate link set up
Speaking for myself, I ask that you consider donating to the Electronic Frontier Foundation -- Eff.org -- they help keep our right to hack/jailbreak/root our own hardware safe and legal when corporations or government (usually under heavy lobbying from corps) try to infringe on it. And to that end, they also take up the legal defense of folks who are threatened or sued unfairly, such as just a few days ago with the security blogger who posted a spyware/rootkit warning and was hit with an intimidating takedown legal threat by the company he outed. They also fight laws that would censor or wall off parts of the Internet.
Donations to the EFF are tax deductable for US residents as well. They are one of the few organizations concerned with defending the Internet and digital-related interests of normal citizens and consumers, and a donation to them is really doing yourself a big favor.
Plus I think they'll send you a hat.
/end of pitch.
fattire said:
Speaking for myself, I ask that you consider donating to the Electronic Frontier Foundation -- Eff.org -- they help keep our right to hack/jailbreak/root our own hardware safe and legal when corporations or government (usually under heavy lobbying from corps) try to infringe on it. And to that end, they also take up the legal defense of folks who are threatened or sued unfairly, such as just a few days ago with the security blogger who posted a spyware/rootkit warning and was hit with an intimidating takedown legal threat by the company he outed. They also fight laws that would censor or wall off parts of the Internet.
Donations to the EFF are tax deductable for US residents as well. They are one of the few organizations concerned with defending the Internet and digital-related interests of normal citizens and consumers, and a donation to them is really doing yourself a big favor.
Plus I think they'll send you a hat.
/end of pitch.
Click to expand...
Click to collapse
im gonna look more into that but ill probably donate to that foundation
thanks for the info and i wish you luck with ics fattire
All checks and analysis were done to fresh installs only. No additional apps were installed except for those required for the security checks. The analysis is of currently active projects ONLY.
[ROM] Stock official firmware 20140513
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
CVE-2014-1600
Masterkey 9950697
Masterkey 10148049
USSD
Optimizations;
CPU Governor- Stock
SDCard Cache- Stock
OOM- Stock
SYSCTL- Stock
Network- Stock
Build.prop- Stock
BT Tether (watch>phone>internet);
Not working
BT Companion;
Not working
Kernel
Whatever kernel is provided.
[ROM] monxDIFIED™ SMART ROM ? SECURE + BT TETHERING v01-04
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
CVE-2014-1600
Masterkey 9950697
Masterkey 10148049
USSD
Optimizations;
CPU Governor- Stock
SDCard Cache- Stock
OOM- Stock
SYSCTL- Stock
Network- Stock
Build.prop- Minimal edits (Density config, Enable USB debugging, Disable debugging notify, Disable Bytecode, Disable sending data and logging)
BT Tether (watch>phone>internet);
Not properly working. Blue icon, no connection. Browser, Play Store, Voice Search, Google Now, Maps, etc., all fail to find a connection.
BT Companion;
Not properly working
Kernel
Whatever kernel you have prior to flashing is what you get.
[ROM] 07.06 EnSec STOCK Secure
(Continuation of the, Omate officially supported and approved, EnSec Project by Adam Outler, ClearD , Dees Troy, kuronosan and others.)
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
Masterkey 9950697
Masterkey 10148049
USSD
Optimizations;
CPU Governor- Tuned for lower CPU clocks under load to save battery
SDCard Cache- Tuned for optimal R/W speeds
OOM- Stock
SYSCTL- Tuned
Network- Tuned
Build.prop- Multiple edits (Density config, Network, playback, etc....)
BT Tether (watch>phone>internet);
Not working
BT Companion;
Not working
Kernel
Device specific matched kernel.
[ROM] mystery companion ROM
(if you don't know, don't ask. If you do know, don't tell)
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
Optimizations;
CPU Governor- Tuned for lower CPU clocks under load to save battery
SDCard Cache- Tuned for optimal R/W speeds
OOM- Tuned
SYSCTL- Tuned
Network- Tuned
Build.prop- Multiple edits (Density config, Network, playback, etc....)
BT Tether (watch>phone>internet);
Not properly working
BT Companion;
Mostly functional. Working notifications, working contacts sync, working remote app management, working speaker phone. Remote camera control not working,
Kernel
Whatever kernel you have prior to flashing is what you get.
How did you perform these security checks? I would like to check my own device.
Belarc
Bluebox
Dou Security XRay
Eeye
Secunia
SRT App Integrity
(all in attached zip)
USSD can be checked by going to ESET. You can also create your own page to check USSD and have it issue more aggressive codes, that what I've done. CVE-2014-1600 has to be checked by hand.
I'm still running EnSec + Operative Casual Edition 20140318 20140120 firmware ONLY!
It suits my purposes. The watch does what it's supposed to do. Tethering would do me no good unless I could tether to Maemo 5 or Meego Harmattan, which seems singularly unlikely.
Should I be worried and reflashing to something else, or is there no real point in a change from what I'm running right now?
EnSec STOCK Secure is a continuation and is based on newer firmware. There may be some sensor fixes and a couple of other things but other than that is very close to the original EnSec. Even though neither are perfect, both are still the best choice for security at this time. I personally would suggest flashing kuronosan's EnSec simply because it is a current and active release.
I have not tested the current version of monx ROM as every dev that was here prior to monx has quit releasing on xda for this device. I have quit dev support for the device on xda as well. You can pretty much thank monx for that.
So ClearD is gone, kuronosan is only providing support, and Dees wasn't surprised at what happened. Adam Outler is off on other projects. Any other dev I've talked to also found monx's kanging, games and insults a bit offensive. Enjoy your monx flavored icing as, from what we can tell, there is almost no real ROM work and mostly themeing. But what do we know, we are nothing but wannabe devs according to monx anyway.
You guys are so pathetic, NO ONE CARES ABOUT YOUR ISSUES
Focus on your own roms and ignore the rhetoric, because no one actually cares.
xcooling said:
You guys are so pathetic, NO ONE CARES ABOUT YOUR ISSUES
Focus on your own roms and ignore the rhetoric, because no one actually cares.
Click to expand...
Click to collapse
If you want to support somebody that stole Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and my work then calls the very same people whose work he stole fakes and wannabe's go ahead. Enjoy your easily hacked, unoptimized theme being passed off as a ROM.
And it wouldn't have been a problem if he had simply done the proper thing and asked and credited and not called everybody else a fake and wannabe. Not a problem though as of 8/7/2014 I have rescinded any and all permissions for xda and it's members to use my works, reference my works and mirror my works.
awesome, what a helpful person.
Thanks for standing by the community.
xcooling said:
awesome, what a helpful person.
Thanks for standing by the community.
Click to expand...
Click to collapse
Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and myself all work(ed) together on the TrueSmart/x201. Almost all work released on xda and any other forums, English or otherwise, is either based on our work, or authorized mirrors of our work. Some of our work is even in official firmware as we have worked with Omate since October of last year on issues.
I maintained an updated archive of almost every firmware and ROM released for not only the TrueSmart but the entire x201 platform and did security checks on all of it as well as look for any changes that may benefit all x201 users. I was also responsible for the core ROM work as well as being part of the early TWRP development and assisting the other devs with their work. Adam Outler, Dees Troy and kuronosan have all referenced my work at one point or another for their own works. In fact my work was called "amazing" by Adam Outer and "required" buy multiple other devs.
monx STOLE the work of at least five other devs and never even so much as apologized, then have repeated called other devs wannabe's.
And as far as the security and optimizations analysis, those results are after a peer review in which all the results matched. monx has called it b$ and and yet again called multiple devs wannabes.
I have better things to do than be part of a community that allows an ass like monx to kang, distribute an admitted trojan infected ROM and call multiple devs that came before him wannabe's and be a general ass with little repercussions.
In short. This section would not even be here if it was not for myself and a couple others. Also, the vast majority of the work, support and info would not even exist. This is not the first device I've done this for either. I did my part, and more.
xcooling said:
awesome, what a helpful person.
Thanks for standing by the community.
Click to expand...
Click to collapse
When several MTK developers (who have coded custom ROMs, kernels, and firmwares for MTK devices) tell you that your ROM has issues and you call them wannabes or haters, you really don't deserve any sort of adulation.
Besides, I'm still here providing support. Much of what I've discovered while working with other developers has become commonplace on future firmwares. I don't appreciate being called a "wannabe" or "hater" when calling people out on stupid mistakes.
XDA is not a place for Solid Snakes. It's a place for developers to work together. Not helping others is the peak of asshole-i-tude and accepting contributions to your work while not contributing to that of others is the antithesis of XDA.
Loosers attitude: give up and run away, complain because you were not given enough credit or fame
Winners attitude: would be to make your rom better, keep helping the community as you have done.
xcooling said:
Loosers attitude: give up and run away, complain because you were not given enough credit or fame
Winners attitude: would be to make your rom better, keep helping the community as you have done.
Click to expand...
Click to collapse
Cool story bro
So you support lying, theft of intellectual property and copyrights and acting like an 3 year old by calling people names? If that's the case then let me steal his work, improve it and call it my own vs trying fixing real problems like the ability to erase the IMEI with nothing more than a webpage or destroy the partition map with an email. Themes are the least of this devices problems.
Awesome. This device already had a bad rep with the devs for various reasons, then this monx guy swoops in to crush any remaining hope we had. Oh well, I'm thankful for what you guys have done, I actually enjoy my TS because of you guys, and that's all I could have asked for.
speedyink said:
Awesome. This device already had a bad rep with the devs for various reasons, then this monx guy swoops in to crush any remaining hope we had. Oh well, I'm thankful for what you guys have done, I actually enjoy my TS because of you guys, and that's all I could have asked for.
Click to expand...
Click to collapse
I'm still working on quite a few projects. Stay tuned. They likely won't end up here, but you never know.
Glad to hear kuronosan! I understand if you don't want to release it here, maybe you could PM me where you plan to release it or something? I've been interested in what you've been doing, and you have said some things in the past that sound promising (like news of KK and the like).
Thanks for sticking with it, and again to all the devs for all the previous work that helped us get as far as we are.
Lokifish Marz said:
Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and myself all work(ed) together on the TrueSmart/x201. Almost all work released on xda and any other forums, English or otherwise, is either based on our work, or authorized mirrors of our work. Some of our work is even in official firmware as we have worked with Omate since October of last year on issues.
I maintained an updated archive of almost every firmware and ROM released for not only the TrueSmart but the entire x201 platform and did security checks on all of it as well as look for any changes that may benefit all x201 users. I was also responsible for the core ROM work as well as being part of the early TWRP development and assisting the other devs with their work. Adam Outler, Dees Troy and kuronosan have all referenced my work at one point or another for their own works. In fact my work was called "amazing" by Adam Outer and "required" buy multiple other devs.
monx STOLE the work of at least five other devs and never even so much as apologized, then have repeated called other devs wannabe's.
And as far as the security and optimizations analysis, those results are after a peer review in which all the results matched. monx has called it b$ and and yet again called multiple devs wannabes.
I have better things to do than be part of a community that allows an ass like monx to kang, distribute an admitted trojan infected ROM and call multiple devs that came before him wannabe's and be a general ass with little repercussions.
In short. This section would not even be here if it was not for myself and a couple others. Also, the vast majority of the work, support and info would not even exist. This is not the first device I've done this for either. I did my part, and more.
Click to expand...
Click to collapse
Could just not ignore him,,, I only flashed the rom to see what the BT tethering was like out of curiosity (its very slow and useable)... will be ditching the ROM when I can get round to it... been annoying me all week I can't wear my watch has it just drains flat with this ROM....
speedyink said:
Glad to hear kuronosan! I understand if you don't want to release it here, maybe you could PM me where you plan to release it or something? I've been interested in what you've been doing, and you have said some things in the past that sound promising (like news of KK and the like).
Thanks for sticking with it, and again to all the devs for all the previous work that helped us get as far as we are.
Click to expand...
Click to collapse
I've personally approached monx about sharing work and ideas but he clearly has no intention of doing so; he has not responded but he continues to post in his topics.
That's fine. I'm only interested in continuing to better this watch and I have my own things to work on. As far as battery tweaks, I've managed to stabilize that (one of my users mentioned battery life 4-5 days with regular use) and I've managed to make quite a few gains.
Some of the things I would like to share involve making BT more stable and accessible across all ROMs, but again... he has no interest in sharing.
So while some of you hang from his beard as though Loki is the bad guy here, remember the ROM you love so much came from Loki's work and from the relationship I continue to foster with the CEO of this company.
But hey, no worries. Keep on praising a glorified themer who won't share his work with anyone else.
I'll be back here when I get my hands on the KK build.
Well, I'm gonna stick to my MotoACTV for a little longer. Planned on buying a TS secondhand, but hardware issues, software issues, and the current bout of drama, are very well keeping me from upgrading.
I understand your (TS devs) positions and motives. I know that there's a reason why you left the development on this device, and I'm glad you've simply quit development, rather than fighting and starting a riot.
However, with nearly all of the developers having abandoned the device, I don't see a good future coming from this.
I was hopeful through the kickstarter phase, and it's a pretty cool piece of tech, but, chances are, Omate will support it better than the community, until someone stands up, starts their own thing, and isn't afraid of getting their work ripped off.
Anyway, thanks for the development it did get, and all the cool things you guys do. If it weren't for you, this device would probably be dead in the water unless the OEM goes above and beyond to support it for a while.
Wear 24 DevelopmentContributors: @JaredTamana, @davwheat
Current Status: ActiveCurrent Kernel Status: Building, NFC driver working but still potentially WIPSystem ROM Status: Still WIP. Current task: collecting/compiling files, modifying .jarsTHIS ROM IS NOT YET AVAILABLE TO DOWNLOAD AS AN END-USER ROM
This project has a few goals:
- Bringing NFC/Google Pay support to Wear24 [Feasible, main goal]
- Bringing system updates to the Wear24, ie System H [Probably doable, second goal]
- Adding/fixing functionality in the Wear24 (such as new radio bands, no cloud icon, etc) [Maybe possible but needs more research, low on the list)
- Other projects are being considered for the Wear24, but no news on them at this time.
Links
Social
Wear24Dev Blog, periodic updates on this project: http://wear24dev.blogspot.com
Wear24 NFC Discord, open chat so users can see us develop in real-time! Also, tech support. https://discord.gg/8XyTeUC
Development
Wear24-NFC-Kernel GitHub, this is our source for building the kernel. Instructions for building it yourself are in the README. https://github.com/davwheat/Wear24-NFC-Kernel
Travis-CI Build Logs for Kernel: https://travis-ci.org/davwheat/Wear24-NFC-Kernel
Wear24-NFC-ROM GitHub, will soon contain the files needed to make an image/zip, depending on how we decide to distribute. https://github.com/davwheat/Wear24-NFC-ROM
JaredTamana's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/folders/1h6gz-oLMPZ90nwt7BLhWVgHii1DRCW5c
davwheat's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/fold...droid-msm-dorado-3.18-nougat-mr1-wear-release
tetra release for enabling NFC: https://forum.xda-developers.com/sm...ony-smartwatch-3-nfc-support-package-t3219713
NXP Setup Guidelines: https://github.com/NXPNFCProject/NF...r/AN11762-Android_NXP_NFC_Setup_Guideline.pdf
Special Thanks
janjan: Dev guidance
@bensdeals: Donor, help
@yochanmarquos, u/lerxi: Development help.
-- RESERVED -- Because you never know
Someone should have a TWRP backup handy with the images you are looking for. Correct me if I'm wrong, but all the images you require are inside a TWRP backup image.
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
Please. I beg you to make this happen. Thanks for even trying
I'm definitely interested in this. If I knew I could get Google Pay working on this device, I would definitely buy one. I'll happily throw a few dollars your way too, if you can release something that works.
Hoping I found it
JaredTamana said:
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
Click to expand...
Click to collapse
Is this what you're looking for? (Sorry, I'm not allowed to post url yet so just remove space before .com)
github .com/FlorentRevest/android_device_sony_tetra
My Wear24 just came in from eBay . It's a really good looking device. I might be able to help you test at some stage. Also willing to donate ducats if you get far enough. Good Luck :good:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
YTSec said:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
Click to expand...
Click to collapse
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
** NEWS **
Semi-daily updates will be going on this Blogger Page so I don't clog up the thread
http://wear24dev.blogspot.com
Hi, can i flash this rom to zte quartz 2017?
Hi, can i flash this rom to zte quartz 2017?
Eshal said:
Hi, can i flash this rom to zte quartz 2017?
Click to expand...
Click to collapse
Eshal, this ROM hasn't even been built yet. I cannot guarantee compatibility with your device because I'm not building for your device. You can try flashing whatever you like, but I'm not liable for your device.
This ROM is still in its first steps and I quite literally have nothing to release yet. I've just finished bringing backups over to my PC.
JaredTamana said:
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
Click to expand...
Click to collapse
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
YTSec said:
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
Click to expand...
Click to collapse
Glad to hear it! Make sure to read the main thread as to tips on how to do it. Use lots of heat, and don't forget the Y000 (0.6) screwdriver.
Kernel builds are now passing, and I've begun debugging the boot process. More info on the Blogspot
Sorry for the late reply, I'm just waiting on a toolkit that works on it, then I'll start ripping it apart to help out! Also, I got that new UI which is great.
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well
@JaredTamana Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS
Here's their GitHub.
VlitalityX said:
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well
Click to expand...
Click to collapse
Hiya! Sorry for the lack of updates. I've hit a wall with that Binder error. All documentation online seems to be about x86 machines and ranges from IO errors to SELinux errors. I've already tried compiling without SELinux in a few different ways to no avail. I've tried contacting development channels on IRC, but no one seems to have the answers I need (most times I don't even get a reply...)
I'm still brainstorming. I took a look at the kmsg from the stock build and there's a LOT being sent to logs there that isn't from my kernel. I'm not sure where to go next, and I don't want to go knocking on the door of every single developer that might know the answer. The problem is the Binder errors are so vague about what's causing the failed transaction that I can't even start to understand what's wrong.
yochananmarqos said:
@JaredTamana Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS
Here's their GitHub.
Click to expand...
Click to collapse
Thanks! I do remember seeing this. Problem is, if I can't even build a stock kernel, nothing else can be done. I need the device booting first before I can move to system changes.
Hi,
When I read the questions and guides, it seems the Surface Duo can be unlocked and rooted pretty easily.
So I was wondering why there is no custom ROM for this device which is, by all means, not perfect (it has a lot of flaws) but that I consider as at least a refreshing attempt to dig out of the "one glass rectangle touch screen" that we're now used to for years.
Is it beacause there's no love for the device ?
Or is it because Microsoft released absolutely no sources for the internal hardware ?
If there's anyone willing to try, I can offer build server to do it...
And contacts in a community to help iron out problems...
Regards.
Microsoft has indeed released the sources of the internal hardware, or, at the very least, some of it. I don't really know how to determine whether or not all of the drivers are included with the kernel source code. But they do have this kernel source code hosted on GitHub, under a combination of MIT, Apache, and GPL licensing, as well as full instructions on how to build the kernel. The instructions are located at microsoft/surface-duo-oss, and the scripts end up downloading from other microsoft/surface-duo-oss-* repositories. I've not actually tried to build this myself, and I'm not sure what you actually end up with afterwards, whether it is just a kernel, or if it also includes AOSP, and whether or not this can be included in the process of generating another distribution such as Lineage. But, I think this should at least be some information that can be used to at least start the process assuming anyone with existing experience is interested in starting this.
I have seen it expressed elsewhere that one reason people have not created a custom ROM is that android 10 does not have native support for multiscreen devices, while android 11 does. Meanwhile, Microsoft has only released android 10 for the device, and this includes the surface-duo-oss scripts as well, but that there is plans here soon (late September) by Microsoft release android 11 for the Surface Duo.
Fingers crossed! Looking forward to a robust desktop mode and multiple external monitor support like the regular Surface Pro does
Basically a phone that acts like a Surface PC when you dock at home or at work so you can actually work from the device like a normal Surface laptop and then fold and put it in our pockets when we're done working
I know this is an older post but I sure wish someone would go ahead and give me the dummy guide to flash their custom rom!! If anyone needs a duo that thinks they can make it happen I have a spare one..... The left screen is glitching in and out tho.