Since there are a lot of questions that get asked repeatedly, I'm going to start up a FAQ thread.
Q: Why doesn't multiwindow work?
A: Multiwindow is still a work in progress. It's 90% working but that last 10% (such as the fact that it breaks Google+ layout) is proving to be much more difficult to polish than expected, and everyone who was working on it has been very busy keeping on top of community contributions and core project work. Progress can be followed at https://gerrit.omnirom.org/#/c/1510/ - Please do not comment there unless you are able to build Omni with the patch yourself have a specific suggestion on how to improve the code. (No UI/UX suggestions please, only code - finishing the code is difficult enough as it is.)
Q: Is my device officially supported?
A: Check http://dl.omnirom.org/ - The device support page sometimes is out of date, while the downloads page is ALWAYS current.
Q: Is my device unofficially supported?
A: Check your device's own communities, don't ask in the general omni communities. Sadly, many unofficial maintainers don't communicate with the team at all, or do so very poorly. If your device becomes supported, support is going to come from a maintainer in your device's development community, not from the core Omni project unless you're lucky and have a device that one of the team is interested in for their own personal reasons.
Q: Where do I report bugs?
A: The official bug reporting system is at http://jira.omnirom.org/ - This is only for devices in the list on dl.omnirom.org
Q: Will you support my device?
A: Just like with other projects, for a device to be supported requires that it have a maintainer. We're already short on maintainers and spread a bit thin, so your best bet is to go to your device's own forums here on XDA. Any device support requests posted in the general Omni forums will be reported to the moderators for moving to device-specific forums.
Q: Why don't I have root?
A: We were planning on integrating an opensource version of SuperSU but Chainfire hasn't had the time to finish that up. The rest of us have been pretty busy too. The recommended approach is to install SuperSU from recovery (If you were able to flash Omni, you have a custom recovery capable of flashing SuperSU) and then choose the "Install backup script" option in SuperSU's settings. (The ease of flashing SuperSU is why most of us haven't put too much effort into getting this cleaned up.)
In addition to this, apps which block usage on rooted devices are proliferating, and many corporate policies forbid using a device that is rooted on their network. It's easier for users who need root to flash SuperSU or another solution in recovery than it is to try and remove root. (I realize that as of July 2014, Omni is partially rooted - 'adb root' and 'adb remount' work, we'll be looking into removing this for nightlies eventually in order to allow more users to run Omni when connected to a corporate network.)
Q: What happened to nightlies for jflteatt/jfltexx/other jflte carrier-specific variants?
A: They were replaced by a unified jflte build. jflte supports all individual variants that previously received their own builds. You must manually transition to the new builds by downloading from http://dl.omnirom.org/ before resuming usage of OpenDelta
Q: When will *foo* happen?
A: We do not give ETAs. This is because usually, if we knew exactly what was needed to finish something, we'd likely have already finished it.
Q: Why am I not getting updates for my device with OpenDelta?
A: There are a few possible causes for this. One could be that your device's name changed or it was unified into another device build. (Carrier variants of t0lte and jflte are in this category. Carrier-specific builds such as jflteatt and jfltexx stopped when the unified jflte build started) Another could be that the OpenDelta "update chain" was broken - it happens sometimes. For example anyone stuck on a February 17 build of t0lte or n7100 needs to manually update from dl.omnirom.org
http://dl.omnirom.org/ is always the definitive place to find the latest official build for a device
Q: What are the official IRC channels for Omni?
Development - #omni
Users - #omnirom
Q: I sat in an IRC channel for 30 minutes and got no response, why doesn't anyone talk to me?
A: Many of us are hardcore idlers that never log out even when we leave the house for more than a day. If you ask a question and log out before we return to the keyboard, you won't get an answer. I strongly suggest you learn the Art of the Idler like most of us have. It could take a few hours for someone who knows the answer to your question to see it and respond.
Q: I PMed a developer on IRC and got no response, why?
A: See above about us being hardcore idlers. In addition many of us might not see a PM because it's buried way down on our channel list.
In general, unless it ABSOLUTELY has to be private for some reason, you should not be PMing any developer. For one, the Omni team believes in transparency - we want to keep as much discussion in the open as we can. For another, often someone other than the person you PMed could help you.
Also, in general, when pinging people or asking a question, don't ask if you can ask a question - get straight to it. Most of the developers don't like "naked pings" (pings without any real information or question) - see http://blogs.gnome.org/markmc/2014/02/20/naked-pings/ for a great writeup of why.
e.g.
Code:
<someuser> ping Entropy512
is not an efficient way to communicate
but
Code:
<someuser> ping Entropy512 re: https://gerrit.omnirom.org/#/c/7373/
is MUCH better
*reserved 1*
*reserved 2*
*reserved 3*
What is an omni rom whats its specifications? Can any one suggest link or info page?
Thanks
Sent from my N9000W using Tapatalk
Entropy512 said:
Since there are a lot of questions that get asked repeatedly, I'm going to start up a FAQ thread.
Q: Why doesn't multiwindow work?
A: Multiwindow is still a work in progress. It's 90% working but that last 10% (such as the fact that it breaks Google+ layout) is proving to be much more difficult to polish than expected, and everyone who was working on it has been very busy keeping on top of community contributions and core project work. Progress can be followed at https://gerrit.omnirom.org/#/c/1510/ - Please do not comment there unless you are able to build Omni with the patch yourself have a specific suggestion on how to improve the code. (No UI/UX suggestions please, only code - finishing the code is difficult enough as it is.)
Q: Is my device officially supported?
A: Check http://dl.omnirom.org/ - The device support page sometimes is out of date, while the downloads page is ALWAYS current.
Q: Is my device unofficially supported?
A: Check your device's own communities, don't ask in the general omni communities. Sadly, many unofficial maintainers don't communicate with the team at all, or do so very poorly. If your device becomes supported, support is going to come from a maintainer in your device's development community, not from the core Omni project unless you're lucky and have a device that one of the team is interested in for their own personal reasons.
Q: Where do I report bugs?
A: The official bug reporting system is at http://jira.omnirom.org/ - This is only for devices in the list on dl.omnirom.org
Q: Will you support my device?
A: Just like with other projects, for a device to be supported requires that it have a maintainer. We're already short on maintainers and spread a bit thin, so your best bet is to go to your device's own forums here on XDA. Any device support requests posted in the general Omni forums will be reported to the moderators for moving to device-specific forums.
Q: Why don't I have root?
A: We were planning on integrating an opensource version of SuperSU but Chainfire hasn't had the time to finish that up. The rest of us have been pretty busy too. The recommended approach is to install SuperSU from recovery (If you were able to flash Omni, you have a custom recovery capable of flashing SuperSU) and then choose the "Install backup script" option in SuperSU's settings. (The ease of flashing SuperSU is why most of us haven't put too much effort into getting this cleaned up.)
In addition to this, apps which block usage on rooted devices are proliferating, and many corporate policies forbid using a device that is rooted on their network. It's easier for users who need root to flash SuperSU or another solution in recovery than it is to try and remove root. (I realize that as of July 2014, Omni is partially rooted - 'adb root' and 'adb remount' work, we'll be looking into removing this for nightlies eventually in order to allow more users to run Omni when connected to a corporate network.)
Q: What happened to nightlies for jflteatt/jfltexx/other jflte carrier-specific variants?
A: They were replaced by a unified jflte build. jflte supports all individual variants that previously received their own builds. You must manually transition to the new builds by downloading from http://dl.omnirom.org/ before resuming usage of OpenDelta
Q: When will *foo* happen?
A: We do not give ETAs. This is because usually, if we knew exactly what was needed to finish something, we'd likely have already finished it.
Q: Why am I not getting updates for my device with OpenDelta?
A: There are a few possible causes for this. One could be that your device's name changed or it was unified into another device build. (Carrier variants of t0lte and jflte are in this category. Carrier-specific builds such as jflteatt and jfltexx stopped when the unified jflte build started) Another could be that the OpenDelta "update chain" was broken - it happens sometimes. For example anyone stuck on a February 17 build of t0lte or n7100 needs to manually update from dl.omnirom.org
http://dl.ominrom.org/ is always the definitive place to find the latest official build for a device
Q: What are the official IRC channels for Omni?
Development - #omni
Users - #omnirom
Q: I sat in an IRC channel for 30 minutes and got no response, why doesn't anyone talk to me?
A: Many of us are hardcore idlers that never log out even when we leave the house for more than a day. If you ask a question and log out before we return to the keyboard, you won't get an answer. I strongly suggest you learn the Art of the Idler like most of us have. It could take a few hours for someone who knows the answer to your question to see it and respond.
Q: I PMed a developer on IRC and got no response, why?
A: See above about us being hardcore idlers. In addition many of us might not see a PM because it's buried way down on our channel list.
In general, unless it ABSOLUTELY has to be private for some reason, you should not be PMing any developer. For one, the Omni team believes in transparency - we want to keep as much discussion in the open as we can. For another, often someone other than the person you PMed could help you.
Also, in general, when pinging people or asking a question, don't ask if you can ask a question - get straight to it. Most of the developers don't like "naked pings" (pings without any real information or question) - see http://blogs.gnome.org/markmc/2014/02/20/naked-pings/ for a great writeup of why.
e.g.
Code:
<someuser> ping Entropy512
is not an efficient way to communicate
but
Code:
<someuser> ping Entropy512 re: https://gerrit.omnirom.org/#/c/7373/
is MUCH better
Click to expand...
Click to collapse
The link to to omni ROM website doesn't work
^ There's just a typo on the last (bottom) link to omni downloads page.
The others work fine : http://dl.omnirom.org/
AngryHapposai said:
^ There's just a typo on the last (bottom) link to omni downloads page.
The others work fine : http://dl.omnirom.org/
Click to expand...
Click to collapse
Good catch, thanks for specifying which specific link was broken. Should be fixed now.
Related
Hey guys, sorry if this is an obvious question.
I'm trying to get my facts straight on the various CyanogenMod builds.
1.) First, what is going on with Official CyanogenMod and HD2/Leo? Are we in the process of transitioning to "Experimental" (a la the Galaxy S)? There is HD2 specific code in the github repository, but no official support? From reading the "unofficial nightly" thread, it sounds like certain steps are being taken to ensure the HD2 code is in compliance with various programming practices required by CyanogenMod devs? Is this explanation anywhere close to the current state of things? Will the HD2 eventually get a subforum with Experimental (and eventually Stable) downloads in the CM forums? Or, as others have said, will our WinMo base prevent official support from ever happening?
2.) Just to confirm -- the unofficial nightly build is more of an actual "from the ground up" build, whereas the other ROMs are derivatives of other builds? Is there any easy explanation of the differences that someone with some slight programming exposure might understand?
Thanks in advance for any advice you might have to offer.
EDIT: P.S. Please don't take this as "Why don't we have .... yet?" whining. I'm just trying to wrap my head around the whole AOSP/Cyanogenmod issue.
I posted irresponsibly. Sorry dudes!
Announcement:
I have sold my Galaxy S2 and will be getting my Galaxy Nexus on the 25th of January, 2011. As such, from that date onward, I will no longer update this thread. I will gladly copy and paste the template of this post to anyone who wants to continue doing this. If you wish to continue this thread, please PM me (do not post here). If no-one who is willing to continue this thread contacts me by the 25th, I will message the mods to close and unsticky this thread.
Please Read:
This is not the place to voice your opinions, nor is it the place to ask your questions. It is, however, a place to get the latest updates as they come in from the CM9 team.
My aim is to have one place to receive CM9 updates, instead of having to go through several websites / G+ accounts / Twitter accounts.
Disclaimer: I am in no way related to the CM9 team
Current Status:
[Last updated on 18/01/12]
New version out:
1) 2stage boot (now for real)
2) Cleaned up ramdisk / desamsungized
Current Release:
[Last updated on 25/12/11]
The team has released an experimental, unsupported build of CM9. XDA thread here, and the blog post here.
Known issues here.
People to follow:
Codeworkx
Blog: Link
G+: Link
Twitter: Link
Xplodwild
Twitter: Link
IRC
#CMSGS at freenode.net
If you have anyone else to add, please PM me and I'll add them as quickly as possible.
Latest Youtube Videos
[Last updated on 22/12/11]
Exclusive hands-on (pre)review by site Android Next, uploaded on December 22nd, 2011. Watch it here.
Uploaded by codeworkx on December 19th, 2011. Watch it here.
Uploaded by XplodWild on December 13th, 2011. Watch it here.
Frequently Asked Questions
[Last updated on 03/01/12]
Q: I downloaded the latest CM9 build, but [XXX] isn't working!
A: Search! Search the CM9 threads, search Google, but for the love of God - please first search for the answer! If you did, and could not find it, you have three options:
1) Read this, it might very well answer your question.
2) Check out the live support chat But search first.
3) Go here and ask your question. But search first. Did I mention you should search first? You should search first.
In any case, if your question or query is not directly related to development, please do NOT post in the development section!
Q: I can't connect my phone to my PC! What can I do?
A: This is a known issue. There are several ways you go around this - either by downloading to your PC a program called Droid Explorer, or by downloading any of the wi-fi file transfer apps on the market.
Q: When I start up the Superuser app, it crashes! What do I do?
A: Users are reporting success by searching for Superuser updater on the Market, installing it, and forcing an upgrade.
Q: I can't buy apps from my phone! What can I do?
A: This is a known bug. The only way to buy apps right now is through your home computer. Refunding is reported working on the phone, though.
Q: When I download a big app from the market, I get an error message! What can I do?
A: This is a known bug. Nothing can currently be done about it, unless you already downloaded the app and have it backed up. In that case, there is an advanced work around that you can find by searching the CM9 threads.
Q: I heard Codeworkx got a Galaxy Nexus, is he going to stop supporting the Galaxy SII?
A: Nope, not currently. Actually, it means he can use his Nexus for day to day use, and only focus on development on his GSII. This is in our favor.
Q: I found and downloaded an ICS ROM by Airbus360, I heard its better than CM9, is that true?
A: Apparently, Airbus360 simply took what the CM team has been building, added a few useless lines of code (read: they don't do anything), and claimed that its faster. He also pretty much claims to be doing most of the hard work when in fact, he isn't adding much of anything.
If you have anymore frequently asked questions to add, please PM me and I'll add them as quickly as possible.
Thanks
To all the devs who put in the time and effort to make our phones shine.
To Stylez and Conantroutman, for their continuous support in managing this thread.
To Matriak for keeping the community up to date while he could.
To everyone who post updates here while I am away.
Note: If any updates come through between 21:30 - 05:00 UTC, they will not be reflected here because I will most likely be sleeping
[REF] Galaxy SII CM9 Progress
Reserved...............
[REF] Galaxy SII CM9 Progress
Reserved.................
Thread cleaned.
Please do not post as thread is open to allow OP to keep updated posts will be removed.
CarbonDev said:
About Carbon
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. and on our Gerrit CarbonDev Gerrit.
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 whenever possible 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.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
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.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Click to expand...
Click to collapse
These builds are for the Samsung Galaxy Exhibit and the Samsung Galaxy Ace 2e.
Models:
SGH-T599
SGH-T599N
SGH-T599V
Download: meticulus.co.vu
GApps here
Known issues:
Screenrecording locks up device. ( do not use )
Moving apps to SD does not work. Reports "not enough space" or something similar. FIXED! see here
OTG Host mode only works once per boot.
If GApps are not flashed there is a ramdom reboot issue due to issue with gps blog. Not an issue as long as you flash GApps.
Setting a govenor via "PerformanceControl" may not work due to "Usecase" control.
Offline Charger options via "Extras" do not work.
Root is disabled by default. Some options in "Extras" and "Performance" depend on root. Enable in "Developer Options"
Thanks for all your work.
Good to see you back at it on the T599.
Tried you latest. Seems to work quite well.
Thanks again.
Sent from my BN Nook HD using XDA Free mobile app
Moving apps to the SD card is FIXED! see here
New Build!
New Build: http://www.meticulus.co.vu/2016/07/new-build-carbon-lp-511-for-galaxy.html
Update released : http://www.meticulus.co.vu/2016/07/carbon-lp-511-for-galaxy-exhibit-ace2e.html
Several bug fixes...
Another Update Release: http://www.meticulus.co.vu/2016/08/carbon-lp-511-for-galaxy-exhibit-ace2e.html
Encryption fixed.
Hang at "Finishing Boot" fixed.
...
Progress on MM: http://www.meticulus.co.vu/2016/09/progress-on-marshmallow-for-codinalte.html
WOWWW you are back! I thought this phone was already forgotten. Let me try this on my old t599n with stock laggy tw 4.1.2 with internal memory for only 2 or 3 apps.
Can't wait for MM rom.
Great work and welcome back!!
Update: Hi @Meticulus , I am using this rom and I like it. I got just some little issues:
First: Is the Carbon sources updated? I ask this because i see in my language (portuguese) there are lot of words not translated (when i was on cm 12.1 in my s5 didnt face this issue), i see that the security patch is November 2015 (a bit old no?)
Second: I don't know why but i can't install facebook... it took like 5 minutes to install and then it fails with error -504 on playstore
BTW great work man, I really wanna try your CM 13 on this machine
Keep it up
If anyone is reading this, I've noticed http://www.meticulus.co.vu is down (probably for years). Is there any way to obtain the 5.11 Carbon ROM ? I have two old T599N devices that I want to "resurrect/upgrade". I've googled a lot but could not find any download links for the 5.1.1 Carbon ROM created by Meticulus for this device. I also tried searching for this in DC hubs but without success. Thank you!
Checklist of Things to Do w/ Axon 7
1. Unlock Bootloader - DONE
2. Flash TWRP - DONE
3. Get Root Access, along with Root apps - DONE
4. Flash Cyanogenmod 13.1 - PENDING
Who is interested in seeing Cyanogenmod 13.1 running on the ZTE Axon 7 as much as I am? If so, please post on this thread. Hopefully, the right people will check this out and get the ball rolling on this project.
Why don't you build it ? ?
We are never happy ... let the devs work ... on the other hand they have a life and bills to pay !
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app
like tupirujp says.
If you want your question answered just contact Cyanogen directly.
***Thread Cleaned*** (removed negative, counterproductive comments/quotes, for a fresh start)
Some concerned users brought this thread to the attention of Moderation staff.
A good practice is to have the dev needing the device (Unjustified Dev) set up their own donation link, express their desire to dev for the device, and put out a little description of the work they intend to do for that device (ie; unlock bootloader, Roms , Kernels, etc)...
Otherwise, third party donation links usually only raise suspicion, mistrust, and rarely accomplish the goal of helping the dev get a device.
I applaud those who want to support developers (they certainly deserve the support), let's make sure we do it in a way that isn't counterproductive to the goal or the donation process.
Thanks for your cooperation.
Well, in order to build a rom you need:
Device Tree
Kernel
Vendor/Proprietary files
We have versions of the first two already loaded on GitHub. It's a (hard) matter of someone figuring out what proprietary files we need and then going through the iterative testing to ensure all the hardware components are working. So, let the devs have time with the phone to see what they can figure out and we'll start seeing development.
Please Cyanogenmod come to this device..
Hello,
I'm strongly considering picking up a LePro 3, but I do have some concerns. I understand that the stock software isn't very good and I'm looking towards the community to create excellent ROMs for this device, but I do have some questions:
Do we have a clean method for root/unlock/recovery?
Is there anything stopping developers from putting together ROMs that are optimized for every aspect of the phone? i.e. enough source from LeEco?
How would you say developer support is for this device? I'm a fan of official ROM builds instead of using unofficial. Has anyone announced upcoming support for this device that I can look forward to?
Aside from that, feel free to mention anything else I should be aware of before purchasing the phone!
Thanks so much!
Do we have a clean method for root/unlock/recovery?
I have no idea what you mean by clean but if you can use adb then yes we do. If you are looking for a one stop shop all in one unlocker then the answer is no. look here for current method:
http://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
Is there anything stopping developers from putting together ROMs that are optimized for every aspect of the phone? i.e. enough source from LeEco?
I believe all source code has been released.
How would you say developer support is for this device? I'm a fan of official ROM builds instead of using unofficial. Has anyone announced upcoming support for this device that I can look forward to?
There is minimal development currently. One person is trying to build a Nougat 7.1 Rom. That's a pretty big feat so it will probably be a while. Look here:
http://forum.xda-developers.com/le-pro3/how-to/7-1-progress-t3511474
There is a developer that posted a debloated version of the x720(international version) of this rom already. It will work on our x727(US version). It is an older version though so there's that. Look here:
http://forum.xda-developers.com/le-pro3/development/rom-google-edition-cydras-t3514742
xiton said:
There's a CM 13 rom here based on the chinese x720. Look here:
http://forum.xda-developers.com/le-pro3/how-to/cm-13-lex720-t3508015
Aside from that, feel free to mention anything else I should be aware of before purchasing the phone!
This is literally the smallest compilation of threads I've ever seen for a phone so starting a new thread to ask these questions is pretty silly. Since it's the holidays, I've been nice and responded to what could have easily been found in a couple of minutes.
Click to expand...
Click to collapse
Thanks for the reply.
The reason I compiled these questions were because I was hoping for more specific answers and some clarity. Perhaps I wasn't clear enough my initial post and for that I apologize.
I was reading what seemed to be conflicting information about the recovery software and process in which to flash it to the device. It looked as if there wasn't any goto method or specific TWRP version to go with and that this was still somewhat experimental.
It's good to know that the source has been released. I was seeking info about LeEco and people were saying that they didn't release source code for their phones as company policy.
While I've visited the ROM forum section, I was hoping someone would have insight into official ROMs instead of what currently exists there.
For the US model Le Pro 3 (X727) I would recommend using this (http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388) method to unlock the bootloader. That's what I did and had no issues. From there you can use TWRP to do a full wipe and install the ROM of your choice. Of course, I would recommend taking a backup of everything before doing this.
I'm running that CM 13 build with no issues on my X727. It's also possible to get the IR blaster working if desired.