/e/
As always, you take responsibility for what you do to your phone. Don't go filing civil lawsuits against me if your alarm fails to get you up for work in the morning.
The Hell's An /e/?
"/e/ is a non-profit project, in the public interest. We build open-source mobile operating systems that respect users’ data privacy. We’re an international core team of experienced entrepreneurs, developers and designers, and a growing community of contributors." --taken from their website.
Basically think Lineage AOSP but instead of just leaving gapps out of it, they're trying to take it a step further and really give Google the finger. Their ultimate goal for the future is to make a mobile OS featuring an entire ecosystem (/e/cosystem?) that respects users' privacy and avoids the "big-companies-that-sell-your-data". They will have alternatives to the most popular Google services baked in: F-Droid instead of Google Play, something like Telegram instead of Google Hangouts, Lawnchair instead of a proprietary Google launcher, etc. As of the time I'm writing this message this is still really early on in the /e/ project though, so don't expect too much just yet.
What Works?
Exactly the same as what's in Lineage 16 for Payton, WITH THE ADDITION OF VIPER AUDIO (YOU NEED TO USE V2.7.X FROM MAGISK THOUGH)
What Don't Work?
There's no market for apps built in yet (or web browser) so be prepared to sideload your own APKs over ADB to get that stuff on for now, until I fix it in a new build
Where's My Source Code, and How'd You Build this?
Don't worry, this took me forever to find too. I used the v1-pie branch which is Lineage 16.0 based
Here's the roomservice XML I used so you don't have to manually add all the trees yourself
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_motorola_payton" path="device/motorola/payton" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_motorola_sdm660-common" path="device/motorola/sdm660-common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_kernel_motorola_msm8998" path="kernel/motorola/msm8998" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_external_bson" path="external/bson" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_system_qcom" path="system/qcom" remote="github" revision="lineage-16.0" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="lineage-16.0" />
</manifest>
To get the custom /e/ apps in your build you have to edit the portion of vendor/lineage/config/common.mk that talks about "Custom CM Packages". Go to /prebuilts/prebuiltapks for a list of folders' names you can add to this list. Note that not everything will add properly, and adding some things may mess up your ROM, so experiment at your own risk
Where's My Download Link?
MY MEGA BUILD FOLDER
I know some people don't like Mega but it's all I have to work with because my Google Drive is almost full and AFH won't accept me as a user to post all my crap up there. Please don't mirror the download links anywhere else without my permission either
Who Should You Give a Special Thanks To?
--The /e/ team (including but not limited to Gael Duval)
--All the guys here on the payton forums for their hard work in building the trees for this thing
--@bcrichster for showing me how to get the /e/ apps to build with the ROM on this thing so I don't have to steal from AOSP anymore
--@erfanoabdi for his excellent work maintaining Lineage 16 trees for Payton to get this thing stable
RESERVED
You are doing a great work. Keep up with your work. But unfortunately I can't be a part of this project and currently my phone is a daily driver. But once this project becomes stable I will surely try it out. Once again I salute your thinking of creating a new OS.:good:
Zeisthegeek said:
You are doing a great work. Keep up with your work. But unfortunately I can't be a part of this project and currently my phone is a daily driver. But once this project becomes stable I will surely try it out. Once again I salute your thinking of creating a new OS.:good:
Click to expand...
Click to collapse
It's not my OS that I made, eelo (or /e/) is someone else's idea. Their website is HERE if you want to look. All I did was port it over to the X4
And this OS is stable by the way. I've been using it myself for the past couple days and there's no problems at all. Not even random slow downs from what I can tell. If you can live without Google, this thing's good to go as-is
Lot of people on telegram group too can u post this on telegram pls
Thank you and the /e/ team for the hard work. I'll have this downloaded for now and will try it over the weekend and post some feedback.
Edit: I guess i won't be able to do that right now because Mega is blocked in my network. I'll try it out either when i have access to Mega or when someone mirrors the download in an accessible host. With the owners permission of course.
dhinesh_cool said:
Lot of people on telegram group too can u post this on telegram pls
Click to expand...
Click to collapse
Which telegram group, you need to be more specific than this or post a link
Helhound0 said:
Thank you and the /e/ team for the hard work. I'll have this downloaded for now and will try it over the weekend and post some feedback.
Edit: I guess i won't be able to do that right now because Mega is blocked in my network. I'll try it out either when i have access to Mega or when someone mirrors the download in an accessible host. With the owners permission of course.
Click to expand...
Click to collapse
I'd do all of this on AFH or Google Drive, but AFH won't let me in and my Google's almost full and I need it for other things. I'd do something like a Bittorrent with a hash but I've never been able to set one up properly before that actually works. Maybe I'll try again with my next build I'm about to do
jasonmerc said:
Which telegram group, you need to be more specific than this or post a link
I'd do all of this on AFH or Google Drive, but AFH won't let me in and my Google's almost full and I need it for other things. I'd do something like a Bittorrent with a hash but I've never been able to set one up properly before that actually works. Maybe I'll try again with my next build I'm about to do
Click to expand...
Click to collapse
Xda is not allow to post links here
There is Moto x4 official group on telegram u can post there,.
U can use sourceforge ,afh is take time to give access
---------- Post added at 04:11 AM ---------- Previous post was at 04:08 AM ----------
Lot of things going on our custom rom group (motox4_dev) u can join there too??
I will support it and therefore, as soon as I have time, I will put it prominently on my site. This project is really great!!
If you don't want it, just tell me.
https://www.motox4custom.com
MotoX4Custom said:
I will support it and therefore, as soon as I have time, I will put it prominently on my site. This project is really great!!
If you don't want it, just tell me.
https://www.motox4custom.com
Click to expand...
Click to collapse
Thank you for your enthusiasm! You can promote this in any way you want to (and I really do appreciate anyone that wants to do so) but please don't mirror any downloads anywhere else--link back to this thread for the actual link to get it, or my AndroidForums mirror of this thread whichever you'd prefer
I hope everyone's happy with my current build here, because I'm trying to make a new one but I'm having lots of issues. The primary one has to do with the "cryptfs_hw: Support devices use metadata as key" change included with Lineage 16, because /e/ here doesn't know how to handle that flag. Even when I manually remove it there's still other kernel problems and missing dependencies I don't know how to solve. Sorry for the delay, because I really wanted to make timely updates for this thing since Payton's device trees and everything are undergoing a lot of cool changes recently and I'd like you all to have access to them
jasonmerc said:
I hope everyone's happy with my current build here, because I'm trying to make a new one but I'm having lots of issues. The primary one has to do with the "cryptfs_hw: Support devices use metadata as key" change included with Lineage 16, because /e/ here doesn't know how to handle that flag. Even when I manually remove it there's still other kernel problems and missing dependencies I don't know how to solve. Sorry for the delay, because I really wanted to make timely updates for this thing since Payton's device trees and everything are undergoing a lot of cool changes recently and I'd like you all to have access to them
Click to expand...
Click to collapse
Hello, you can join the dev group at Telegram to get help.
Moto X4 Custom Roms
Keep this alive! I'm going to move over to this soon, do not give up or I will be sad.
I'm travelling, but I am going to fire this up and have a look at it soon.
A build actually built. Sent to the x4 telegram group for testing to ensure it actually boots
To outline what I had to do here, I had to do a real redneck way of fixing this that I normally would not recommend doing as it's not best-practice for this kind of thing. I synced the kernel from @SyberHexen (pie-base branch) and tried to build with that. It got past the weird fde flag part, but then failed at some other point. I then went to the roomservice xml and changed the kernel BACK to the normal lineage one, force synced with repo, then restarted a build with brunch payton WITHOUT RUNNING A MAKE CLEAN FIRST. It was at this point it was actually able to build all the way through. Well, it built to about 98% and had some random error, but then restarting with another brunch payton fixed it somehow. Anyway, hopefully despite this thing's weirdness it works for you guys. I'm excited to have eelo start working for this phone again
New build is up, according to the group it works just fine. Someone also flashed gapps with it and it worked... Google-infested eelo is too dangerous of a contradiction and should not be tried at home
This is a cool idea. im becoming more anti google by the month...they probably make a ton of money off of us in several other ways to where im ready to kinda ditch some of booble...keep up the good work I'll flash this soon and toy with it... im down to test if anyone needs
Sorry to do this so abruptly, but certain things were brought to my attention about this ROM and its organization. Granted, I knew this was pretty much nothing more than a reskinned Lineage, but apparently they've got some shady practices they participate in.
Because of this, I will be discontinuing all of my eelo builds, effective immediately. Read about it here: https://ewwlo.xyz/evil
jasonmerc said:
Sorry to do this so abruptly, but certain things were brought to my attention about this ROM and its organization. Granted, I knew this was pretty much nothing more than a reskinned Lineage, but apparently they've got some shady practices they participate in.
Because of this, I will be discontinuing all of my eelo builds, effective immediately. Read about it here: https://ewwlo.xyz/evil
Click to expand...
Click to collapse
This is interesting. I know dozens of developers from this forum that can do WAAAAYYY better than these people had they've been funded like this.. Such a shame.
From the same guys that brought you that PornAOSP joke from a couple years back, they're working on their own ROM designed to give a clean, minimal, google-free android experience. It's already out for some devices, it's called CleanOSP. When I get the time (and patience) I'll work on porting that over to the X4 here. Consider it the spiritual successor to eelo when it comes out
Related
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!
Any word out for Cyanogenmod for Moto Z?
TWRP Team has showed amazing support already building recovery for it
The Hardware is awesome, would be cool if CM 13 or 14 comes to this phone
I hope but I don't think so.
CM does have very few SD810/20 devices. We have to hope for an unofficial port.
I hope so too, the phone is still new to the market, lets wait until developers get their hands on it
The problem with Z phones is the mods and how easy/hard it will be to support mods in other than stock based mods. But I sure hope that simple mods like the battery mod will work eventually. All depends on the additional needed software. Are the "Moto stuff" downloadable and useable on other roms than stock? Or do other roms need to build the very own support all from scratch?
İ finally built working cm14.1
But so many things are not working
Like
Wifi
Brightness
Simcards
Camera
Mods(are you kidding me!)
And also drains battery so flawlessly
But other things working like:
Bluetooth
Fingerprint
Touch
...
I'm working on it until someone upload official stock firmware 7.1 but this device need more developer and I'm alone on this project
If someone can help me contact me to build more stuffs together
just registered to say i've got most things working (ish) here:
the github url slash motoz-2016/android_device_motorola_griffin (not going to spam a bunch of posts just to submit a link, derp)
only things broken in 14.1 are:
- weird battery life issues (it lasts quite a while, but sometimes certain tasks seem to drain it way down)
- radio doesn't recover if it loses signal (curse you elevators)
- no mods support
- camera (this was working in 14.0 and died when i moved to 14.1)
- generally odd little things.
I havn't had much time recently to work on it (hope to change that soon) but it's been a daily driver of mine for a few weeks.
on the mods side of things, all the kernel support for them is already released on moto's github. it's just a matter of us actually using it (my kernel actually builds the kernel modules but that's not quite enough)
if any devs want to help contribute feel free to contact. (sent you a PM @erfanoabdi)
erfanoabdi said:
İ finally built working cm14.1
But so many things are not working
Like
Wifi
Brightness
Simcards
Camera
Mods(are you kidding me!)
And also drains battery so flawlessly
But other things working like:
Bluetooth
Fingerprint
Touch
...
I'm working on it until someone upload official stock firmware 7.1 but this device need more developer and I'm alone on this project
If someone can help me contact me to build more stuffs together
Click to expand...
Click to collapse
can't wait to see that out
sebirdman said:
just registered to say i've got most things working (ish) here:
the github url slash motoz-2016/android_device_motorola_griffin (not going to spam a bunch of posts just to submit a link, derp)
only things broken in 14.1 are:
- weird battery life issues (it lasts quite a while, but sometimes certain tasks seem to drain it way down)
- radio doesn't recover if it loses signal (curse you elevators)
- no mods support
- camera (this was working in 14.0 and died when i moved to 14.1)
- generally odd little things.
I havn't had much time recently to work on it (hope to change that soon) but it's been a daily driver of mine for a few weeks.
on the mods side of things, all the kernel support for them is already released on moto's github. it's just a matter of us actually using it (my kernel actually builds the kernel modules but that's not quite enough)
if any devs want to help contribute feel free to contact. (sent you a PM @erfanoabdi)
Click to expand...
Click to collapse
Just to simplify things: https://github.com/motoz-2016/android_device_motorola_griffin
Not much of a developper, however I can host files and probably set up an automated build on some servers.
sebirdman said:
just registered to say i've got most things working (ish) here:
the github url slash motoz-2016/android_device_motorola_griffin (not going to spam a bunch of posts just to submit a link, derp)
only things broken in 14.1 are:
- weird battery life issues (it lasts quite a while, but sometimes certain tasks seem to drain it way down)
- radio doesn't recover if it loses signal (curse you elevators)
- no mods support
- camera (this was working in 14.0 and died when i moved to 14.1)
- generally odd little things.
I havn't had much time recently to work on it (hope to change that soon) but it's been a daily driver of mine for a few weeks.
on the mods side of things, all the kernel support for them is already released on moto's github. it's just a matter of us actually using it (my kernel actually builds the kernel modules but that's not quite enough)
if any devs want to help contribute feel free to contact. (sent you a PM @erfanoabdi)
Click to expand...
Click to collapse
oh thanks for your post, i'm ready, let's do it together
thanks again for your device tree :fingers-crossed:
Soon.
Sent from my XT1650 using Tapatalk
Any update guys..
Manish54 said:
Any update guys..
Click to expand...
Click to collapse
i was working on naught droid OTA porting. but no success
so came back to CM project
as @sebirdman shared his device tree that was big step on project now i made todo list on google docs : https://docs.google.com/document/d/14-SJ6NVgDSHSiGkqpWVkXCc6N79BydhMnnYJaA-Htqo
if i make it little more useful i'll share flashable zip in this forum :fingers-crossed:
erfanoabdi said:
i was working on naught droid OTA porting. but no success
so came back to CM project
as @sebirdman shared his device tree that was big step on project now i made todo list on google docs : https://docs.google.com/document/d/14-SJ6NVgDSHSiGkqpWVkXCc6N79BydhMnnYJaA-Htqo
if i make it little more useful i'll share flashable zip in this forum :fingers-crossed:
Click to expand...
Click to collapse
CM sounds a lot better than the OTA :laugh:
Many many thanks sirs!!!
CM 14.1 please!!
CM is on the way
(uploading rom to mega ...)
check this out :
sadly I have the droid version I can't use this I wish sunshine team would work on the moto z but they said they are not Is there any bugs on the cm14.1?
Can't wait to try it
erfanoabdi said:
CM is on the way
(uploading rom to mega ...)
check this out :
Click to expand...
Click to collapse
I thought CM would never come to this phone.... :crying:
hassanman1997 said:
Can't wait to try it
Click to expand...
Click to collapse
now you can try it :
http://forum.xda-developers.com/moto-z/development/rom-cyanogenmod14-1-moto-z-t3514432
I am surprised that you missed that or maybe I missed it here
I dirtyflashed it over a CM13 and it seems to work
testing now
here are the roms/links
on german x820 forum its clear #1
http://download.mokeedev.com/?device=le_x2
dont forget its without gapps so flash add them when you like google stuff
Se didnt miss it but thanks anyway. That ROM was deleted from xda due to the fact that some users that dont do anything else but complaining, and attacking the dev. The dev from mokee hás informed that hes not posting anymore ROMs in xda. Nougat included
What is the dif btw release n nightlies
nosidefcp said:
Se didnt miss it but thanks anyway. That ROM was deleted from xda due to the fact that some users that dont do anything else but complaining, and attacking the dev. The dev from mokee hás informed that hes not posting anymore ROMs in xda. Nougat included
Click to expand...
Click to collapse
Hello. You forgot to tell the full truth. The case is the dev was asked to release sources and he refused.
Regards Filozof71
Sent from my Le X820 using Tapatalk
Filozof71 said:
Hello. You forgot to tell the full truth. The case is the dev was asked to release sourced and he denied.
Regards Filozof71
Sent from my Le X820 using Tapatalk
Click to expand...
Click to collapse
Thats not true. He said he wasnt releasing the source in that day. Three por four days later he released here the source code
nosidefcp said:
Thats not true. He said he wasnt releasing the source in that day. Three por four days later he released here the source code
Click to expand...
Click to collapse
Incorrect. People were asking for the Device Tree used to build Mokee, which wasn't and still hasn't been provided. XDA isn't a place for you to download roms, it's a developer community. Pretty sure the device tree would have been converted from one that was available (Probably OP3) and not sharing it is disrespectful to every developer who has worked on it previously.
https://github.com/MoKee/android_device_letv_le_x2 is empty.
mikeysteele said:
Incorrect. People were asking for the Device Tree used to build Mokee, which wasn't and still hasn't been provided. XDA isn't a place for you to download roms, it's a developer community. Pretty sure the device tree would have been converted from one that was available (Probably OP3) and not sharing it is disrespectful to every developer who has worked on it previously.
https://github.com/MoKee/android_device_letv_le_x2 is empty.
Click to expand...
Click to collapse
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
ffboy2009 said:
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
Click to expand...
Click to collapse
Who's talking about rules? This is a community and communities have standards. You're free to do whatever you like but expect people to be unhappy if you disrespect the community.
ffboy2009 said:
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
Click to expand...
Click to collapse
First of all: THANKS for your ROMs. Second: i would really consider publishing the device tree, because there might be a few others who would like to contribute.
Although the Max 2 is a rather "specific" smartphone, which - outside of India and China - nobody really considers buying.
ffboy2009 said:
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
Click to expand...
Click to collapse
The Open Source rule and spirit. We share our knowledge and we don't hide it.
https://github.com/deadman96385/android_device_leeco_x2
https://github.com/AndroPlus-org/android_device_leeco_x2?files=1
I know is difficult to you to understand this. There must be a reason why you don't want to provide your sources.
http://forum.xda-developers.com/showthread.php?t=3494247
ffboy doesn't own anybody anything. He releases his ROM's for free, he doesn't force you to use them. Many rom developers don't release their source code/device trees, one reason is that people could take there hard work getting everything to work and use to build their own ROM's and get donations from them without doing any hard work themselves. Even my grandma can build a ROM when eveyrthing is handed to her. One example is the very resepected developer arter97 who didn't release cyanogenmod device trees for s6 for a while when he was developing for s6. Get off ffboy's case, he is a developer and doesn't deserve this, if there was a downvote in xda I would downvote the haters. You've already been warned by the mods yet you still pour hate on to the dev.
Edit: I agree with ffboy we should continue petitioning LeEco for device trees.
@whymoo
I am not arter97, i don't care what he does and i don't accept donations.
ffboy released his rom under mokee s name who they aclame to be "open source". Also i except to see the whole source and not part of it.
If ffboy doesn't like this he could publice his rom to a hoster like "mega"
ffboy and not me already copied code and signed the same code as his own and don't gave proper credit.
We are a big community and we help each other. We share our knowledge and don't hide it. I and other people don't like to reinvend the wheel again. This is a waste of precius time who lot of us they don't have. Yes! we can contribute, merge bugs and maybe compile other roms and yes, ffboy must accept, that maybe me or others wanna use his device tree or some other code. BUT we don't forget to give credits.
Btw i don't be warned and i don't see a reason why should be.
It's CM or stock based?
ir work?
monleylord said:
@whymoo
I am not arter97, i don't care what he does and i don't accept donations.
ffboy released his rom under mokee s name who they aclame to be "open source". Also i except to see the whole source and not part of it.
If ffboy doesn't like this he could publice his rom to a hoster like "mega"
ffboy and not me already copied code and signed the same code as his own and don't gave proper credit.
We are a big community and we help each other. We share our knowledge and don't hide it. I and other people don't like to reinvend the wheel again. This is a waste of precius time who lot of us they don't have. Yes! we can contribute, merge bugs and maybe compile other roms and yes, ffboy must accept, that maybe me or others wanna use his device tree or some other code. BUT we don't forget to give credits.
Btw i don't be warned and i don't see a reason why should be.
Click to expand...
Click to collapse
first i opensourced kernel soucre as GPL requirement,but device tree was not GPL and you do not have the right to force me do things i dont like.
2nd i know i made mistakes on kernel source for commit authorship brcause i am not good at git tools but i have already corrected them.
i dont care you like me and my rom or not
i have released all source of mi max on my github
the only reason i dont release max2 device tree is,
Some people here is just do nothing but PUSHING AND ATTACKING me because they want my device tree to build there roms to gain Respect and donations i think.they are so rude and ridiculous
when i said "No plan to release kernel source RECENTLY" and released a few days later,they don't care and start attacking and pushing
i also dont warned by forum moderatoer by not released device tree
So ban me out of this forum if you can
ffboy2009 said:
first i opensourced kernel soucre as GPL requirement,but device tree was not GPL and you do not have the right to force me do things i dont like.
2nd i know i made mistakes on kernel source for commit authorship brcause i am not good at git tools but i have already corrected them.
i dont care you like me and my rom or not
i have released all source of mi max on my github
the only reason i dont release max2 device tree is,
Some people here is just do nothing but PUSHING AND ATTACKING me because they want my device tree to build there roms to gain Respect and donations i think.they are so rude and ridiculous
when i said "No plan to release kernel source RECENTLY" and released a few days later,they don't care and start attacking and pushing
i also dont warned by forum moderatoer by not released device tree
So ban me out of this forum if you can
Click to expand...
Click to collapse
I don't care if you like ne or not either. I gave you also a like. I don't care either to gain Respect or earn money through donations.
You are the only one here who try to gain respect or donations but your behavior shows me clearly that you are reacting like a little defiant child who felt driven into a corner.
I made a Pointment about you and you have to accept it.
monleylord said:
I don't care if you like ne or not either. I don't care either to gain Respect or earn money through donations. You are the only one here who try to gain respect or donations but your behavior shows me clearly that you are rect like a child. I made a Pointment about you and you have to accept it.
Click to expand...
Click to collapse
I'd be interested in the device tree so I could play around building with some custom toolchains. All my phones run ROM's I've compiled myself but I've never shared them with anybody here as they aren't my work.
mikeysteele said:
I'd be interested in the device tree so I could play around building with some custom toolchains. All my phones run ROM's I've compiled myself but I've never shared them with anybody here as they aren't my work.
Click to expand...
Click to collapse
This will become ridiculous be smart and open with everybody we talk about a phone don't forget this please
sdevaux said:
This will become ridiculous be smart and open with everybody we talk about a phone don't forget this please
Click to expand...
Click to collapse
I think you misunderstand. Building ROMs with custom toolchains and then posting them here would be passing off the work of others as my own, which is not on. I'm not making any source code changes.
mikeysteele said:
I think you misunderstand. Building ROMs with custom toolchains and then posting them here would be passing off the work of others as my own, which is not on. I'm not making any source code changes.
Click to expand...
Click to collapse
I understand it's just that everyone should be open with others it would allow us to move forward the rom development for this model that's just my opinion
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.
So I really don't know what's going on and what's happening behind the stage.
Obviously alonsoj636 decided to discontinue and abandon his greatly admired LineageOS builds from the past months.
I haven't found any notes or statements as to why he finally has decided to do so and I was not able to reach him on xda because he blocked PMs. If you read this, maybe you want to be so kind and give us some hints what's happened!
Anyway...
we, as the RM10 LineageOS community, have to face reality and that means: currently there is no LineageOS rom build and maintained by anybody. That either means sticking with old versions, changing ROMs/GSI or switching the phone completely.
While alonsoj636's versions are still working very well, they eventually become outdated sometime.
This thread should be used to coordinate discussions about future LineageOS development (if there is enough interest and people).
You have 3 options.
Wait for another builder to pick it up
Build it yourself
Run Lineage GSI from AndyYan (guide here)
One more thing. Building a ROM for a device is never considered a development. What you're referring to, is maintenance. Lineage's development will never stop.
Alright, so the cat is out of the bag on this one:
While I'm really happy that Alonso kept maintaining the ROM for a while, the reality is that he wasn't interested to go official anytime soon and kept being vague about it.
As for me, I'm building up the courage to do MPK99 recommendation and go with GSI. Apparently GSI works like old ROMs, and it doesn't nuke TWRP, so that seems nice.
Try GSI. It's perfect.
MPK99 said:
You have 3 options.
Wait for another builder to pick it up
Build it yourself
Run Lineage GSI from AndyYan (guide here)
One more thing. Building a ROM for a device is never considered a development. What you're referring to, is maintenance. Lineage's development will never stop.
Click to expand...
Click to collapse
I'm pretty aware of that, however all new ROMs are tagged as development on this xda forum so I used this wording.
I think all 3 mentioned options are valid.
I could build it myself, however the time is the problem. Finding someone else building lineage in the future seems to be difficult. The past showed there aren't as many people interested and even less have the time and skill to build it.
GSI sounds like a wonder bag to me. while it's great to always have the latest updates, it might lack of the features LineageOS had for years. (i think of things like os-level online permission per app (wifi/cell), permission center, etc.). you can workaround that with 3rd party tools maybe, but it's cumbersome again.
Also GSi still sounds like a bit of an unpolished OS for this specific phone, with some kind of bugs and lack of features (compared to LOS). it's everybodys own decision to put priority on either that or on latest updates, though.
I might as well give it a try sometime, but I'll need enough spare time for experiments, so it won't happen soon.
my hopes are low, but maybe someone will step up and also build new LOS roms in the future.
Zirila said:
however all new ROMs are tagged as development on this xda forum
Click to expand...
Click to collapse
They're all namesake
Zirila said:
it might lack of the features LineageOS had for years
Click to expand...
Click to collapse
Lineage is lineage whether it's a gsi or a cusrom
Zirila said:
still sounds like a bit of an unpolished OS
Click to expand...
Click to collapse
Those are false claims. You need to use it before committing on it.
Zirila said:
I'll need enough spare time for experiments, so it won't happen soon
Click to expand...
Click to collapse
There's nothing to experiment, as user's experiments are logged on my thread. You can follow them. I'm myself a gsi user for an year long btw. As for the time, it'll take not more than 10 minutes. And I've laid out post configuration & fixes on the thread which'll be another 5 minutes.
well what I meaned with unpolished is what I've red in your thread about bugs like -don't touch screen while booting- etc. I haven't installed it so I solely say that by reading these posts.
and experimenting is synonymous with taking time to clean flash and reinstall everything again while learning and fixing problems with new OS/roms/GSIs.
I'll have a look sometime and I'm grateful there is progress.
Atleast I was transparent about the bugs on it.
Zirila said:
bugs like -don't touch screen while booting
Click to expand...
Click to collapse
Not touching the screen 'while booting' is an easy fix & you won't often reboot your device while work in the first place.
Zirila said:
learning and fixing problems with new OS/roms/GSIs
Click to expand...
Click to collapse
Just the procedure would be new. Rest of it would be your same old preferred AOSP derivative (lineage).
you did well. nothing to complain.
the more I dip into the topic the more I think it might be worth a try. don't count the time till I can focus on it, it'll take a while. but it sounds more and more promissing and the overall experience might as well get even better with time.
regardless of the GSI option, let's still have this thread and discussion opened for the case of some future LineageOS-CustomROM progress.
I'm very sorry for my abrupt decision to kill Lineage.
some personal and family problems made me think that I couldn't continue with this (nothing too big, don't worry... typical family fights)
after some messages I decided to get back to the action.
I will upload a new build with improvements once I unlock my bootloader (not very soon) as my RN10 is my only source of internet and I can't use the Mi Unlock Tool.
Thread will remain locked until the new build is done.
Thank you for your understanding and sorry for my bad steps ....
Regards
Thanks for the informational update
no worry, we are all human. as software engineer and project maintainer in troubled times it's often better to just keep calm, step back for a while, let the projects delay or freeze, that won't really hurt anyone. and then check back later to make a judgement if the project(s) really have to end.
It wasn't that bad for us either, in the meanwhile some of us learned a bit more of the GSI option which might also be a viable way to run LOS in the future. But everything has up- and downsides.
I'm glad we get to see a few more updates for the LOS custom rom.
lineage is alive again
new update is up ... waiting for shadowstep to open the thread again
Changelog
* Switch to SkiaGL Threaded
* Optimize package manager dexopt properties
* Kernel upstreamed to v4.14.295
* Kernel built with Clang 15.0.2
* Enable config_avoidGfxAccel
* wifi: Disable TDLS offchannel
* Disable few debug services
* Don't enable iostats
these are only for LineageOS 19.1
No changes for 18.1
Lineage OS for Mojito - Browse /Lineage at SourceForge.net
LineageOS for Redmi Note 10 (mojito/sunny)
sourceforge.net
Deleted.