There are times when the Official ROMs like LINEAGE Os has issues that are haunting users universally. These issues are need to be dealt with some logcats. But jira don't work that way. Jira was not regular report thread its official bug tracker for any ROM. Like Dirty Unicorns has its own. But this is specifically for LINEAGE Os.
Recently i created a bug report for gallery on jira and i felt that if more people up vote for it, there are more chances that LineageOs developers will look into the issues.
Please make sure you get proper bug report on jira. Just don't come here and fire a report without making sure you log has all things needed for the issue.
I hope this will server the purpose.
PLEASE PASTE BUGBASH(REPORT) link here....
PLEASE UPVOTE this. Gallery is not playing gif images by default. There is no support by current gallery for same.
https://jira.lineageos.org/browse/BUGBASH-589
Related
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.
Hey Guys. @ishubhamsingh needs a group of testers who can test ROMs for him. As someone stole his device, he can't test ROMs by himself. So Please, If anyone wants to test Roms for him along with me, PM Me or @ishubhamsingh.
Roms : AOKP, BrokenOS ( Builds posted on G+), CandySiX, Beanstalk, Nameless etc.
Thank You
Help will be appreciated.
Also you can contact us on Telegram. @AmolAmrit & @ishubhamsingh.
Thread closed to avoid the posting of personal contact details in an open, public Forum. The OP has provided adequate *private* contact details in the first post.
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!
Hi, I found a ROM around the web of Android Nougat 7.1 for our Z3. It seems is under development but it boots and works. I don't know the issues or problems that it has so I wanted to post it to try it and make known. The rom is here: dl.myself5.de/leo/CarbonROM/
It is not my project, is from Myself5 that I think is user of XDA. All the recognitions towards him.
If this topic is not in the correct forum, please the admins move it.
I'll check that. I have a z3 free to test
Enviado desde mi F8331 mediante Tapatalk
ipsilonf said:
Hi, I found a ROM around the web of Android Nougat 7.1 for our Z3. It seems is under development but it boots and works. I don't know the issues or problems that it has so I wanted to post it to try it and make known. The rom is here: dl.myself5.de/leo/CarbonROM/
It is not my project, is from Myself5 that I think is user of XDA. All the recognitions towards him.
If this topic is not in the correct forum, please the admins move it.
Click to expand...
Click to collapse
That rom IS 5.1 Lolipop, not Nougat.
Are you actually serious?
What do you think, why is there no thread for this already? Everyone I shared this link with I told its very early WIP, and not to share it.
I uploaded the builds so that I can download them to my laptop, and that some people who wanted a 7.1 build were able to use it.
While you even know that those are my builds, you did at no point think about sending a PM to me, asking if its ok to create a thread for it.
With that, I just deleted all prereleases of Carbon from my server, never ever expect me to release some preview or WIP builds again.
That does not only count for leo. Have fun being responsible for the deletion of all testbuilds for leo, aries, sumire and i9100.
@caqo71 that assumption is wrong. CR-5.1 is the internal versioning number for Android 7.1 (same as CM is using 14.1). Those builds were Android 7.1.0_r7.
I reported the thread, hoping to get it closed, and I will reference it every time someone asks me where the preview builds did go to. Have a very fun time on XDA.
EDIT: In case it was unclear: I am not against you posting builds of Carbon on XDA, of cause the whole team invites people to compile Carbon for their devices. What I am sepecifically against here, is that, instead of putting your own effort in here, and compiling it on your own, you made a thread about my builds, which is totally not ok, especially not without asking me.
Thread closed.
You cant just share stuff you find on the internet. You need to follow the forum rules (rule 12) before you decide to share it
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