The NookieDevs are pleased to announce the CyanogenMod 10.1.3.2 stable release for the Nook Color!
As the "stable" label suggests, all major features of the hardware work and the release should be suitable for day-to-day use on your Nook Color. As the "stable" label also suggests, updates (if any) will be primarily to fix bugs -- new features and big changes should not be expected.
Highlights: (mostly not news if you've been keeping up with CM10/10.1/10.2 nightlies)
Linux kernel 3.0.8, plus hardware support from TI OmapZoom's android-omap3-3.0 branch and board support forward-ported from BN kernel releases.
All of the features of CyanogenMod 10.1, based on Android 4.2.2.
Full 2D and 3D graphics acceleration using the GPU.
Unofficial Bluetooth support, including support for a wider variety of BT peripherals than in previous releases. (The Nook Color lacks a proper Bluetooth antenna, so range will be somewhat limited.)
10.1.3: significantly improved graphics performance and improved battery life over previous CM10.1 releases.
10.1.3: various bug fixes, including fixes for Bluetooth tethering, Adobe Flash Player, and a nasty hardware bug affecting the internal storage of some Nook Colors.
10.1.3.1: fix for a security bug reported upstream which potentially allows an attacker to obtain local root (see the dev thread for details). Thanks to Nico Golde and Fabian Yamaguchi for reporting, Ivaylo Dimitrov and Pavel Machek for working on a fix, and dhiru1602 for reporting a bug in that fix.
10.1.3.2: fix crash when opening "About tablet" in Settings. Thanks to CM's Ricardo Cerqueira for the fix and the rebuild.
Known issues:
Current releases of Netflix do not work with CM10.1 -- version 1.8.1 is the last version known to work. If you want/need a newer release of Netflix, look into the Xposed mod, which provides a workaround for Netflix -- pastordl has done a nice writeup of the process here.
The CyanogenMod Updater app may crash when checking for new updates. Deleting /sdcard/cmupdater and/or clearing the app's data may help.
Download:
https://download.cyanogenmod.org/get/jenkins/51847/cm-10.1.3.2-encore.zip
Code:
MD5: 72d6978a754d5637f28f3c031367781a
SHA1: 316da5997232bb641240c2378fdaa634ce5d50eb
SHA256: b9391d37418322b1960db8edd2a738a44ac2ea12cdeb02a80628c6f95efaa67f
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-10.1.3 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore/tree/cm-10.1.3 (kernel)
https://github.com/CyanogenMod/android/tree/cm-10.1.3 (manifest for the rest of the CyanogenMod source)
Build instructions (discussion of build issues belongs in the development thread)
This release is the product of much effort by many people over a considerable period: many thanks to fattire, keyodi, eyeballer, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor, dhiru1602 and many more. Thanks are also due to the CyanogenMod project, upon which we are building, and Texas Instruments, which provides excellent support for its embedded platforms to the open-source hacking community. (TI's exit from the consumer electronics SOC market is a loss for all of us.)
XDA:DevDB Information
CyanogenMod 10.1 Stable, a ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 10.1.3.2
Stable Release Date: 2013-12-18
Created 2013-09-05
Last Updated 2013-12-19
Reserved
Google Apps; other CyanogenMod builds
Google Apps
http://goo.im/gapps
As of 2013/10/09, the latest release for CM10.1 is 20130812, but please check the linked page for updates.
Please make sure that you have the correct Google Apps flashed before reporting problems involving the Google Apps (Play Store, Google Keyboard, etc.).
Other CyanogenMod builds
This is the thread for CM10.1 stable releases. There are other official CyanogenMod builds for Nook Color available:
CM11 nightly builds -- these experimental builds, based on Android 4.4, contain the latest changes to CyanogenMod and to hardware support for the Nook Color. As the name suggests, new builds are made and posted (roughly) every day; these builds are fully automatic, with no testing done before posting.
CM10.2 stable releases -- while the state of the Nook Color-specific hardware support should be nearly identical to that of CM10.1, you may find this Android 4.3-based release more (or less!) stable than this Android 4.2-based one.
Archived nightly builds for CM10.2, CM10.1, and CM10. You may find the last CM10 nightly (20130421) faster than the later releases, particularly during playback of HD 720p video.
Please check that your questions are in the appropriate thread. (If you're interested, there's lots of past discussion in those threads, as well as the development thread.)
Frequently Asked Questions and Troubleshooting
The soft keyboard keeps crashing!
The Play Store is acting up!
Did you flash the correct Google Apps?
What happened to the "Developer options" and "Performance" screens in Settings?
They're hidden by default now in CM10.1 and later. To show them, go into "About tablet" and tap the build number (for CM10.1 stable releases, JDQ39) seven times.
How do I get the Honeycomb/ICS tablet UI?
You want to use the Auto-Patcher to modify your ROM for the tablet UI. (Don't forget to thank Caldair for maintaining the Tablet UI mod, and mateorod and the rest of the Auto-Patcher developers for building that tool.)
I'm having a problem with my Nook Color running CM10.1.
That's not a question
Okay, I'm having a problem with my Nook Color running CM10.1 -- is there something I can do to troubleshoot?
Glad you asked! Please check the following:
Does the problem occur with a clean install of CM10.1? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).
Are you overclocking? If so, does the problem occur when you set the maximum clock speed to 1000 MHz or below? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or "sleep of death" (SOD), you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).
Do you have any patches, custom kernels, or other tweaks applied? If you do, does the problem occur without those applied? (We're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know what changes you have applied to judge whether or not the change might be relevant to your problem.)
I'm having no luck with the suggestions above. What information should I include with my bug report?
When reporting a problem, please include the following information if at all possible:
Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?
For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.
For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).
For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.
Edit: Used these instructions for installing 10.1 on a SDCard.
http://forum.xda-developers.com/showthread.php?t=1941858
Great thanks!
Sent from my NookColor using Tapatalk 4 Beta
Congrats and thanks again Steven and the other NookieDevs, this is running very well, at least on my NC, somehow seems a little more responsive/smoother (especially when background apps/downloads are running - new WiFi tweak?) than the recent nightlies/RC's. Great job, but, there is a new nightly calling, or I've sort of been wanting to try Mateorod's AOSP, besides, my schedule is beginning to settle back down enough that I will probably try to increase my "Android Ninja" experience, so I probably won't be stable long. Keep up the great work, glad to hear that you will still be tweaking it.
Question, are your latest WiFi and/or Graphics tweaks merged yet?
NC crashing hard with clean CM10.1 install
Hi,
great to see CM10.1 on NC. I have just made a clean install on my Nook and generally impressed. Unfortunately my Nook started crashing hard, something that I never experienced before It seems to be correlated with Gallery application, I can reproduce crash only after I open Gallery and then return to home page. Here is what happens:
open Gallery, look at one or few pictures
go back to Home
wait a bit, one minute or so, maybe go to other app or settings
screen goes blank, navigation buttons and status bar are still visible but display area gets dark
no response to touch or nook button
after ~30 seconds Nook reboots
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
I ran CM7.2 on the same device for quite some time and had no troubles with that. CM10.1 install is from final, wiped both data and cache, no google apps installed yet, no other apps restored, virgin clean :angel: No overclocking, and no other settings changed, no patches.
Thanks,
Andy
andy1001 said:
Hi,
great to see CM10.1 on NC. I have just made a clean install on my Nook and generally impressed. Unfortunately my Nook started crashing hard, something that I never experienced before It seems to be correlated with Gallery application, I can reproduce crash only after I open Gallery and then return to home page. Here is what happens:
open Gallery, look at one of few pictures
go back to Home
wait a bit, one minute or so, maybe go to other app or settings
screen goes blank, navigation buttons and status bar are still visible but display area gets dark
no response to touch or nook button
after ~30 seconds Nook reboots
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
I ran CM7.2 on the same device for quite some time and had no troubles with that. CM10.1 install is from final, wiped both data and cache, no google apps installed yet, no other apps restored, virgin clean :angel: No overclocking, and no other settings changed, no patches.
Thanks,
Andy
Click to expand...
Click to collapse
I can confirm this - I have been experiencing this for a long time now but since nobody else mentioned it I thought it could be just me (although I was doing clean installs). So this problem really exists.
I cannot reproduce this, but I flash the Picassa compatible gallery app - gapps-jb-picasa-20121011-signed.zip - after GAPPS
andy1001 said:
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
Click to expand...
Click to collapse
Mmm, that's pretty spectacular -- the system basically runs out of memory and the kernel goes nuts killing things to try to keep the system alive. It looks like the 720p video codec is eating the memory, and I believe we tracked that one down to the same root cause as the Flash issues. Can you try a CM10.1 nightly from June 25 or later (EDIT: or flash the patch in the next post on top of your existing CM10.1 install) and see if the problem still happens? (That reminds me, I promised to respin the binary patch for CM10.1 stable ... I should really do that when I get a minute.)
Patch for 720p codec issues (Flash, video thumbnailing)
As promised, here's the patch fixing Flash, video thumbnailing in the Gallery app, and potentially other 720p video codec issues for the CM10.1 stable release series. (The previous one I posted works as well, but is missing a couple of other potentially useful bugfixes in libstagefright.)
Usage: flash the attached ZIP file over your CM10.1 build from recovery. CM10 users: do not flash this -- use the patch in this post instead. Note that if you're on the CM10.1 nightlies, this patch was merged and should be included in builds starting from June 25.
(Source code: https://github.com/CyanogenMod/android_frameworks_av/tree/cm-10.1.0/media/libstagefright with https://github.com/CyanogenMod/android_frameworks_av/commit/c58721cbdcbfc46f550954a1c258d9b0529e4d81 applied on top.)
steven676 said:
As promised, here's the patch fixing Flash, video thumbnailing in the Gallery app, and potentially other 720p video codec for the CM10.1.0 stable release. (The previous one I posted works as well, but is missing a couple of other potentially useful bugfixes in libstagefright.)
Usage: flash the attached ZIP file over your CM10.1 build from recovery. CM10 users: do not flash this -- use the patch in this post instead. Note that if you're on the CM10.1 nightlies, this patch was merged and should be included in builds starting from June 25.
(Source code: https://github.com/CyanogenMod/android_frameworks_av/tree/cm-10.1.0/media/libstagefright with https://github.com/CyanogenMod/android_frameworks_av/commit/c58721cbdcbfc46f550954a1c258d9b0529e4d81 applied on top.)
Click to expand...
Click to collapse
It is really a damn shame we got that merged just after 10.1 Final was sent to the servers.
steven676 said:
Mmm, that's pretty spectacular -- the system basically runs out of memory and the kernel goes nuts killing things to try to keep the system alive. It looks like the 720p video codec is eating the memory, and I believe we tracked that one down to the same root cause as the Flash issues. Can you try a CM10.1 nightly from June 25 or later (EDIT: or flash the patch in the next post on top of your existing CM10.1 install) and see if the problem still happens? (That reminds me, I promised to respin the binary patch for CM10.1 stable ... I should really do that when I get a minute.)
Click to expand...
Click to collapse
I have tested both cm-10.1-20130627-NIGHTLY-encore.zip and final CM10.1 with your patch libstagefright-omxcodec-patch-for-cm-10.1.0-encore.zip, they both seems to be working OK, I could not make them crash in the same way as unpatched CM10.1 does :victory: Thanks a lot for the fix, much obliged!
Andy
Still having issues with the nook color.
Check the dmesg file for Cm10.1 stable.
Thanks for the patches <steven> Seems to help.
My stable is still holding up good on my NC.
mhzrus said:
Still having issues with the nook color.
Check the dmesg file for Cm10.1 stable.
Click to expand...
Click to collapse
This is what I encounter with Nook Color CM 10.1.2 stable version.
CMUpdater cannot download new Nightly!!!
Battery went flat no indicator.
Wifi issues, network error! For Nothing!
Touch Screen still having issues. The left hand side and right hand side of the screen cannot response to any touches! (About 2 inches thick!)
I come to know that there is issues with Nook Color Touch screen.
http://forum.xda-developers.com/showthread.php?t=1385896
CM10.1.2
A quick heads-up: CM10.1.2 was released last week (check the links in the first post), including important security fixes. (The Flash fix didn't go in and looks unlikely to go into the 10.1 stable series at this point -- you'll have to continue flashing the patch above for now.)
cm-10.1.2-encore stable vs nightly - Patch for 720p codec issues?
steven676 said:
A quick heads-up: CM10.1.2 was released last week (check the links in the first post), including important security fixes. (The Flash fix didn't go in and looks unlikely to go into the 10.1 stable series at this point -- you'll have to continue flashing the patch above for now.)
Click to expand...
Click to collapse
Thanks for that info steven676; so that patch will work for cm-10.1.2-encore stable?
What's the easiest way to tell if the patch is or isn't working on my NC?
Lastly, is it necessary or included with any of latests cm-10.1.2-encore nightlies?
:good:
eltrkbrd said:
Thanks for that info steven676; so that patch will work for cm-10.1.2-encore stable?
Click to expand...
Click to collapse
Yes, it'll work for CM 10.1.2 stable (or any other CM10.1 release).
eltrkbrd said:
What's the easiest way to tell if the patch is or isn't working on my NC?
Click to expand...
Click to collapse
Install Flash, enable plugins in the browser, then open Flash Player Settings -- if the bug is still present, the page will lock up and you'll eventually be prompted to kill the tab.
eltrkbrd said:
Lastly, is it necessary or included with any of latests cm-10.1.2-encore nightlies?
Click to expand...
Click to collapse
As noted in the post with the patch, the fix should be included in CM10.1 nightlies starting with the June 25 build.
Related
As of 8/25/12, this project is officially discontinued. All information below is for archival purposes only and will not be supported henceforth.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
INTRODUCTION
Now that Fattire has lifted his request that everyone build their own zips, I've decided to make available the nightly builds I've been generating. I've got an OS X system cranking out a new build every night at midnight, so there will always be an up to date zip available!
Credit for this rom goes to Fattire, Dalingrin, keyodi, nemith, arcee and the the other hard working people over in the development thread, as well as the the CyanogenMod developers and anyone who's done work on the Nook Color. I wish I could list everyone by name but there's so many great people who've made contributions I can't even begin to do so. I'm just building zips from the source; we'd be nowhere without the contributions these great developers have made to this community.
As nighty builds, these zips may not always work. I'll try to remove any zip found to be broken, but you know the drill: All files provided here are to be installed at your own risk. I'm making built zips available, but no warranty is expressed or implied by the hosting of said zips. I'll provide what support I'm able to, but that doesn't mean that there aren't potentially unknown bugs. If you have questions, you should check the development thread or try the #NookColor IRC channnel on irc.freenode.net.
As posted by Fattire slightly further down, anyone feeling adventurous should definitely consider building from source rather than downloading the built zips. Here's his two cents:
fattire said:
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
Click to expand...
Click to collapse
However, if you're not quite sold on setting up a development environment but you still want to try the goodness that is Ice Cream Sandwich, proceeed on down to the...
DOWNLOADS
Without further ado: The Ice Cream Sandwich zips!
Ice Cream Sandwich Nightly Builds.
The rom does not include the google apps, so you can/should flash the lastest version of those, which is available here.
Finally, I've hosted a few flashable zip files to make small tweaks to the rom. These are all located in the misc. folder on my server. Below is an explanation of each zip and its purpose.
MISC FOLDER INFO
If you notice that some apps are missing from the market, this may be due to the fact that these ICS builds for the nook do not include support for apps which request phone permissions. Although this ideally would be fixed by developers not requesting phone permissions for their app unless it absolutely needs to be phone-specific, you can also fix it by flashing the telephony-permissions-fix.zip file located in the misc folder. You will likely want to flash this file immediately after flashing your rom.
Secondly, if you prefer the old bootanimation from the galaxy nexus, you can also flash the fix-bootanimation.zip located in the Misc. folder, which replace the new CM9 animation it with Homer_S_xda's fixed version. Thanks to Homer for the fix!
NOTES ON INSTALLING TO SD
I've fixed Verygreen's sd installer image to work with ICS -- you should no longer have to flash SP1 first, or rename the gapps to gapps-gb. If you test out this image, please let me know how it works for you! More recently, Leapinlar has stepped up in helping to fix the image further, increasing its size to allow for the larger size of the new nightlies. Thanks to him for his help -- It's available for download here. Huge thanks to Verygreen for helping me to figure out what needed to be fixed -- in the words of HacDan, "He's not just super helpful, he's a genius". Once you've got the new image, you can use Verygreen's original instructions from his thread on SD Installs, replacing "cm7" with "cm9" where necessary.
IN CONCLUSION
Please remember to thank the developers working on this project, as they've done seriously awesome things for us in an amazingly short amount of time. If you have questions/comments specifically regarding my zips, please post them here, but if you have more general questions regarding Ice Cream Sandwich on the NC you may want to head on over to the development thread. Finally, if you're really enjoying the rom I'd strongly recommend that you try setting up a build environment and building your own zips -- even though I'm making prebuilt ones available they're no substitute for the experience gained by getting familiar with the build process yourself, and Fattire has done a great job of making it an extremely accessible and rewarding project.
Thank you!!!!
What bugs can we expect as far YouTube, flash player. Boot loop . A breakdown of what to expect and not to expect. I don't expect anything but like to know for flashing
And you can build too!
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
So awesome!
Youtube missing in latest gapps ?
I installed the latest nightly with the gapps and found youtube app is missing ?
Thanks for sharing! I love nook color devs community! You did an awesome job!
Brilliant work! I upgraded from CM7 and all my existing apps that ive checked worked no problem, it kept all my settings too! Speed-wise I would say its very close to CM7, i use ADW EX in preference to trebuchet, and it just flies!
One thing ive noticed is that NFS shift doesnt behave properly when using the tilt sensor to steer, its axis sensor wants the tablet to be in portrait orientation when the screen is in landscape. Hard to know if its the games fault or the sensor. If thats all there is to complain about this early in the development then the future looks promising
rajazeeshan said:
I installed the latest nightly with the gapps and found youtube app is missing ?
Click to expand...
Click to collapse
I think you can just get it in the market, I removed it to save space. Let me know if you have a problem downloading it.
Dual boot ?
I currently have a dual boot environment setup so I can boot into stock (primary boot partition is currently CM7). Does anyone know if this still supports that ? Anything specific I'd have to do with the install then ?
TIA
Thanks a bunch for hosting these nightlies.....let the fun begin!
I just want to point out for the sd-card users using verigreens 1.3 boot image to setup cm7 to run off of sd card and retain stock for various reasons.
That process will also work for ICS/cm9. Currently, you need to flash update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip first. It's found in the ics/cm9 dev. thread: http://forum.xda-developers.com/showthread.php?t=1370873
Then, flash Samiam's nightly builds otherwise you will get stuck in a boot loop right now.
Ok just tested it and it works great.
Youtube works just not HQ, although I have to admit that for non HQ the quality and smoothness is very high.
Flash Player doesn't work but I think that has to do with 3D H/W acceleration.
Maps wifi location doesn't work allthough it did work on the normal version of the gapps so something is amiss there.
And I am also experiancing alot of hyper sensitivity especially when using two finger actions.
Otherwise all is well.
I'm gonna stay on cm7 for a while. But I love the progress were seeing with ics.. thanks guys
pavlos46 said:
Ok just tested it and it works great.
Youtube works just not HQ, although I have to admit that for non HQ the quality and smoothness is very high.
Flash Player doesn't work but I think that has to do with 3D H/W acceleration.
Maps wifi location doesn't work allthough it did work on the normal version of the gapps so something is amiss there.
And I am also experiancing alot of hyper sensitivity especially when using two finger actions.
Otherwise all is well.
Click to expand...
Click to collapse
What version of the gapps did you have where the wifi location worked? If you link me to that I can see if there's something missing from my gapps zip.
YouTube is incompatible from the market. Actually, it appears any device I have that runs ICS is listed as incompatible.
youtube app missing in gapps
Samiam303 said:
I think you can just get it in the market, I removed it to save space. Let me know if you have a problem downloading it.
Click to expand...
Click to collapse
Unfortunately thats not the case when I search market it doesn't list YouTube app and when I
Google it takes me to mobile YouTube app in market that is not compatible with this device.
I salute you all dev. gurus.
Hat off and thanks for the ICS
Awesome thanks so much!
Hey,
awesome awesome work, thank you very much!
I have a slight problem with the GApps, though: I came from update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs and just updated over that with some ics-apps installed. Unfortunately, I do not remember which ones.
Now after the update all my apps are there, but the home screen wiped (not so bad), but my Google Account vanished and I cannot add a new one. Neither in the Settings, nor by opening GMail, Talk, whatever. These will just crash.
Any suggestions?
Thanks again for all your work and energy, I really appreciate that.
Greetz,
Felix
ZenoGia said:
Awesome thanks so much!
Click to expand...
Click to collapse
+1 .
As usual, pointing to the post concerning this ROM from its main team HERE
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
1.6 is a pretty big update for us! Check out the changelog on our goo.im page for more, but here are the highlights:
-We've fixed PIE! It no longer decides to be invisible from time to time.
-We fixed the battery charge light! None of us use it but apparently you guys are just nuts for it!
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-3.4 kernel on D2xxx devices. It's finally stable enough where we're comfortable with this - remember to only flash other 3.4 kernels or it will not boot as there are rom-level dependencies.
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
-a million other little things as well - we basically don't even sleep anymore.
Screenshots
{
"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"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users!
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Change Log
Carbon change log HERE
6.02.13 -
Initial release "nightly" build
Fixed Camera
Fixed GPS
6.09.13 -
Synced to Chad0989's trees
Synced sources
Uses chad's -chad branch not fb branch kernel, crpalmer's kernel may work with this build.
6.11.13 -
HALO implemented
6.30.13
Code:
Synced back up with chad's trees
Synced with Carbon source
-Removed for space, post is to long
7.15.13
Code:
Device tree:
Updated with *SOME* of chad/flyhalf/crpalmer's recent work:
https://github.com/CM10DNA/android_device_htc_dlx/commit/b18cbc01baf535de447b44675727ca91b7548bea - cleanup more inline with cm *note* not all changes were done, it was causing issues with Carbon.
https://github.com/CM10DNA/android_device_htc_dlx/commit/9a01d0428755502b17cd2d5854fd293da9b6f143 - updates from m7
Kernel:
To many to list one by one, however visit here https://github.com/CM10DNA/android_kernel_htc_dlx/commits/cm-10.1-chad
And look back to june 30th which was my last pull.
Change log removed for space reasons (post is to long now)
8.06.13:
Tried out the BT fixes from Chad's CM10.2 stuff, so it may or may not work.
Current sources, should be the same as the 8.1.13 final stable releases for Nexus devices.
Change Log 8.06.13
The post is to big for XDA posts now, so instead I'll include a link to the changelog itself!
From here on ONLY use 4.3 gapps, I don't want to see any reports of broken cameras, keyboards or locking up if you are on anything besides a 4.3 gapps!
8.09.13
Fully updated to 4.3 Jellybean source
Fully updated to chad and crew's latest work on kernel/vendor/device
Use only the included kernel for now, crpalmer's 3.1.2 kernel is not fully compatible and will cause display and camera glitching.
Use only gapps for 4.3
A complete revamp of Carbon, they're starting over from the ground up so you may notice a lot of features missing, such as halo, expect these to return soon. What you can also expect is a smooth fast ROM with a solid foundation to build upon!
8.12.13
Updated source
BlueTooth now turns on (how well it works I can't test)
Single build, for now GSM is at least somewhat working on the CDMA build, so for now, pending further investigation, only a single "unified" version is available.
8.19.13
Updated souce
Updated with Chad and company's latest awesomeness
Features are beginning to trickle back in, Halo is back, etc.
Compatible with crpalmer's latest kernel (and .torrented's should also work)
Change Log 8.19.13
8.26.13
Updated Carbon source (ribbons?)
Updated with chad and groups work:
Device:
- Use correct mic for Google Search and other voice apps (bottom, not the top)
- Change back to HTCQualcommRil (from HTCCDMAQualcommRil) * CDMA build only
- Custom recovery graphics
- Sim hotswap will no longer prompt for reboot
- Everything from the 17th to today
https://github.com/CM10DNA/android_d...ommits/cm-10.2
Kernel:
- Hardware VSync support
- Missing clocks added
- ROW Scheduler added
- Everything done for the 14th to today, I'm not typing that all out
https://github.com/CM10DNA/android_k...ommits/cm-10.2
ROM:
- Carbon Fibers updated with a new swype style
- Ribbons returns from AOKP
- See change log on the site as usual
8.29.13
- Updated source
- Removed default showing of the overflow menu button, most hardware key map this and prefer to save the screen space.
- GSM Only: Changed default to WCDMA preferred from GSM/LTE: Should help with initial issues with calling/sms/mms maybe not working on some networks.
- Device, Kernel, Vendor trees otherwise untouched from last build.
- Listview Animations and Interpolator (Carbon Fibers > Interface)
9.13.13
- Updated source
- Built against the M7 kernel
- Includes everything done up to a couple of hours ago.
- NOT Global, CDMA and GSM versions will be needed still.
- CM's enhanced NFC added, I can't test it so any reports would be appreciated.
- MUST CLEAN FLASH THIS NO MATTER WHAT
- Compatible with crpalmer's 4.x.x kernels as far as I know.
9.13.13- B2
Removed qcom keystore to prevent hot reboot on display off.
9.13.13- CDMA B3
Correct issue causing bootlooping on the CDMA build, GSM didn't have it.
9.15.13
Updated source build:
Halo updates from PA
Add color support to text only battery
Fix network speed statusbar indicator traffic color on reboot
Fix reboot menu not being themed
Minor changes
9.16.13
Updated Carbon source:
Small stuff
Corrected QCOM keystore issue (thanks crpalmer)
9.23.13- Part Deux
Update 9.23.13
Updated Carbon source
All updates for the device/kernel sources.
Things that were messed with include the GPS HAL, some display stuff, camera stuff, and more. If you're interested in the details...
Device:
dlx: Import GPS HAL from jf
dlx: HTC camera expects insecure MM heap
dlx: enable option to set button brightness
Kernel:
Large amount, so I'll post the commits from last update, not each one. Not all concern the dna directly. Quite a few concerning bcmdhd, kgsl, msm_fb and other goodies
FROM HERE
TO HERE
Apparently the blank display was due to changes Carbon made to msm8960-common that I hadn't thought to look in on, and it changes quite a few things concerning the display. For now I have reverted to the CM common tree to correct the display issue.
12.5.13:
Initial bringup to KitKat 4.4
UNTESTED, CDMA Version only for now.
New folder for the 4.4 ROM here http://pio-masaki.com/DroidDNA/Carbon-KK
Please use an updated 4.4 GApps package!
Please CLEAN FLASH this only!
Please flash this with the latest 4.4 compatible recovery!
12.10.13:
CDMA only
Updated source and trees
I still can't test so those who had pervious issues (data, MMS) please give this a try and report when you have time.
1.22.14:
CDMA only, may be Global.
Updated build, untested as I lack the device now, please report any issues!
1.29.14:
Updated sources
Camera should work now
Please see if the Settings>Carbon Fibers> Interface FC still occurs.
As usual use the 4.4 GApps that has worked for you so far.
Not on pio-masaki.com yet, you can nab it now here http://d-h.st/Zsj
2.2.14:
Updated sources.
Camera and Interface FCs were corrected last build, should also be alright here.
4.4 GApps that you usually use.
Available on pio-masaki.com
2.5.14:
Updated sources.
Check that the carrier, date/day/whatever is proper and that the data connection icons are correct (IE no more roaming in 3G etc)
For those with speed issues, a report on that would be appreciated.
4.4 GApps that you used last time.
Available on pio-masaki.com
2.9.14:
Updated sources
Built because I was already on my 8th build of the day, why not?
4.4 GApps that you used last time.
Available on pio-masaki.com
2.20.14:
Updated sources
Built because my wife hates me and the couch sucks
4.4 GApps as usual
Available on pio-masaki.com
3.8.14:
Updated sources
Built because why not, its been awhile.
4.4 GApps as usual
Available on pio-masaki.com
4.7.14:
Updated sources
Built because its been a damn month, that's why!
4.4 GApps as usual
Available on pio-masaki.com
6.23.14:
4.4.4
Updated sources
JustArchi optimizations implemented
FULL 100% -03 built ROM, not just portions
Linaro 4.8 toolchain
Built as user instead of userdebug, odexes the ROM and disables some of the background logging
Updated Adreno candies
Peek
Available on pio-masaki.com in the usual place, however look in the SS folder as this is no longer just Carbon.
Instructions:
Please clean flash this, there's so many extra settings that dirty flashing will likely cause problems. If you dirty flash, please don't report any issues until you flash clean and the issue occurs again!
Please use a proper 4.2.2 Gapps package, using inversed or any modded versions can and likely will cause issues, please use the current 4.2.2 from goo.im, if you use inverted or modded Gapps, please don't report issues until you clean flash with a proper package from goo.im!
If you are not S-OFF you will need to extract the boot.img and flash it separately, either flashGUI or fastboot, your choice, needs done.
S-OFF:
Download the ROM for your needs, CDMA or GSM.
Download the current 4.2.2 Gapps from goo.im or pio-masaki.com
Place files someplace useful
Boot into recovery
This part assumes you know how to operate your installed recovery
Wipe system
Factory reset
Wipe dalvik
Flash CarbonROM
Flash Gapps
Reboot
Let settle for a few minutes after booting
Setup phone as usual
If you have issues on first boot, flash the ROM only, then after it boots, reboot and flash Gapps then manually setup your phone in settings.
CDMA version: for use with Verizon, NOT for any other network.
GSM version: for use with GSM carriers, NOT for Verizon.
Global verison: for use with BOTH Verizon and GSM, no different build required
​
FAQS
If you didn't read the bugs list in the first post, go back up and read that now, asking the same questions over and over is a trademark of xda and I hate it, please read the change log and bug list before posting questions or reporting issues.
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, that's basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
Q. Is this daily driver ready?
A. Can't answer that, what a person needs from their phone varies from person to person, what I may consider fine for my use may be 500 kinds of broken for another user. Example, I don't use my camera often, maybe once a month, and my BT has never been turned on for the last 5 devices, for me broken BT audio and camera doesn't make it a non daily driver ROM. Please read and decide for yourself if features included outweigh the broken, or if broken things are required for your comfortable use of your device.
Q. How can I build my own versions?
A. For now you can use the existing CM tree and build it that way. Any further help can be asked as needed.
Q. Can I use -insert kernel name here-?
A. No. Well ok you can, but please don't report any issues while running anything besides what came with the ROM.
Q. Your files all download as index.php!
A. This happens on certain browsers, namely the stock browser and Chrome. You can either use another browser (naked and dolphin don't do this) or simply rename the file to something useful, like "piostotallyepicawesomesaucedrizzledromthatrocksyourass.zip"
Q. Can we do random bantering and good natured fun poking in your thread?
A. Sure, feel free to go OT on occasion, I'm all for having FUN on xda, even if some are not. I would like users to feel completely comfortable in my thread with no worries of me coming down on any thing not ROM or development related, I don't run a strict thread as many know by now. What I don't want is flame wars, though. Please keep a limiter on what is good natured fun as we all know things can get out of hand quickly. If someone is taking offense to something going on and its made known, please end it there with no hard feelings.
Bugs:
None specific to Carbon
Downloads:
Please visit pio-masaki.com for all my ROM builds
Kernel source used:
https://github.com/CyanogenMod/android_kernel_htc_m7​
Whoop!!!! I heard rumors! I'm about to no sleep and flash this tonight...thanks so much for your hard work!
I downloaded this from your server and running it now. Seems very smooth and I like the breathing effect of notifications. You need to rest!
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Shamrock13 said:
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Click to expand...
Click to collapse
Didn't notice the placeholder post? I was still making the posts lol
And yes, generally it will have whatever issues CM currently has.
Shamrock13 said:
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Click to expand...
Click to collapse
Goto www.pio-masaki.com and download from there
@pio,
Really nice work man.
Using it for the last 2 days and I can say that its the smoothest ROM out there. Paired with crpalmers kernel its SWEEEEEEEEEEET.
Tapatalked from TF300T with AOKP goodness
Pio is a ROM building machine! He probably dreams about code and bug fixes...lol
Websites going down at 3am CST for update and backup...only be down about 20 mins
Updates and backup done. Websites up.
Sent from my Nexus 7 using Tapatalk 2
pio/guys,
I just want to ask, since I have to wait until my battery charges before I flash... How are you liking this ROM compared to PAC/Revolt? Also since it's CM10.1 based it should have all multi-touch issue fixed right? ( I would hate to flash & find out my kid can't play his Gunman Clive again, that would mess him up. lol )
Also I read that maybe we should keep the STOCK Kernel on this ROM instead of using the AOSP Kernel. Did I read right or misunderstand?
pio, you are the Gandalf of the HTC Droid DNA, you indeed are working some sweet magic.
THANK YOU! Ohh and like everyone is saying..... Get some REST! :cyclops:
Epic 4g said:
pio/guys,
I just want to ask, since I have to wait until my battery charges before I flash... How are you liking this ROM compared to PAC/Revolt? Also since it's CM10.1 based it should have all multi-touch issue fixed right? ( I would hate to flash & find out my kid can't play his Gunman Clive again, that would mess him up. lol )
Also I read that maybe we should keep the STOCK Kernel on this ROM instead of using the AOSP Kernel. Did I read right or misunderstand?
pio, you are the Gandalf of the HTC Droid DNA, you indeed are working some sweet magic.
THANK YOU! Ohh and like everyone is saying..... Get some REST! :cyclops:
Click to expand...
Click to collapse
Unless you are flashing bootloaders it is extremely hard to screw up. I flash ROMs with less than 10% without even thinking twice and never had a problem. Do what you feel comfortable doing, anything over 20% would be fine IMHO.
I personally prefer the other all in one ROMs he has released. PAC is my favourite as it has every feature I want. If you don't care about Paranoid Android's Hybrid Properties then flash Carbon as it runs smoother for some users.
uppon2 said:
Unless you are flashing bootloaders it is extremely hard to screw up. I flash ROMs with less than 10% without even thinking twice and never had a problem. Do what you feel comfortable doing, anything over 20% would be fine IMHO.
I personally prefer the other all in one ROMs he has released. PAC is my favourite as it has every feature I want. If you don't care about Paranoid Android's Hybrid Properties then flash Carbon as it runs smoother for some users.
Click to expand...
Click to collapse
Cool I hear that, it's just that I want to be able to play with the ROM after I flash. If I flash a ROM at 10% or so then that REALLY limits my time with the ROM, because then I would have to put the phone to charge.
I just went to pio's website & downloaded Carbon but the file I downloaded is called "index-1.php" instead of "CARBON-JB-UNOFFICIAL-20130602-dlx-CDMA.zip".
Is that OK or is there a problem here? I am not going to flash that file until I get confirmation that it's supposed to be like that.
Thanks to anyone who can verify & help. This is the first time this has happened to me on one of pio's ROMS.
Epic 4g said:
Cool I hear that, it's just that I want to be able to play with the ROM after I flash. If I flash a ROM at 10% or so then that REALLY limits my time with the ROM, because then I would have to put the phone to charge.
I just went to pio's website & downloaded Carbon but the file I downloaded is called "index-1.php" instead of "CARBON-JB-UNOFFICIAL-20130602-dlx-CDMA.zip".
Is that OK or is there a problem here? I am not going to flash that file until I get confirmation that it's supposed to be like that.
Thanks to anyone who can verify & help. This is the first time this has happened to me on one of pio's ROMS.
Click to expand...
Click to collapse
Rename the file to something.zip . it does that with chrome or stock browser, user Firefox on android for downloads to fix the filename issue. Other than being named wrong, the file is fine.
Sent from my Nexus 7 using Tapatalk 2
diesburg said:
Rename the file to something.zip . it does that with chrome or stock browser, user Firefox on android for downloads to fix the filename issue. Other than being named wrong, the file is fine.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
OK I will rename it "something.zip" as you said with out the quotations marks & flash. Thank you for the heads up. You are the man! :good:
Awesome going to flash this now! Does this include the halo framework or is that not released yet?
My head is spinning! Which way to I turn? Thanks pio!!
Sent from my HTC6435LVW using Tapatalk 2
I added the index.php issue to the FAQs last night.
Personally I use crpalmers kernel with this ROM, its great, by all means use it.
Personally I use carbon because I don't use PA features. Second is ReVolt, then PAC, though since the recent apps fix in PAC its a little harder to say lol
No halo in this, its in the works, though. The carbon team has released a special halo version for some devices a couple weeks ago, so it may happen once halo matures a little more.
Tapatalked from my HTC DNA - Carbon
Hey pio is the 20130602 build the same build from a couple days ago? Or did you update it? Just wondering because my WiFi isn't working. I saw yesterday you said you where going to upload new builds with WiFi fixed. Thanks again for the awesome ROM
Sent From My HTC DNA Carbon
I clean flashed this coming from a Sense 5 rom and cant find any of my old data anywhere. The free space on the card has not gone up but I cant see to find my stuff. I tried storage/emulated/0, storage sdcard0, everywhere i can think of.
coachcrey said:
Hey pio is the 20130602 build the same build from a couple days ago? Or did you update it? Just wondering because my WiFi isn't working. I saw yesterday you said you where going to upload new builds with WiFi fixed. Thanks again for the awesome ROM
Sent From My HTC DNA Carbon
Click to expand...
Click to collapse
It was fixed, also if you flash crpalmers kernel wifi will work as well.
Budwise said:
I clean flashed this coming from a Sense 5 rom and cant find any of my old data anywhere. The free space on the card has not gone up but I cant see to find my stuff. I tried storage/emulated/0, storage sdcard0, everywhere i can think of.
Click to expand...
Click to collapse
Its in /data/media, this is discussed numerous times in various threads so I won't get into much detail, but copy from /data/media to /0 and it'll work fine in 4.2 ROMs. To go back to a sense ROM move back from /0 to /data/media. After you can delete /0 but don't they to delete /data/media, just what may be in it as that's your internal SD card.
Tapatalked from my HTC DNA - Carbon
THIS BUILD IS ONLY FOR PEOPLE WHO WAN'T TO POINT OUT BUGS AND OTHER ISSUES THAT I HAVE NOT MENTIONED PLEASE DON'T COMMENT AND SAY ZOMG WHY DOESN'T CALL WORK OR STUPID CRAP LIKE THAT! AGAIN TESTING ONLY!!​
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATION
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
CHECK KNOWN ISSUES IN SECOND POST
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
First time installing CyanogenMod 10.2 to your ONE X+, or coming from another ROM:
- Read known issues ans FAQs
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into HBOOT (hold Volume Down at boot)
- Flash the boot.img
- Fastboot flash boot boot.img
- Reboot into recovery via the bootloader menu
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
DOWNLOAD:
Google Apps:
http://goo.im/gapps
ClockworkMod Recovery:
http://forum.xda-developers.com/showthread.php?t=2074396
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
XDA:DevDB Information
[ROM] CM10.2 AT&T/TELUS , ROM for the HTC One X+
Contributors
Lloir, h8rift
Source Code: https://github.com/evitareul
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-11-28
Last Updated 2014-11-19
List of stuff that IS working currently (not released and no eta)
Display
Audio
MTP
Camera
Microphone
GPS Borked
Ril\GSM
WIFI Now borked
Bluetooth
NFC​
Reserved
CHANGELOG
Code:
18/2/14
Fixed call audio, all it was, was a super hard to find error which said which permission it was
Fixed Data\gsm
28/11/13
inital testing release
In call is 100% buggered
GPS is trashed
Camera works (if gps is turned off)
Most recent CM source
PLEASE enable the Xda 2013 theme to view this thread correctly, as it is a DEVDB thread.
which enables you to see the downloads section
Q&A
Bug reports
Reviews
Screenshots
ALL questions > Q&A and NOT into this thread
Bug reports > Bug reports tab, with a logcat
Once all the kinks are sorted, this will be pushed to OFFICIAL CM.
If we stumble onto an issue, you want us to send the report?
Update: Been using it for a little under 3 hours, with a mix of Wi-Fi and can confirm that Data works in San Antonio Texas, it's been amazing. After everything settled in and downloaded all my apps, I installed TricksterMod to use the Interactive Governor, it runs very smooth. In addition, will confirm that both SMS & MMS Text messaging works, and Wi-Fi Tethering works. Thank you SO Much LLoir and everyone who is working on this. It really is amazing. I can't say that enough. Okay, just got done trying my Bluetooth headset, audio on games works as for music as well, but alas sadly not for calls, however, I am going to try a wired headset to see if that works.
sledgeharvy said:
If we stumble onto an issue, you want us to send the report?
Update: Been using it for a little under 3 hours, with a mix of Wi-Fi and can confirm that Data works in San Antonio Texas, it's been amazing. After everything settled in and downloaded all my apps, I installed TricksterMod to use the Interactive Governor, it runs very smooth. In addition, will confirm that both SMS & MMS Text messaging works, and Wi-Fi Tethering works. Thank you SO Much LLoir and everyone who is working on this. It really is amazing. I can't say that enough. Okay, just got done trying my Bluetooth headset, audio on games works as for music as well, but alas sadly not for calls, however, I am going to try a wired headset to see if that works.
Click to expand...
Click to collapse
yes please ALL bugs, please make sure you have the xda 2013 theme on (bottom left corner on the site) so you can see the bug report tab. Also you will be able to see the Q&A section CM10.2 ATT thread, where you can ask questions
all questions should go to that section please
thanks
Data/WiFi working great (no lte here so can't test), messaging too, and whole ROM seems to be running very smoothly. Almost faster than stock I'd say and the phone seems to run at about the same temperature - though not as hot as usual when using a lot of data. Didn't encounter any unmentioned bugs and not had any crashes in my day of use, seems pretty stable. Nice job Lloir, honestly the only thing keeping me from using this is the call/audio issue. You've got an awesome start here, thanks for all the hard work!
guys please use the Q&A section or even the review tab (you need the XDA 2013 theme on)
thanks
Any update on the status? I'm itchy to try this out but would really like phone audio before I do.
loftwyr said:
Any update on the status? I'm itchy to try this out but would really like phone audio before I do.
Click to expand...
Click to collapse
Updates will be posted by the OP. FYI, that's a no no question too. Rest assured lloir is working on it unless otherwise stated by lloir.
Sent from my HTC One X+ using XDA Premium HD app
I'm currently running new builds, based on the AT&T X+ 4.2.2 leak
right now i'm updating lib's
Lloir said:
I'm currently running new builds, based on the AT&T X+ 4.2.2 leak
right now i'm updating lib's
Click to expand...
Click to collapse
is there a link to the leak??
TheJokah said:
is there a link to the leak??
Click to expand...
Click to collapse
if you can get access to my pc? sure, but i'm not going to be the target of a HTC c&d notice
short answer no.
Keep us updated. So excited!
later today, i will upload a build purely to see if people pre-4.2.2 can still flash + boot the rom with the old hboot...as i cannot use previous builds with the new 4.2.2 hboot
so yea....in a few hours check the downloads tab for a new download
Lloir said:
later today, i will upload a build purely to see if people pre-4.2.2 can still flash + boot the rom with the old hboot...as i cannot use previous builds with the new 4.2.2 hboot
so yea....in a few hours check the downloads tab for a new download
Click to expand...
Click to collapse
Still running Solomon's PA 4.2.2 build from Feb 19th. I'll assume I'm using the old hboot, then, so I'll try the build when it's posted!
Having a few issues with ril (data/gsm) at the moment, along with WIFI
the plus side looks like GPS is fixed, but can't confirm it 100%
more soon
don't go quoting this damned post here, but post in Q&A
Working as of now:
Camera
Video Camera
GPS (not sure if 100% yet)
GSM
Audio
Lights
Touch Screen
BT
MTP
Borked :
Not tested in call audio yet
WIFI (50% borked)
DATA (Kind of, doesn't connect to the interwebs)
SELinux (will be the last thing i fix)
Dialer app (phone.apk)
Thread Cleaned and Members please report vice posting against others, and I will ask any & all to watch their language, regarding profanity.
Thank You.
[Q&A] [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam
Q&A for [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Just registerd to say thank you for 5.0 android!
Only yours build is working awesome! NFC, camera, battery life is exelect! I'm very glad. One problem is that i can't put some widgets on desktop... it crashes and reappearing without my widget.
Why you didn't update your thread, and what is differences in your build(for exmpl. the 2th of December and the 9-th)?
nikudim said:
Just registerd to say thank you for 5.0 android!
Only yours build is working awesome! NFC, camera, battery life is exelect! I'm very glad. One problem is that i can't put some widgets on desktop... it crashes and reappearing without my widget.
Why you didn't update your thread, and what is differences in your build(for exmpl. the 2th of December and the 9-th)?
Click to expand...
Click to collapse
I haven't gotten to the point with cm-12.0 where I'm comfortable "advertising" it yet. Once I get it building with linaro, and get init.d scripts and some other goodies working I'll do a new thread. As it stands, it's very much the same as brothaedhung's with some extra kernel kangs and some device tree tweaks.
As far as widgets go, I'm not sure as I haven't seen that issue. Could you describe the issue with some more detail, and get a logcat if possible?
Thanks for the kind words though
ronasimi said:
I haven't gotten to the point with cm-12.0 where I'm comfortable "advertising" it yet. Once I get it building with linaro, and get init.d scripts and some other goodies working I'll do a new thread. As it stands, it's very much the same as brothaedhung's with some extra kernel kangs and some device tree tweaks.
As far as widgets go, I'm not sure as I haven't seen that issue. Could you describe the issue with some more detail, and get a logcat if possible?
Thanks for the kind words though
Click to expand...
Click to collapse
Oh, you won't believe I just disable "Don't keep activities" and it works now!!!:laugh:
The problem was when i tried to put Clock for expl. the launcher crashes and appearing again without my widget. Now, i've put my widgets and turn on "Don't keep activities". Perfect! I could not spot any problems, yet!!! Good luck with developing, and thanks again!
ronasimi said:
02/03/2015 - Sorry guys, I've been slacking off on updating this post. All current builds are using my KK kernel brought up for LP, with stock frequencies instead of low_cpuclocks. I'll be posting a new build later this morning. As far as I know, this is the only CM build still using mako sources
Click to expand...
Click to collapse
Noticed this over here after looking in the Canadian section (which has most certainly be dead for a while). Great to see you're still active on this. Just want to make sure before trying this that there's nothing else required to move from KK to LP (assuming not since its on a KK kernel still). Any particular recovery recommended and/or version? I'm on a Bell E973 using PAC 4.4.4-RC2, TWRP 2.6.3.1.
Edit: Decided to update recovery to 2.8.4 from brothaedhung after doing some lurking around. Flashed 02/03 and full stock PA gapps. Everything butter so far. Cheers!
@ronasimi : Latest build is working fine, in call screen is also normal, just sensors not working some times,,
thanks..
Click to expand...
Click to collapse
I have the same issue in your latest CM12. Proximity and brightness don`t work at all. I use jb e970 modem. Don`t flash hybrid radio because I`m in Russia. Also there isn`t any frequence low than 300 Mhz...
And I try your build of CM11: 20141111. There are a lot of bugs:
1. In profiles doesn`t work ring mode "normal". It doesn`t swith to it after another modes (vibrate and mute).
2. Don`t work "Double tap to sleep"
3. In perfomance dont`t work setting minimal and maximum frequency - after rebooting they are turned to default.
I have e970 will it work with this rom?
dro3 said:
I have e970 will it work with this rom?
Click to expand...
Click to collapse
It works. You should give a try to the CM12.1 version. :good::good::good:
ryupunk said:
It works. You should give a try to the CM12.1 version. :good::good::good:
Click to expand...
Click to collapse
I have tried it but my phone gets signal lost many times
"ap watchdog bark detected"
Help!
Since i flashed 12.1 rom, this message with green screen appears frequently!
5.1.1 CM12.1 Unofficial, Watchdog Kenel Panics (green screens)
long post, so if you want the meat of the story scroll down!
hi guys, i'm an avid user of the e970 and i found this marvelous forum to be one of the most useful resources ever. freegee, lgnpst for when i bricked my phone, cm11, cm12, solid geeb kernel, validus, and now cm12.1 unofficial; it's all there. i'm certainly enjoying the experience that this device paired with this community has to offer.
first i'd like to thank the developers, and i'm seriously appreciating the active development on 12.1. i just finished using validus and while it was a much more solid experience than the short-lived cm12, android 5.0 was still killing me in terms of battery life. 5.1 certainly fixed that up though.
i want to second a few observations that are being made, which are the green-screen happenings. i want to mention something in particular though:
when i first flashed 12.1 unofficial i didn't have the recommended gapps at the time, so i flashed the minimal gapps for 5.0 (just to get wheels rolling per se). sure enough, it was a crazy experience. com.google.<insert service name here> was crashing repeatedly, often causing loss of functionality or green-screens. in a day i'd get anywhere between 4 and 7 green-screens (this was for three days, i'm talking about the 4/21 release). i re-wiped and formatted /system and re-installed 4/21 cm12.1, along with the recommended gapps this time.
NOW i'm having far fewer crashes, far fewer slow-downs and stutters; overall a much more lean experience. i also want to especially thank the developer for one thing: THANK YOU, for giving me back HSPA+ speeds on my att jb radio. validus and cm12 for some reason wouldn't give me HSPA speeds, just slow HSPA speeds that would take forever to peak at 200, 250 K/s (averaging around 70 to 140 K/s). now i can enjoy speeds up to 900 K/s (i'll run a speed test when a more stable release comes out)
so, is it gapps or a kernel issue? newer gapps reduced a lot of problems (though that's a given). also i'd like to point out another error: wi-fi. the mac address keeps changing upon reboot, namely the last three hex values. the first three are always 00:11:22. this wouldn't bother a lot of everyday users, but my workplaces utilizes mac filtering (only way around it is to use the battery-intensive 3g option instead, and i have terrible 3g reception at work where i sit; OUTSIDE my office, i get great reception, but it's bloody hot here x.x)
in any event, if someone could help me out or give me some advice that'd be great.
to summarize:
5.0 gapps + cm12.1 = lots of watchdog events
5.1 gapps + cm12.1 = a lot LESS watchdog events, still happening though
wi-fi mac address gets randomly generated at reboot
phone doesn't get detected by the computer on usb unless you leave it plugged in and do a soft reboot (advanced reboot option; common in most cm12.x instances with default kernels; solid geeb was better, and cm11 was flawless pretty much)
using built-in kernel
att jb radio
clockworksmod touch recovery, the last one (6.0.1.8 i think? it's the last one on their website)
4 gig micro sd card is in the slot, if that makes a difference
one more note: i'm having far fewer crashes on this new install maybe because there are only google related apps (other than whatsapp which i installed right away). future planned apps to be installed:
adobe acrobat
battlenet authenticator
es file explorer
facebook messenger
titanium backup
mx player
aedict japanese dictionary
busybox
greenify
orpheus music player
qr code reader
skype
supersu
terminal emulator
any increase in instability henceforth i'll let you know. also for anyone NOT having greenscreens on the e970, do you have whatsapp? if NO, interesting. if YES, still interesting, but please what version? mine's not the latest (yet)
blitz9826
so this is new:
after reaching 100% battery level on charge, the phone used to cool down. ever since switching to this rom, the battery DOESN'T cool down, it stays warm/hot. i know for a fact it's not a charger issue since i'm charging it with the same usb port as i have been in hte past (and every other phone for that matter on the same port)
any ideas?
blitz9826
sensors
Sensors isnt working. 28.04 build.
Will you fix it?
Icons are blurry?
Hey. Loving this ROM so far. Only problem is that the icons are blurry (not HD as usual). I wiped the cache and delvik cache but it's the same problem. Anyone know how to fix this? Thanks.
ronasimi, i am waiting, that you will read this. Please try to fix sensors in your unofficial 12.1 builds. I really want use your rom, but sensors is not working.
I have e970 with mako z30f bootloader, and latest twrp.
Auto rotation
The auto rotation is not working. Only staying in portrait. Can anyone help?
Mobile Data to Wifi Switching
@ronasimi
first of all thanks for the Great rom im using from almost a month with no issues at all.
Just a little question about wifi. Wifi did not connect automatically when my phone is locked. I've to wake it then WiFi connects immediately.
same is when im using mobile data and saved WiFi is in range. but phone will connect it,until i wake the device.
please help me out on this.
[SOLVED] Problems rooting 12.1 E971
Edit: For anyone else facing this issue, flashing the beta version of SuperSU from a custom recovery works.
On a previous 12.0 build I was able to get root just fine, but after clean flashing the latest 12.1 build no method seems to work. I've tried flashing the latest SuperSU update zip from TWRP, using adb to push su and busybox, and using the built in root in developer options.
Flashing the zip and using adb result in SuperSU saying there is no binary installed, and with the root in developer options it never pops up something asking for permission.
Has anyone gotten root on the latest 12.1? Thanks in advance.
Cm 12.1 Bluetooth Issue on E971
Thanks for the great rom. Works great except one minor. Bluetooth connection on and off consistently.
I have cm-12.1-20150521-UNOFFICIAL-geeb.zip rom installed.
Thanks!
Thank you for your hard work on the ROM.
On an E971 with a clean flash, as others above have reported, the sensors/auto rotation are not working.
Another request would be to add repo specifics on your description of the ROM at the start of the thread. You link to your github account where the repos are stored but there are many of them, some with similar names. I am interested in reproducing your build process and possibly contributing some changes, but I am not sure which specific device, vendor and kernel repos you are using to generate the build. Would love to get rotation sorted out and keep development going on this solid 5.1 option for a still capable device.
Still kind of suprised that CM isn't doing 12.1 builds for E973/E971 but it seems they have dropped a large number of phones with the move to 5.0/5.1 and angered a lot of people.
Thanks!
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
As active user of the MadCatz MOJO, I found it pitty that rom development halted, mainly because the Android-TV rom from Unjustified Dev has some limitations.
As a result I've done quite some reading on "how to create an android rom from source" in the last 4+ weeks, in the hope that I could improve the work of Unjustified Dev.
In my attempt to understanding building the android source code to create my "own" Android-TV rom, I was succesfull in creating my first CM ROM (took 2h30)
(Big thanks to the source on https://github.com/TeamRegular?utf8=%E2%9C%93&q=mojo )
changelog:
Code:
[B][U]cm-12.1-20171226-UNOFFICIAL-mojo[/U][/B]
- fixed media server crashes, audio is again functional :)
- included the Tegra note 7 - widevine L1 DRM libraries (testing required)
[B][U]CM-12.1-20171222-UNOFFICIAL-mojo[/U][/B]
- Fixed hardware identification
- added DRM libs to support for widevineDRM
[U][B]BUG [/B][/U]: No audio - mediaserver crashes :(
[U][B]cm-12.1-20171216-UNOFFICIAL-mojo[/B][/U]
- changed boot animation to google animation (I like it more then the CM one)
- changed default dpi = 240
- removed not functioning multi rom code
[STRIKE]- synced media profiles to be inline with ADT-1 and cm-13 tree[/STRIKE]
[STRIKE]- added google media_codecs_performance[/STRIKE]
- applied some cm-13 changes to sync tree.
[B][U]BUG[/U][/B]: Play store seems broken,
[U][B]cm-12.1-20171208-UNOFFICIAL-mojo[/B][/U]
- Included nvcgcserver - should fix chrome issues with streaming.
- Applied kernel patch to increase from 3.4.57 -> 3.4.59
[U][B]cm-12.1-20171203-UNOFFICIAL-mojo[/B][/U]
- The update is a minor Android build update : LMY48G -> LMY49J
- Security level set to November 2016
[URL="http://www.androidpolice.com/android_aosp_changelogs/android-5.1.1_r36-to-android-5.1.1_r37-AOSP-changelog.html"]http://www.androidpolice.com/android_aosp_changelogs/android-5.1.1_r36-to-android-5.1.1_r37-AOSP-changelog.html[/URL]
Location of the ROM:
Code:
File name : cm-12.1-20171226-UNOFFICIAL-mojo.zip
[URL="https://drive.google.com/open?id=1SpF5dcRg7kHYstTQtGrTTzus4e7p6fAy"]https://drive.google.com/open?id=1SpF5dcRg7kHYstTQtGrTTzus4e7p6fAy[/URL]
File name : cm-12.1-20171208-UNOFFICIAL-mojo.zip
URL : [URL="https://drive.google.com/open?id=1ocMDgBCHDC4VV8rYBtEuQUHq81xhtSa2"]https://drive.google.com/open?id=1ocMDgBCHDC4VV8rYBtEuQUHq81xhtSa2[/URL]
File name : cm-12.1-20171203-UNOFFICIAL-mojo.zip
URL : [URL="https://drive.google.com/open?id=1KctTiSn8Hv8IiHGPZXDa7A_I4cDbZ29l"]https://drive.google.com/open?id=1KctTiSn8Hv8IiHGPZXDa7A_I4cDbZ29l[/URL]
Next step:
- fix issue : https://forum.xda-developers.com/showpost.php?p=69887922&postcount=393 the post should contain enough info
- gaining more ROM development skills
- build AndroidTV-5.1 rom or CM13
Side note: I'm not as experienced as Unjustified Dev, so a "mayor" update can take a while,
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Mad Catz M.O.J.O.
Contributors
carp_be, EdoNINJA93
Source Code: https://github.com/dide0
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Current Beta Version: 5.1.1_r37
Beta Release Date: 2017-12-03
Created 2017-12-04
Last Updated 2018-05-21
CM13 would be very nice. I was trying as well but my skills are to low for + no time
( i'm from Belgium 2 btw )
Wmapa said:
CM13 would be very nice. I was trying as well but my skills are to low for + no time
( i'm from Belgium 2 btw )
Click to expand...
Click to collapse
Same here only time in the weekend to do some stuff. I hope to release a new build on sunday
carp_be said:
Same here only time in the weekend to do some stuff. I hope to release a new build on sunday
Click to expand...
Click to collapse
Will you work on cm13? It is way better than android tv if we use toplauncher it is very tv friendly
Thank you so much, OT!
Yeah, I also would prefer a Marshmallow or Nougat based ROM, since you can do more stuff with them and you can get an Android TV experience whenever you like by simply using 3rd party launchers.
Keep it up the good work!
Main fixes I'd like to see:
- Chrome fix (I know you just have to put a separate file inside a specific folder, but it would be better to fix it by scratch by installing a fresh new and optimized ROM)
- Netflix fix
- Wi-Fi activation fix (on both CM 12 and CM 12.1 for Mojo the Wi-Fi activation works randomly after you boot the device and you have to restart the console everytime it doesn't)
While I expect the nvgcserver/Chrome fix would be baked in eventually, I think perhaps you are expecting a bit much of this poster's already-declared skill set when it comes to fixes. I'd love to see these things fixed (especially the WiFi bug - urgh!), but I'm not pressuring the individual as it is obviously just a nice weekend pass time for him/her.
However, good luck and I look forward to what comes next if it becomes possible for you. Clearly there are one or two of us MOJO faithful still keeping an eye on developments. Keep us posted. I'm pretty sure folks will perhaps send a donation or two your way if things do become viable for you.
New release
cm-12.1-20171208-UNOFFICIAL-mojo now available As I don't have Netflix/Amazon , please let me know if the this new build fixed the streaming issues in Chrome. I checked the forum posts, they mentioned setting the permissions on this file. I check the source code and this should be done by default in the building process.
While I expect the nvgcserver/Chrome fix would be baked in eventually, I think perhaps you are expecting a bit much of this poster's already-declared skill set when it comes to fixes. I'd love to see these things fixed (especially the WiFi bug - urgh!), but I'm not pressuring the individual as it is obviously just a nice weekend pass time for him/her.
However, good luck and I look forward to what comes next if it becomes possible for you. Clearly there are one or two of us MOJO faithful still keeping an eye on developments. Keep us posted. I'm pretty sure folks will perhaps send a donation or two your way if things do become viable for you.
Click to expand...
Click to collapse
thanks
For me it's indeed a hobby project for the weekend, I really like programming but besides writing some simulation software for work projects, I'm not in the programming/embedded development business. I already did a lot of reading in the Github changes/commits on the ADT-1 (molly) and TeamRegular repo's. It should be possible to create a CM13 rom as the ADT-1 has a working rom, CM14 is not working atm on the ADT-1 so I don't expect that I could provide such update.
Currently I'm focusing on the CM12.1 branch as there is a working "rom" (see above ) and trying to add Android TV on this. The ADT-1 has such ROM, so it must be possible on the MOJO. I'm busy merging the changes from ADT-1 to MOJO but atm my build is stuck in a boot loop.
- Wi-Fi activation fix (on both CM 12 and CM 12.1 for Mojo the Wi-Fi activation works randomly after you boot the device and you have to restart the console everytime it doesn't)
Click to expand...
Click to collapse
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
carp_be said:
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
Click to expand...
Click to collapse
It happens only on both CM12 and CM12.1 roms for the Mojo.
I think the issue is kernel related, but I could be wrong.
carp_be said:
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
Click to expand...
Click to collapse
I have experienced this on both CM12.1 and Remix OS. Two things can happen:
Firstly, if you are using an SD card in your MOJO and you have this plugged in at boot, it's a lottery as to whether or not the console will boot up with any WiFi. I'm no expert at all, but by this I mean that it appears that the WiFi module doesn't even load into the system. It cannot be turned on or off as it is all greyed out. As I say, this doesn't happen on every boot up, but is very annoying when it does.
Secondly, if you decide to fix this by not using an SD card in your MOJO, the WiFi will be better but still not great compared to the stock OS. Sometimes it never connects on fresh boots, meaning I have to go into WiFi settings and switch off and on again several times before it connects properly. Then on other times very odd things happen when it does connect. For example, quite often I have experienced when downloading big app updates for example, it seems to "flood" the WiFi if that doesn't sound silly, which results in every one in the house complaining that our router has kicked all their devices off the WiFi and they can no longer get any connection. The MOJO itself also disconnects when this happens. The only thing I can do then is to reboot the router.
I am assured none of these things happen on the stock OS.
Good luck with your builds. I myself would love to see CM13, as I use a modified TV Launcher to polish things off. My fear with the Android TV system is it won't recognise my 2TB external drive, which would mean I couldn't use it. Remix had issues with it also. CM12.1 has no problems at all mounting it and allowing me access to my media files.
Great work ! Tested - nothing broken
Keep going !
no luck today with AndroidTV, did several builds but after Android boots and optimizes it's App's and then it got stuck in starting the App's . I've not found a way yet to read out debug info during boot, so i'll invest some time on that subject. Next weekend the hunt continues.
EdoNINJA93 said:
It happens only on both CM12 and CM12.1 roms for the Mojo.
I think the issue is kernel related, but I could be wrong.
Click to expand...
Click to collapse
I've not seen this on the AndroidTV build of Unjustified Dev, so i'll diff it once with my build and see if there are driver changes.
rahsoft said:
Great work ! Tested - nothing broken
Keep going !
Click to expand...
Click to collapse
Could you please provide a feedback about Netflix and Wi-Fi issues?
carp_be said:
no luck today with AndroidTV, did several builds but after Android boots and optimizes it's App's and then it got stuck in starting the App's . I've not found a way yet to read out debug info during boot, so i'll invest some time on that subject. Next weekend the hunt continues.
Click to expand...
Click to collapse
Replace
Code:
persist.sys.usb.config=none
by
Code:
persist.sys.usb.config=adb
in default.prop and build.prop, this will enable usb debuging during boot.
rahsoft said:
Great work ! Tested - nothing broken
Keep going !
Click to expand...
Click to collapse
More info plz!
Is WiFi any better? What apps do you use?
K-Project said:
More info plz!
Is WiFi any better? What apps do you use?
Click to expand...
Click to collapse
I dont use Wifi - I use ethernet. Heard that Wifi works better without microsd in slot...
From what I tested - everythink works like before. I mean no new bugs
Some programs and Youtube on some videos just silent closes.... But this was on all CM 12.1 builds for mojo. Sound volume bug is still here but it is not critical.
Is it any way to add ethernet interface / config settings ?
P.S. Programs used: HD VideoBox, Torrent Stream Controler, MX Player, VLC, Archos Video player (for SPDIF), Youtube, Chrome, Total Commander, Simple Reboot, Set Orientation, SuperSU and so on...
P.S.2. Maybe it will be better set dpi to 240 in build.prop by default...
rahsoft said:
I dont use Wifi - I use ethernet. Heard that Wifi works better without microsd in slot...
From what I tested - everythink works like before. I mean no new bugs
Some programs and Youtube on some videos just silent closes.... But this was on all CM 12.1 builds for mojo. Sound volume bug is still here but it is not critical.
Is it any way to add ethernet interface / config settings ?
P.S. Programs used: HD VideoBox, Torrent Stream Controler, MX Player, VLC, Archos Video player (for SPDIF), Youtube, Chrome, Total Commander, Simple Reboot, Set Orientation, SuperSU and so on...
P.S.2. Maybe it will be better set dpi to 240 in build.prop by default...
Click to expand...
Click to collapse
The playback issues could be related to DRM content. I saw that the CM build don't have the "google widevine" libraries included, while the AndroidTV build has. I'll include this in the next update,might solve the issue. Otherwise If you get a logcat file, the exception thrown by the app could shed some light what is needed.
besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="1980x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="1920x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
DPI can be changed to 240, will do (need to adjust ro. sf.lcd_density in system.prop file) .
Log
View attachment 2017-12-12-17-54-04.txt
Made little log - maybe will help
Please look at:
Process com.google.android.youtube (pid 10272) has died
Process com.lolapp.lolapptv (pid 22409) has died
Process ru.norgen.homevideo (pid 26606) has died
carp_be said:
...besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="1980x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="1920x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
Click to expand...
Click to collapse
Unless I'm going mad, which is quite possible, both those lines are exactly the same!
K-Project said:
Unless I'm going mad, which is quite possible, both those lines are exactly the same!
Click to expand...
Click to collapse
carp_be said:
...besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="[COLOR="yellowgreen"][B]1980[/B][/COLOR]x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="[B][COLOR="YellowGreen"]1920[/COLOR][/B]x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
Click to expand...
Click to collapse
Are you sure?