Database Users

[REF] [18/01/12] [Announcement] Galaxy SII CM9 Progress

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.​

[FAQ] Omni FAQ - READ BEFORE POSTING

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.

Cyanogenmod 13.1 for Axon 7... When?

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..

LineageOS development [unofficial][To-Start]

Okay people, i know things do not look very good for this device, and yeah, we all are frustrated with the fact that no one is building any good rom(except this Resurrection Remix(on http://forum.le.com/in)) for this device.
I am thinking of trying to build the LineageOS for this device.
I am new to building roms, I have not developed any rom before, so this will be my very first experience.
I would very much appreciate any help that any of you may offer regarding any thing.
Be it any tutorial/guide, source codes, testers, or any thing else you have in mind.
I would be downloading the sources today and will look around for tutorials for porting roms with source code that i already have (thanks to that resurrection remix ROM dev 19wisnia89(on http://forum.le.com/in)).
I would also be contacting other devs of other devices for any help regarding the porting process and stuff.
If you know these stuff and would not mind helping me out, it would be very nice.
Please quote me on the reply here or PM me with anything here
Note: I would be needing testers because i don't quite own the device for myself, it's my mother's and i can't risk tempering with it, but I still want it to have a dev support.

All the best for the success, I also tried to compile the kernel and the source code is working completely fine without any modification but I was confused about the process of building the android So I will always help you whenever needs my help. and if you can guide me to building guide then i will also love to try that.

sscsps said:
Okay people, i know things do not look very good for this device, and yeah, we all are frustrated with the fact that no one is building any good rom(except this Resurrection Remix(on http://forum.le.com/in)) for this device.
I am thinking of trying to build the LineageOS for this device.
I am new to building roms, I have not developed any rom before, so this will be my very first experience.
I would very much appreciate any help that any of you may offer regarding any thing.
Be it any tutorial/guide, source codes, testers, or any thing else you have in mind.
I would be downloading the sources today and will look around for tutorials for porting roms with source code that i already have (thanks to that resurrection remix ROM dev 19wisnia89(on http://forum.le.com/in)).
I would also be contacting other devs of other devices for any help regarding the porting process and stuff.
If you know these stuff and would not mind helping me out, it would be very nice.
Please quote me on the reply here or PM me with anything here
Note: I would be needing testers because i don't quite own the device for myself, it's my mother's and i can't risk tempering with it, but I still want it to have a dev support.
Click to expand...
Click to collapse
all the best...we are here for testing!!

sscsps said:
Okay people, i know things do not look very good for this device, and yeah, we all are frustrated with the fact that no one is building any good rom(except this Resurrection Remix(on http://forum.le.com/in)) for this device.
I am thinking of trying to build the LineageOS for this device.
I am new to building roms, I have not developed any rom before, so this will be my very first experience.
I would very much appreciate any help that any of you may offer regarding any thing.
Be it any tutorial/guide, source codes, testers, or any thing else you have in mind.
I would be downloading the sources today and will look around for tutorials for porting roms with source code that i already have (thanks to that resurrection remix ROM dev 19wisnia89(on http://forum.le.com/in)).
I would also be contacting other devs of other devices for any help regarding the porting process and stuff.
If you know these stuff and would not mind helping me out, it would be very nice.
Please quote me on the reply here or PM me with anything here
Note: I would be needing testers because i don't quite own the device for myself, it's my mother's and i can't risk tempering with it, but I still want it to have a dev support.
Click to expand...
Click to collapse
If you are on Telegram(app)
you could join us few devs and testers in this group and ask for anything you need
here is invite & join link:
https://t.me/joinchat/AAAAAEEHPrwCrEYn3uf6BA

Abhi_ said:
hey i first want you to tell me what you know about building?
Because you have mentioned you will look around for porting roms,etc.
I hope you know how linux works.
That's it
if you have queries feel free to ask
If you are on Telegram(app)
you could join us few devs and testers in this group and ask for anything you need
here is invite & join link:
https://t.me/joinchat/AAAAAEEHPrwCrEYn3uf6BA
Click to expand...
Click to collapse
I have gone through the porting guide on CM wiki(through archive.org) a couple of times and a few more places, I have not downloaded the source code of Lineage os, but I have source code of cm13, so i'll build it first,

Resurrection Remix 6.0 Oreo Redmi Note 3(Kenzo)(Official)

Greetings to all RR users
First and foremost we would like to thank you all for being patient for the RR-Oreo release.
We , Team RR would like to announce that the wait is finally over .
Today we will be releasing first builds for RR-OS based on Android 8.1.0 .
A selected devices will get this build today (not all) because this has been a sudden release .It will take time for maintainers to apply and start maintaining to we request you to be a little more patient for that .
As maintainers know, they can apply to maintain for the device by making a pull request on our Settings app against your device name .
We apologize again for the delay for this version as Google rebased their entire trees when coming from 8.0 to 8.1.0 which would have cost us time anyways .
We sincerely thank you and hope you enjoy this build as it comes with a great ton of features and some large UI improvements in RR configurations and other fixes in code since RR 5.8.5.
Builds will be shipped rootless.
It's themable and supports OMS Oreo substratum themes .
Unfortunately there have been no translations for RR settings yet so translators can contribute at.
We hope you have a great weekend . Please follow proper flashing instructions and present a proper logcat on finding issue .
Last and foremost we'd like to thank LineageOS as our rom is based on it . Also a HUGE thanks to all the open source Roms out there (there are too many to list) that have a large contribution to the features presented in RR .It could not have been possible without them.
Downloads will be up on (FOR KENZO ONLY):
I will comment the link down below.
‎
If your device isn't showing , wait for your maintainer to upload the build . It's a kind request for users to refrain from asking for ETA of each device . It will come when it's ready
Happy flashing!
I'm not the developer but i can answer all your Questions!
<Mod Edit>
Thread Closed.
Official link here:
https://forum.xda-developers.com/redmi-note-3/development/rom-resurrectionremix-5-8-0-t3507433

what is the purpose of the thread ??????///

The purpose of this thread is to share the rom.
agriculture said:
what is the purpose of the thread ??????///
Click to expand...
Click to collapse
The purpose of this thread is to share the rom.

hasaber8 said:
The purpose of this thread is to share the rom.
Click to expand...
Click to collapse
Are you the maintainer?
Sent from my Redmi Note 3 using Tapatalk

Close this thread. The official thread is here.
https://forum.xda-developers.com/redmi-note-3/development/rom-resurrectionremix-5-8-0-t3507433

This