{
"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"
}
What is Omni?
Omni Gerrit Review
Disclaimer
Code:
#include
/*
* 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. Hard. A lot.
*/
DOWNLOADS:
omni-7.0-20161022-mako-HOMEMADE.zip
Because of the nature of Xposed framework, NO SUPPORT will be given to those running Xposed framework on Omni 6
CHANGELOG:
Code:
[CENTER]
2016-10-22:
-Video recording fixed on stock camera (snapdragon camera still have some issues there, jerky video)
-Omni features progressively backported
2016-10-4:
Initial Release[/CENTER]
You MUST DO A FULL WIPE, whether you are coming from homemade builds (aka my builds), or a previous version of OmniROM. Be certain to do a full backup of your data, apps, call logs, sms/text and so on before flashing.
GAPPS must be flashed BEFORE initial boot, they will NOT work properly if you flash them afterwards !!!
KNOWN BUGS:
Code:
[CENTER]- Camera recording only works with Google Camera
- Screen rotation isn't working
[/CENTER]
Omni only supports TWRP recovery, use any alternate recovery at your own risk.
RECOMMENDED TWRP
Source
OmniROM Source
Only a few changes are taken from CyanogenMod, but thanks to them for those
CyanogenMod Source
XDA:DevDB Information
OmniROM 7, ROM for the Google Nexus 4
Contributors
kldoc, MaR-V-iN, Maxwen, Entropy512, Xplodwild, Jiangyi
ROM OS Version: 7.x Nougat
Based On: AOSP
Version Information
Status: Testing
Created 2016-10-04
Last Updated 2016-10-21
Wow.... already?
Thanks for the hard work! Any features?
ddaggebi said:
Wow.... already?
Thanks for the hard work! Any features?
Click to expand...
Click to collapse
More or less the same features than in Omni 6, everything is being backported.
Battery led and custom notification led will be there in next build.
We expect android 8
Why such a hurry !?
Before you refine the A-7 will have A-8.
Of course it was a joke, but journalists already predict the future:
Android 8 : ce que l'on attend
ze7zez said:
Why such a hurry !?
Before you refine the A-7 will have A-8.
Of course it was a joke, but journalists already predict the future:
Android 8 : ce que l'on attend
Click to expand...
Click to collapse
Mostly because I'm in vacations, and got the time this week to do the bringup for Nexus 4, then OmniROM got gerrit fixed so we could merge everything that needed to, from there, things go quite fast, team is actually quite efficient
I noticed a few kernel side commits i didn't merge yet, so tomorrow's build, you should expect a few things fixed, rotation should be fixed, and some omnigear stuff are coming back
Do you know if the future official omni 7 will require full wipe if coming from official omni 6???
Sent from my Nexus 4 using Tapatalk
mandgeo said:
Do you know if the future official omni 7 will require full wipe if coming from official omni 6???
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I think I stated it the header, yes, it will be needed to avoid any problem, Android 7 has a lot of changes.
New build delayed for tomorrow, have been hard at work trying to solve the camera video recording, failed. Rotation is fixed.
Video recording seems to be a recurring issue on Android 7 for older devices, and none of the ROM I checked managed to really fix it for good. From there, I'm not actually certain it will ever get fixed, and because of this, I don't know if Nexus 4 will reach nightlies or not. I will publish builds as OmniROM features get backported, but won't go any further than this.
Given Google's pricing for Pixel, I am soon buying a Oneplus 3, and will switch to it for OmniROM support.
I'm not giving up totally on Nexus 4, but dev won't be as up to date as it was when I did Marshmallow or Lollipop.
Hi all! I have been wondering if Snapdragon camera is included, cuz that's the only thing stopping me from switching to Omni 7 or CM 14?
Chefov01 said:
Hi all! I have been wondering if Snapdragon camera is included, cuz that's the only thing stopping me from switching to Omni 7 or CM 14?
Click to expand...
Click to collapse
Yes, Snapdragon Camera is included, it's actually replacing the stock AOSP camera, only video recording is broken on Nexus 4 atm, that's what I was mentioning earlier, no one has this properly working 100%, camera itself is able to take pictures, no issues there, but just video recording isn't possible atm.
I remember stepen wolf with cm 14 unofficial figuring on how ot fix it. but I am not sure if he has done so as of yet or not. but he di state it was on hhis list of things to do to fix the rom. so whwho knows between you and stepean with cm14 you guys can figure it eventually.
---------- Post added at 01:35 PM ---------- Previous post was at 01:18 PM ----------
just read his post he still has the same issue with camera video recording having issues it will record in 720 p ok but with 1080p has issues. so he will be working on it. so hopefully between kldoc and stepan the issue will get resolved.thats the only issue with nexus 4 having had the AOSP 7 rom on my nexus 4 over 2 months now. kldoc I am also agreeing with you google made a big disservice to the developer by raising the price of the pixel for the development community. as soon as I have some fund I will be joining in support and getting a 1 plus 3 as well. the only thing will be to get older nexus device and keep them up to date and then going forward go with other vendor to prove to google that they are not the only premium product with a outrageous price that the development community cant afford and then will end up jumping ot other product lines to support going forward in the future . that's one thing that google has now gotten out of touch with its community. they are forgetting that the development community got them to the big Android dance. The developers developers . I respect what all you guys and gals do here on XDA for all of us!!!!
mrk2815 said:
I remember stepen wolf with cm 14 unofficial figuring on how ot fix it. but I am not sure if he has done so as of yet or not. but he di state it was on hhis list of things to do to fix the rom. so whwho knows between you and stepean with cm14 you guys can figure it eventually.
---------- Post added at 01:35 PM ---------- Previous post was at 01:18 PM ----------
just read his post he still has the same issue with camera video recording having issues it will record in 720 p ok but with 1080p has issues. so he will be working on it. so hopefully between kldoc and stepan the issue will get resolved.thats the only issue with nexus 4 having had the AOSP 7 rom on my nexus 4 over 2 months now. kldoc I am also agreeing with you google made a big disservice to the developer by raising the price of the pixel for the development community. as soon as I have some fund I will be joining in support and getting a 1 plus 3 as well. the only thing will be to get older nexus device and keep them up to date and then going forward go with other vendor to prove to google that they are not the only premium product with a outrageous price that the development community cant afford and then will end up jumping ot other product lines to support going forward in the future . that's one thing that google has now gotten out of touch with its community. they are forgetting that the development community got them to the big Android dance. The developers developers . I respect what all you guys and gals do here on XDA for all of us!!!!
Click to expand...
Click to collapse
Feedback i have, is most devices actually have camera issues on Android 7, things will eventually smooth out and get polished
I still have a build to publish today, been working on that camera issue, but also working on cleaning up stuff to get that on OmniROM's gerrit and github.
I checked his work, but he's more or less at the same point everyone else is, sill no real solution atm.
Oh and by the way, my builds are also Selinux enforced
will be patiently waiting ot test the next build you have out for nexus 4.thanksfor maintaining and building android 7 for nexus 4.
Uploading the new build as we speak, Battery light are back, Custom notification lights are also back (didn't in Omni 6).
Rotation is fixed, battery display is back, and a lot of Omni features are back, doze mode isn't there yet, but should be soon.
EDIT: Link in the OP updated, enjoy
Have fun with OmniROM !
P.S.: I merged my commits on Omni repos for kernel and device trees
Awesome ROM, keep up the good work.
However, there are some issues I noticed;
1. Can't seem to change the SELinux mode to Permissive with SELinux mode changer.
2. Permission requests appear as in the screenshot with no way to take an action (can grant from settings though).
Btw, is SuperSU integrated into the ROM?
kanishkad said:
Awesome ROM, keep up the good work.
However, there are some issues I noticed;
1. Can't seem to change the SELinux mode to Permissive with SELinux mode changer.
2. Permission requests appear as in the screenshot with no way to take an action (can grant from settings though).
Btw, is SuperSU integrated into the ROM?
Click to expand...
Click to collapse
No you will not be able to change SELinux to Permissive rom within the system, if you want to run OmniROM permissive, you need to build it by yourself, OmniROM (not only me) is really strict about this. The initial build was permissive, but it was a proof of concept. Android N changes a lot of things, there might be bugs here and there, but SElinux is relatively working well now.
Permission granting, i will have to check things on that, but ROM is barely coming together, 80% of our maintained devices are barely uploading a semi working build, will ask your for a bit of patience
Supersu never was a part of OmniROM, and probably won't be anytime soon (if ever).
A screenshot without a logcat is more or less useless ...
kldoc said:
No you will not be able to change SELinux to Permissive rom within the system, if you want to run OmniROM permissive, you need to build it by yourself, OmniROM (not only me) is really strict about this. The initial build was permissive, but it was a proof of concept. Android N changes a lot of things, there might be bugs here and there, but SElinux is relatively working well now.
Permission granting, i will have to check things on that, but ROM is barely coming together, 80% of our maintained devices are barely uploading a semi working build, will ask your for a bit of patience
Supersu never was a part of OmniROM, and probably won't be anytime soon (if ever).
A screenshot without a logcat is more or less useless ...
Click to expand...
Click to collapse
Just to clarify if my post seemed like a complaint, this is awesome work and really glad that devs like you are keeping a 4 year old device alive Just wanted to point out the issues I faced in order to help you make it better..
I was able to set it to permissive by the command "setenforce 0". Need it to get Viper4Android working
I will post a logcat if I encounter any issues. Keep up the good work :good:
kanishkad said:
Just to clarify if my post seemed like a complaint, this is awesome work and really glad that devs like you are keeping a 4 year old device alive Just wanted to point out the issues I faced in order to help you make it better..
I was able to set it to permissive by the command "setenforce 0". Need it to get Viper4Android working
I will post a logcat if I encounter any issues. Keep up the good work :good:
Click to expand...
Click to collapse
Oh, I wasn't aware Viper4Android was still being maintained, external modifications aren't something we bring support to, mostly because it changes initial behavior and it's hard to predict what changes towards drivers support throughout system updates.
Someone in Omni pointed me at a modified video recording handling ( coming from slimrom actually), will give it a shot tomorrow.
I'm also planning to enable LTE support for those who need it in the future, even though I won't be able to test it (China's network don't handle those frequencies)
kldoc said:
Oh, I wasn't aware Viper4Android was still being maintained, external modifications aren't something we bring support to, mostly because it changes initial behavior and it's hard to predict what changes towards drivers support throughout system updates.
Someone in Omni pointed me at a modified video recording handling ( coming from slimrom actually), will give it a shot tomorrow.
I'm also planning to enable LTE support for those who need it in the future, even though I won't be able to test it (China's network don't handle those frequencies)
Click to expand...
Click to collapse
Your existing build actually already picked up LTE for me, with no modifications needed. Working just fine on my end
Sent from my Nexus 4 using Tapatalk
DontPushButtons said:
Your existing build actually already picked up LTE for me, with no modifications needed. Working just fine on my end
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Good to know, wasn't intended If it works well, glad that you're happy with it
Related
{
"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"
}
The Open ROM
Omni is a community-based project for the Android community which is Free^3:
Free to Use, Free to Modify, Free to Share. It's also about options, which is the beauty of Android
Introduction - What is OmniROM?
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. Our goal is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap.
Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
What's Working
Support for old and new partition setups
Sound
Data / LTE
Voice
SMS
WiFi
Notification Lights
Sensors
GPS
other features TBD
What Needs Work
Under certain conditions (constant back and forth from 1x/evdo<->ehrpd/lte) the RIL will take it's ball and go home. This one I'm still working on getting sorted, but in the mean time toggling airplane mode will make it act right.
TBD - Let me know if you find more!
Downloads
See post #2
Code:
Disclaimer: Unless required by applicable law or agreed to in writing, this work is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the software and assume any risks
associated with your use of any information or software provided to you.
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate
and grossly negligent acts) or agreed to in writing, shall any contributor be liable to you for damages, including any direct, indirect, special, incidental,
or consequential damages of any character arising as a result of this or out of the use or inability to use the software (including but not limited to
damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such contributor has
been advised of the possibility of such damages.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and
the section as a whole is intended to apply in other circumstances.
XDA:DevDB Information
Omnirom-jewel-unofficial, a ROM for the Sprint HTC EVO 4G LTE
Contributors
xHausx
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information
Status: Beta
Created 2013-10-23
Last Updated 2013-12-27
Downloads
DevDB Download Page (Torrent)
Dev Host Unofficial Test Builds
omni-4.3.0-20131022-jewel-HOMEMADE.zip - 161.42 MB
omni-4.3.0-20131022-jewel-HOMEMADE-multiwindow.zip - 164.84 MB
omni-4.3.1-20131027-jewel-HOMEMADE-2.zip - 165.80 MB
omni-4.3.1-20131028-jewel-HOMEMADE.zip - 166.09 MB
omni-4.4-20131113-jewel-HOMEMADE.zip - 171.79 MB
omni-4.4-20131204-jewel-HOMEMADE.zip - 174.71 MB
omni-4.4.1-20131206-jewel-HOMEMADE.zip - 175.06 MB
omni-4.4.1-20131209-jewel-HOMEMADE.zip - 175.49 MB
omni-4.4.2-20131226-jewel-HOMEMADE.zip - 174.53 MB
omni-4.4.2-20131228-jewel-HOMEMADE-4.zip - 174.53 MB
omni-4.4.2-20131230-jewel-HOMEMADE.zip - 174.52 MB
omni-4.4.2-20140107-jewel-HOMEMADE.zip - 174.34 MB
omni-4.4.2-20140109-jewel-HOMEMADE.zip - 164.60 MB
omni-4.4.2-20140111-jewel-HOMEMADE.zip - 164.30 MB
omni-4.4.2-20140117-jewel-HOMEMADE.zip - 165.04 MB
omni-4.4.2-20140202-jewel-HOMEMADE.zip - 164.46 MB
omni-4.4.2-20140227-jewel-HOMEMADE.zip - 164.07 MB
omni-4.4.2-20140314-jewel-HOMEMADE.zip - 164.14 MB
omni-4.4.2-20140331-jewel-HOMEMADE.zip - 163.57 MB
Official Nightlies
Gapps
4.3 Gapps
OFFICIAL 0-Day PA-GOOGLE APPS (All ROM's) - PA gapps are recommended for OmniROM
Recovery
Patched TWRP for SE Linux Compatibility - courtesy of kushdeck
Native 4.4 TWRP with full SE-Linux support
Super SU
Sources
Device: https://github.com/omnirom/android_device_htc_jewel
S4 common: https://github.com/omnirom/android_device_htc_s4-common
Kernel: https://github.com/omnirom/android_kernel_htc_msm8960
Thanks
Thanks go out to everyone below and everyone who has contributed to AOSP, CM, Omni and the Evo in general. This wouldn't be possible without the prior work of many people to get our device running with AOSP.
kushdeck for kernel, device repos, and telling me what needed to be done to the kernel
Toastcfh, intervigilium & Flemmard for kernel and device repos
Everyone who has contributed to OmniROM
The entire Cyanogenmod team for all they've done for the community
Entropy512, xplodwild, CaptainThrowback, eagleeyetom, jmztaylor, Pulser, GoblinZ, shortyishere and everyone on XDA and in #htc-evo-4g-lte who has helped me along the way
Nice. I tried building Omni also, gonna use yours though. Wouldn't trust myself around a computer, let alone a rom
Sent from a non-i****
Awesome.. Something new to try..
-----Evo LTE..
Haus. To seeyou sharing is awesome. You've brought us a million so far (radios, downgrades, etc,...you've taken huge risks for the community. Anything yoibuild, I will try
Sent from my EVO 4G LTE using XDA Premium 4 mobile app
Awesome man I also got a build with this and got it booted but same issue I had with this ROM
Too much fun going on for our phone. Thanks Haus!!
Good stuff, bro. Now fix all teh borken stuffs .
Yeah I tried this one and had no radio on the current ota so it may only be good on 3.16 but I may try again later and give vanir as my daily but when I get home I will give this another shot
Sent from my EVO 4G LTE using XDA
zacnking said:
Yeah I tried this one and had no radio on the current ota so it may only be good on 3.16 but I may try again later and give vanir as my daily but when I get home I will give this another shot
Sent from my EVO 4G LTE using XDA
Click to expand...
Click to collapse
You DID read the OP, right?
Captain_Throwback said:
You DID read the OP, right?
Click to expand...
Click to collapse
THIS^^ and this..... (per OP)
*Cell service must be enabled by going to Settings -> More.. -> Mobile network settings -> CDMA subscription -> NV (Toggling airplane mode may be needed)
Ahh beat me to it good luck hope it works out great.
Sent from my EVO using XDA Premium 4 mobile app
Captain_Throwback said:
You DID read the OP, right?
Click to expand...
Click to collapse
I must have missed something in the fine print. . . that's probably why I'm still with sprint still as well :]
Sent from my EVO using XDA
numel007 said:
Nice. I tried building Omni also, gonna use yours though. Wouldn't trust myself around a computer, let alone a rom
Sent from a non-i****
Click to expand...
Click to collapse
If you still want to you should be able to build it by adding the three repos I linked to above to your .repo/local_manifests folder. For the proprietary drivers I used the ones from TheMuppets github, so I would recommend those as well.
To be honest I'm still fairly newbish when it comes to building from source as well, but now is as good a time as ever to learn.
untz1456 said:
Awesome man I also got a build with this and got it booted but same issue I had with this ROM
Click to expand...
Click to collapse
Were you able to get it with an up to date kernel? I ended up just rolling the entire kernel back to a few months ago where caf_2.6 was merged in, but unfortunately I removed a lot of important (security) patches in the process.
lreyes said:
Ahh beat me to it good luck hope it works out great.
Click to expand...
Click to collapse
The more the merrier, I think the GS3 (or one of the sammy devices, can't keep them all straight) already has four different builds. lol
One of the main reasons I posted this in it's current state was to hopefully help anyone else who was working on it. Plus, with the DevDB setup you can have multiple people as sort of co-owners for the project and let them edit the OP or accept ownership for the thread.
xHausx said:
If you still want to you should be able to build it by adding the three repos I linked to above to your .repo/local_manifests folder. For the proprietary drivers I used the ones from TheMuppets github, so I would recommend those as well.
To be honest I'm still fairly newbish when it comes to building from source as well, but now is as good a time as ever to learn.
Were you able to get it with an up to date kernel? I ended up just rolling the entire kernel back to a few months ago where caf_2.6 was merged in, but unfortunately I removed a lot of important (security) patches in the process.
The more the merrier, I think the GS3 (or one of the sammy devices, can't keep them all straight) already has four different builds. lol
One of the main reasons I posted this in it's current state was to hopefully help anyone else who was working on it. Plus, with the DevDB setup you can have multiple people as sort of co-owners for the project and let them edit the OP or accept ownership for the thread.
Click to expand...
Click to collapse
yeah i was able to for me all that it was missing was libs did u use evervolv source to build this ? or cm
Thanks for bringing this to the LTE xHausx. Of all the AOSP projects out there Omni ROM stands out. The concept and idea behind this project are what its supposed to be about. Definitely interested in where this goes.
Sent from my EVO using Tapatalk 2
untz1456 said:
yeah i was able to for me all that it was missing was libs did u use evervolv source to build this ? or cm
Click to expand...
Click to collapse
I forked from CM but so far everyone I found looks to have come from the htc-msm8960 group.
So looks like the only things broken are GPS and camera eh? I'm just going to assume that the GPS fix doesn't work here. Flashing soon!
Sent from my EVO using xda premium
numel007 said:
So looks like the only things broken are GPS and camera eh? I'm just going to assume that the GPS fix doesn't work here. Flashing soon!
Sent from my EVO using xda premium
Click to expand...
Click to collapse
It looks like GPS is due to the proprietary libs CM was using. I've got a new copy building that has updated props so hopefully that one will be good now.
edit: and the build failed, looks like it won't be quite that easy
xHausx said:
I forked from CM but so far everyone I found looks to have come from the htc-msm8960 group.
Click to expand...
Click to collapse
Hmm have u tried using evervolv kernel ? I think it might be the same as cm but it doesn't hurt to try since evervolv is aosp and they have their sources for 4.3
Edit: also try to get libs from other ROMs for camera and check if its the right size and what not
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 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 official Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
For mondrianwifi downloads:
CARBON-KK-UNOFFICIAL-20140429-0035-mondrianwifi.zip
CARBON-KK-UNOFFICIAL-20140612-2345-mondrianwifi.zip
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
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Reserved
Hey folks.
None of this would have been possible without the hard work of @crpalmer - he got the device started on CM, and did 99.999% of the hard work for this device bringup!!
I have done some basic tests - it boots!
The stock keyboard seems to be missing a lot - I'm sure installing an alternative will solve that issue. I'm also getting a lot of FC's from Google Keyboard.
CarbonFibers is not happy, going to look into that.
Should be on par with CM. Let me know what you find!
Thanks for developing for this device, will flash when I get a chance.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Does this ROM remove multi-window?
KrazyAttack said:
Does this ROM remove multi-window?
Click to expand...
Click to collapse
Well I suppose if you are comparing to stock, yes, it does "remove" multi-window...
Just remember, this ROM is not based (loosely or otherwise) on any Samsung ROM. It's built from source AOSP base with patches from all over the place.
Makes me wonder where Omni left off with their multi-window. I haven't been following it lately.
Thanks so much for the time and work you put into this. I love seeing more roms for this great device!
Sent from my SM-T320 using Tapatalk
arrrghhh said:
Well I suppose if you are comparing to stock, yes, it does "remove" multi-window...
Just remember, this ROM is not based (loosely or otherwise) on any Samsung ROM. It's built from source AOSP base with patches from all over the place.
Makes me wonder where Omni left off with their multi-window. I haven't been following it lately.
Click to expand...
Click to collapse
Yeah I assumed it did, I wish I could run a nice feature rich rom but I use multi window probably 80% of my time on this tablet. I almost always have YouTube on one half and chrome the other like right now haha. Wish there was a way to keep it or an alternative but thanks anyways.
Luckily my nexus 5 feeds my rom itch nicely. For now I'll just stay with CleanROM.
arrrghhh said:
Hey folks.
None of this would have been possible without the hard work of @crpalmer - he got the device started on CM, and did 99.999% of the hard work for this device bringup!!
I have done some basic tests - it boots!
The stock keyboard seems to be missing a lot - I'm sure installing an alternative will solve that issue. I'm also getting a lot of FC's from Google Keyboard.
CarbonFibers is not happy, going to look into that.
Should be on par with CM. Let me know what you find!
Click to expand...
Click to collapse
Dear @arrrghhh I am not a developer, but I have a little guess as to what might be causing the FC's on the google keyboard. The keyboard learns the user style and way of writing (if you see the T it has many settings that are probably intefering with the absence on Knox.
I'm excited about Carbon for this device, but seeing that there's been no activity in the thread for over a week has me wondering if something is wrong with it. I'm using cm 11 right now and it's very stable if lacking in features.
From my Pro Tab 8.4
JaylanPHNX said:
I'm excited about Carbon for this device, but seeing that there's been no activity in the thread for over a week has me wondering if something is wrong with it. I'm using cm 11 right now and it's very stable if lacking in features.
From my Pro Tab 8.4
Click to expand...
Click to collapse
CarbonFibers has a FC issue which has been resolved... but some of the customizations are still lacking because the CF app isn't really setup for tablets at the moment... so the experience is a bit off. I didn't see the value in updating until the issue is completely fixed, as most of the reason to run the ROM is in that area .
That makes sense. I'll follow the thread for updates. This is the closest ROM to SlimKat, which is my favorite.
From my Pro Tab 8.4
JaylanPHNX said:
That makes sense. I'll follow the thread for updates. This is the closest ROM to SlimKat, which is my favorite.
From my Pro Tab 8.4
Click to expand...
Click to collapse
I saw a SlimKat tree from crpalmer, so I am assuming he is going to bring that out / is working on that... because I was going to attempt that as well until I saw that tree
Cool. Thanks for the heads up.
From my Pro Tab 8.4
arrrghhh said:
I saw a SlimKat tree from crpalmer, so I am assuming he is going to bring that out / is working on that... because I was going to attempt that as well until I saw that tree
Click to expand...
Click to collapse
Nope, I have no intentions of doing a slim build. I was trying that to sanity check that I had things configured well enough to make it easy for people to use the CM device tree to build other ROMs.
I had it booting and working reasonably well except that there were external sdcard problems (at the very least the lack of exfat support).
I do think I had to cherry pick missing commits into a few slim repos but I have forgotten what that was.
crpalmer said:
Nope, I have no intentions of doing a slim build. I was trying that to sanity check that I had things configured well enough to make it easy for people to use the CM device tree to build other ROMs.
I had it booting and working reasonably well except that there were external sdcard problems (at the very least the lack of exfat support).
I do think I had to cherry pick missing commits into a few slim repos but I have forgotten what that was.
Click to expand...
Click to collapse
Ah ok. I'll roll a SlimKat build too, see how that runs... I haven't really seen any of these on a tablet, so it's kind of interesting to see the difference. Carbon, at least CarbonFibers definitely has some work to be done for tablets.
arrrghhh said:
Ah ok. I'll roll a SlimKat build too, see how that runs... I haven't really seen any of these on a tablet, so it's kind of interesting to see the difference. Carbon, at least CarbonFibers definitely has some work to be done for tablets.
Click to expand...
Click to collapse
I wonder if SlimKat will have better luck, since it doesn't centralize all of its features into one thing like Carbon Fibers. I think they just added the 2014 Note 10.1 as officially supported. I have no idea if there's any similarities between that and our Tab Pro or if that would help even if there were.
From my Pro Tab 8.4
Who wants to try out multiwindow?
{
"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"
}
It's definitely a bit quirky - and the issue with CarbonFibers is still present... but Bluetooth works great, so my builds of Slim must be missing something else outside of the device tree...
Great Rom
Just flashed new build. Works great so far. Thanks for the work.
So is this ROM finished now where there are no more updates going to be done?
Disclaimer:
Code:
[FONT="Book Antiqua"][SIZE="4"]All the firmwares, custom ROMs, official firmware updates, mods and tools mentioned here belong to their respective developers/owners.
You will be doing everything at your own risk.
We nor the developers cannot be held responsible if you end up damaging or bricking your device.[/SIZE][/FONT]
{
"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"
}
Introduction:
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion...
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Features:
-- Odexed for faster performance (only in official releases, nightlies are deodexed)
-- Incremental updates
-- OTA updates - update on the fly!
-- Native exFAT support (Samsung devices only)
-- ListView animations
-- Calendar - with lunar and solar calenders
-- Bulk SMS recipients
-- Adjustable SMS font size
-- SMS sending delay
-- Smart dialing
-- Speed dialing
-- IP dialing
-- Custom carrier name
-- Network speed in status bar (upload and download!)
-- Built in timer in Apollo - determine when to stop playing music
-- Unique Power Saver functions!
-- Custom screen off animations
-- Lockscreen notifications
-- Multiuser support
-- Smart Lock
-- Many more! Since we are constantly adding new features, see changelogs to keep updated!
Screenshots
The screenshots below gets outdated very fast!
Links:
-- Official website
-- Google Plus Community (join us for faster response!):
-- Statistics
-- Official Build Status
-- Bug Tracker
-- Changelogs
-- MoKee Github
-- MoKee Code Review
Downloads
-- ROM - UnOfficial - n7100
-- ROM - UnOfficial - t0lte
-- Latest Google Apps for Lollipop
Donations:
-- All donations will be used for build server.
You can scan this QR CODE to donate me by Alipay.
Installation Instruction
-- Make a backup of your ROM
-- Wipe data/factory reset
-- Format /system
-- Flash ROM
-- Flash Gapps
-- Reboot
Notes/Faqs
-- First boot might take a while around 5 to 10 minutes so don't panic, it will boot fine.
-- This ROM has not been tested with dual sim, so flash it by your own risk.
-- Working and Not working list is as same as CM12 unofficial Build
-- Restore from 4.4.4 rom is not recommanded (Do it at your own risk).
-- Download google camera for photos and video.
-- Use search button for your errors first and than put a query in here.
-- Do not ask ETA, it will not make release any faster than what it is.
Credits:
-- MoKee Developers
-- CyanogenMod
-- AOSP
-- Koush for open-sourced SuperUser
-- Slim Roms
-- OmniROM
从我的 iPhone 发送,使用 Tapatalk
Great to see new lollipop rom for n7105
---------- Post added at 05:24 PM ---------- Previous post was at 05:00 PM ----------
[/COLOR]Downloading now. Will report
Oh I do wish devs would write their own list of what's working instead of me having to have to research other ROMs threads for answers.
King Kaze said:
Oh I do wish devs would write their own list of what's working instead of me having to have to research other ROMs threads for answers.
Click to expand...
Click to collapse
So... It's not enough for builders/maintainers/developers to provide to you a free ROM on their own time and their own dime, but they should also be responsible to spend even more of their free time to dig up every issue/problem/bug and provide a specifically catered list for you, on demand, so that you can save a few minutes researching them yourself or installing the ROM to find out for yourself what may or may not work as you would like? Seems like a very reasonable and not at all selfish demand to me. Thank you for your most useful and helpful input.
Have a good one!
AzraelsKiss said:
So... It's not enough for builders/maintainers/developers to provide to you a free ROM on their own time and their own dime, but they should also be responsible to spend even more of their free time to dig up every issue/problem/bug and provide a specifically catered list for you, on demand, so that you can save a few minutes researching them yourself or installing the ROM to find out for yourself what may or may not work as you would like? Seems like a very reasonable and not at all selfish demand to me. Thank you for your most useful and helpful input.
Have a good one!
Click to expand...
Click to collapse
I'm glad you said what I was thinking.
AzraelsKiss said:
So... It's not enough for builders/maintainers/developers to provide to you a free ROM on their own time and their own dime, but they should also be responsible to spend even more of their free time to dig up every issue/problem/bug and provide a specifically catered list for you, on demand, so that you can save a few minutes researching them yourself or installing the ROM to find out for yourself what may or may not work as you would like? Seems like a very reasonable and not at all selfish demand to me. Thank you for your most useful and helpful input.
Have a good one!
Click to expand...
Click to collapse
Excuse me?
Its common practice to list the bugs with THEIR ROM in THEIR THREAD. Who cares if it is free? Its like providing screenshots for your ROM.
Imagine if all devs that made AOSP looking ROMs put under their screenshots; "same as CM11/12" and you had to go on a wild goose chase looking for CM screenshots? Its simply bad practice and an inconvenience. Hence why I don't flash ROMs as much as I used to because these new devs make sloppy threads compared to the Devs back in CM7/9 days.
'tis up to you. I know I wouldn't use a ROM, no matter how good it is, if it's XDA thread was sloppy. That is, after all, the most important thing when it comes to ROMs. I mean, if a builder insists on spending so much time to perfect the build that they cannot cater the thread to anyone and everyone, they shouldn't even bother.
Have a good one.
Features I didn't like...
Lot of Asian characters in settings and in some popups ..
Packaged with some search engine in Asian language.
really keen to try this LP Build.
not keen on as the previous user posted,
I cant read any other language other than english.
not to sound harsh but, i dont want to see asian characters and stuff popping up, I cant understand them.
if there is a way to rid of them or change to english. all good.
R0B3RTF1SH3R said:
really keen to try this LP Build.
not keen on as the previous user posted,
I cant read any other language other than english.
not to sound harsh but, i dont want to see asian characters and stuff popping up, I cant understand them.
if there is a way to rid of them or change to english. all good.
Click to expand...
Click to collapse
Not a asian language. this is chinese. and I agree with that because the third party app comes with chinese. third party app in AOSP rom...well...
Guys just freeze the Chinese apps or uninstall. I'm sure you guys knew that. The KK version of Mokee was nails. I'll wait for more features to start using this build, but I'm looking forward to it.
In Samsung the word Note 2 is pronounced t0lte.
King Kaze said:
Excuse me?
Its common practice to list the bugs with THEIR ROM in THEIR THREAD. Who cares if it is free? Its like providing screenshots for your ROM.
Imagine if all devs that made AOSP looking ROMs put under their screenshots; "same as CM11/12" and you had to go on a wild goose chase looking for CM screenshots? Its simply bad practice and an inconvenience. Hence why I don't flash ROMs as much as I used to because these new devs make sloppy threads compared to the Devs back in CM7/9 days.
Click to expand...
Click to collapse
Truly spoken like someone who has never built a ROM or had to support one. Well said Entitled One, well said.
It disturbs me how many devs will stay awake at night, knowing you will not flash their rom.
dicksteele said:
Truly spoken like someone who has never built a ROM or had to support one. Well said Entitled One, well said.
It disturbs me how many devs will stay awake at night, knowing you will not flash their rom.
Click to expand...
Click to collapse
Their sleep does not bother me tbh.
It's as simple as highlight>right click>copy>click>right click>paste
How does me wanting a Dev to take an extra 15 seconds when making a thread for everybody's convenience make me entitled? Who wants to trawl through thread after thread looking for a bug list?
It also has nothing to so with developing a ROM either.
King Kaze said:
Their sleep does not bother me tbh.
It's as simple as highlight>right click>copy>click>right click>paste
How does me wanting a Dev to take an extra 15 seconds when making a thread for everybody's convenience make me entitled? Who wants to trawl through thread after thread looking for a bug list?
It also has nothing to so with developing a ROM either.
Click to expand...
Click to collapse
Indeed sir ! You have convinced me.
How dare they not take an extra 15 seconds outside of the hours they have spent compiling, doing backups to test their build, flashing their build, fixing any issues, doing more backups and flashes. Coordinating with testers, gathering their input, doing more builds, backups and flashes.
How dare they not spend the extra time indeed. Unbelievably selfish, I agree.
dicksteele said:
Indeed sir ! You have convinced me.
How dare they not take an extra 15 seconds outside of the hours they have spent compiling, doing backups to test their build, flashing their build, fixing any issues, doing more backups and flashes. Coordinating with testers, gathering their input, doing more builds, backups and flashes.
How dare they not spend the extra time indeed. Unbelievably selfish, I agree.
Click to expand...
Click to collapse
actually, he has a point.
1. only if you used the other roms would know the bug/change lists. therefore. the rom is dependant.
2. some devs ive seen with postings saying "i do not own a note 2, but this should work, im not responsible for bricking your device"
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
can you tell me, what baseband your using on this, in the screenshots it says
msm86bp_1032,365.70.00R
Click to expand...
Click to collapse
R0B3RTF1SH3R said:
actually, he has a point.
1. only if you used the other roms would know the bug/change lists. therefore. the rom is dependant.
2. some devs ive seen with postings saying "i do not own a note 2, but this should work, im not responsible for bricking your device"
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
can you tell me, what baseband your using on this, in the screenshots it says
Click to expand...
Click to collapse
The screenshot does not come from a N7105, but from a MotoG
I had this ROM installed for one minute. Could not get the keyboard showing at all.... Uninstalled and moved on..... Flashed another lollipop rom
ddaazzzzaa said:
I had this ROM installed for one minute. Could not get the keyboard showing at all.... Uninstalled and moved on..... Flashed another lollipop rom
Click to expand...
Click to collapse
skip all. goto input settings, keyboad, advanced, enable hardware keyboard.
Where is N7100 one?
NisseCool said:
Where is N7100 one?
Click to expand...
Click to collapse
i think if u have a n7100 modem and kernel handy u can use any n7105 rom. dont quote me but im pretty sure.
{
"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"
}
About Us:
Dirty Unicorns is a project that started out with no name. It was a project that was first based off AOKP back in the early days of Jelly Bean. In the early days it was just a one man show on one device, the EVO 3D. Since then, many others have joined the project and it has grown exponentially.
We have seen a lot of talent contribute to this project of ours. Big or small, the focus was always on contributing to the community. That is ultimately why we do what we do. After Jelly Bean, we decided to move to a new base, OmniROM. While AOKP was fun, OmniROM proved to be even more exciting base because it challenged us to see what we could do with a project that had different goals in mind. We learned a lot and again, gain contributors. With Lollipop, we moved to an AOSP base with a lot of patches from CAF to make our older devices function as they should. We grew even more and learned a whole lot more.
It has been an awesome learning experience and is still not over! We are still learning every day and continue to move forward. Lastly, we DO NOT accept, nor ask, for donations. We don't believe in that. Everything that is necessary to keep this project going is out of our own pocket. Gerrit, Jenkins, Websites, Devices, etc. We will never ask for a dime. All we do ask, is that you have patience, search, read and try to enjoy the process with us!!
Kernel Source:
https://github.com/CyanogenMod/android_kernel_lge_g3
Flashing Instructions:
- Verify that you're using the latest version of TWRP
- Perform a FULL WIPE as described below if coming from another ROM or a different version of Android
(A full wipe is when you wipe system/data/cache)
- Flash the latest version of this ROM
- Flash recommended GAPPS linked below
- Reboot and ENJOY!!
**If you fail to follow these instructions, please don't bother reporting any bugs**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
Change Log:
Code:
[B]Version 10.5 [/B]
[I][U]07 Aug 2016[/U][/I]
- Synced with DU source
- Version bumped to 10.5
- For a detailed change log, check [URL="http://gerrit.dirtyunicorns.com/#/q/status:merged,n,z"]DU gerrit[/URL]
[B]Version 10.4 [/B]
[I][U]14 July 2016[/U][/I]
- First build
- For a detailed change log, check [URL="http://gerrit.dirtyunicorns.com/#/q/status:merged,n,z"]DU gerrit[/URL]
Credit and Thanks:
We would like to give thanks to everyone that contributes to the Android community, big or small because every bit counts. Although we can't list each and every contributor within the Android community, we would like to highlight some of the teams and individuals that have made it possible NOT only with just this version of DU but throughout the years because we don't ever want to forget where we came from nor those that have helped us!
Special thanks to:
@ishanbhatnagr96 for testing the ROM :good:
That said, on behalf of the DU team we say THANKS to....
JMZ Software
Baby Jesus
Code Aurora Forum
Omni ROM
Android Open Kang Project (AOKP)
Android Ice Cold Project (AICP)
XDA-Developers
SlimROMs
Preludedrew
Max Weninger
Team Black Out
CyanogenMod
Pure Nexus Project
**If we have left someone or some team out, we apologize and please PM us**
Download Links:
Version 10.5 - https://www.androidfilehost.com/?fid=24591000424952756
GAPPS - http://download.dirtyunicorns.com/files/gapps/
Frequently asked questions:
The download link is slow, can you provide a mirror?
From time to time, we perform maintenance on our website but we do not authorize any mirrors. Please have patience!
I'm on a TEST BUILD and have this bug, can you help?
Please keep any discussion about test builds in the G+ community!
How can I get Viper4Android working?
Check this thread out https://plus.google.com/+JasonPasch5/posts/6JDRjdL2mKM
Are you coming from a ROM with Layers?
Make sure you remove your 'overlay' folders and perform a FULL WIPE
My battery stats are all messed and reporting the wrong percentage, what can I do?
Stop using another kernel. Do a FULL WIPE and flash the ROM again
Is this ROM CM based or AOSP based?
This ROM is based off AOSP
Does this ROM have layers or the CMTE?
This ROM uses the CM theme engine
Pulse doesn't work with [insert music app]
Check this thread out https://plus.google.com/101146731143183859725/posts/TcSzc61xuVx
I'm getting a FC from the theme chooser, what gives?
This is due to restoring data/apps from Google. Go ahead and clear data and cache for theme chooser and theme provider then reboot you should be good moving forward.
I changed my LCD density and now the navbar looks weird, what gives?
This is currenly an issue that we are aware of and addressing. For now after you changed density reset navbar layout or stay on the stock density.
Other Links:
G+ community - https://plus.google.com/u/0/communities/109738128866939227235
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
Jira (Bug Report / Feature Request) - http://jira.dirtyunicorns.com/
XDA:DevDB Information
[ROM][6.0.1][Unofficial] Dirty Unicorns for LG G3 [F400], ROM for the LG G3
Contributors
nitin.chobhe
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Testing
Created 2016-07-15
Last Updated 2016-08-09
Thanks @ishanbhatnagr96 for the Screenshots
One more if needed
Good stuff man! Loving the smoothness of DU ?
Sent from my LG-F400 using Tapatalk
@nitin.chobhe, can you tell me if laser AF is working?
Thanks, I hate any stock firmware and I may consider to switch.
Then... regarding modem, the 21C needing still exists?
Simone98RC said:
@nitin.chobhe, can you tell me if laser AF is working?
Thanks, I hate any stock firmware and I may consider to switch.
Then... regarding modem, the 21C needing still exists?
Click to expand...
Click to collapse
Laser autofocus does work fine. And this is a F400 thread. Please ask that question in the appropriate thread
Sent from my LG-F400 using Tapatalk
ishanbhatnagr96 said:
Laser autofocus does work fine. And this is a F400 thread. Please ask that question in the appropriate thread
Sent from my LG-F400 using Tapatalk
Click to expand...
Click to collapse
Ah ok... sorry and thanks for the reply
Switching from Fulmics 5.3
I have been a fan of AOSP and CM-based ROM since I started fiddling Android devices. But for the first time, I used stock rom in LG G3 due to the fact that the camera performs better (according to my readings) than AOSP-based rom, mainly shooting 4K videos, time-lapse and slow-mo. But I hate the fact that the battery drains fast, overheating issues, and it lags a lot, as in a lot. I have to restart a couple of times to get my phone to work on some time.
I used Dirty Unicorn on my previous Android device (HTC One M7), and I was happy with its performance. So I'm considering this ROM, but I use my phone as a daily driver, so reinstalling apps is a bit hassle, especially coming from stock ROM. And I use camera a lot, so is there any alternative to this?
Thank you for those who will answer
ronmarccharlesms said:
I have been a fan of AOSP and CM-based ROM since I started fiddling Android devices. But for the first time, I used stock rom in LG G3 due to the fact that the camera performs better (according to my readings) than AOSP-based rom, mainly shooting 4K videos, time-lapse and slow-mo. But I hate the fact that the battery drains fast, overheating issues, and it lags a lot, as in a lot. I have to restart a couple of times to get my phone to work on some time.
I used Dirty Unicorn on my previous Android device (HTC One M7), and I was happy with its performance. So I'm considering this ROM, but I use my phone as a daily driver, so reinstalling apps is a bit hassle, especially coming from stock ROM. And I use camera a lot, so is there any alternative to this?
Thank you for those who will answer
Click to expand...
Click to collapse
Are you rooted? If yes, then you can get the Titanium Backup and backup all the apps that you want, flash DU and restore the apps :good:
@ishanbhatnagr96 can you help him about camera?
Nitin
ronmarccharlesms said:
I have been a fan of AOSP and CM-based ROM since I started fiddling Android devices. But for the first time, I used stock rom in LG G3 due to the fact that the camera performs better (according to my readings) than AOSP-based rom, mainly shooting 4K videos, time-lapse and slow-mo. But I hate the fact that the battery drains fast, overheating issues, and it lags a lot, as in a lot. I have to restart a couple of times to get my phone to work on some time.
I used Dirty Unicorn on my previous Android device (HTC One M7), and I was happy with its performance. So I'm considering this ROM, but I use my phone as a daily driver, so reinstalling apps is a bit hassle, especially coming from stock ROM. And I use camera a lot, so is there any alternative to this?
Thank you for those who will answer
Click to expand...
Click to collapse
Well the camera which comes with this ROM is snapdragon camera which is by far the best I've used on any AOSP/CM rom. I'd also suggest Google camera.
Sent from my LG-F400 using Tapatalk
ishanbhatnagr96 said:
Well the camera which comes with this ROM is snapdragon camera which is by far the best I've used on any AOSP/CM rom. I'd also suggest Google camera.
Sent from my LG-F400 using Tapatalk
Click to expand...
Click to collapse
does it support 4k shooting? what is the average screen on time, if you mind? mine last only for about 2 hrs, with just browsing and music (with v4a).
ronmarccharlesms said:
does it support 4k shooting? what is the average screen on time, if you mind? mine last only for about 2 hrs, with just browsing and music (with v4a).
Click to expand...
Click to collapse
Yes 4K is there. As for battery, I average off anywhere between 3.5 to 4.5 hours.
TBH you just have to try it for yourself. If it suits your preference then good, otherwise look for something else. Usage and battery life depends on user to user. This is the only CM based rom which gives me good battery life along with temasek. So you should try everything as it'll give you a better insight
Sent from my LG-F400 using Tapatalk
nitin.chobhe said:
Are you rooted? If yes, then you can get the Titanium Backup and backup all the apps that you want, flash DU and restore the apps :good:
@ishanbhatnagr96 can you help him about camera?
Nitin
Click to expand...
Click to collapse
yes i am rooted . uhmm, wouldn't that leave any traces of "stock" setting? I've read somewhere that one of the reason wiping cache is important is to remove all traces of previous rom, including the apps affected by it..or is it wrong?
and how about the SOT? does it last for 3h or more?and what kernel os recommended with this ROM?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
ishanbhatnagr96 said:
Yes 4K is there. As for battery, I average off anywhere between 3.5 to 4.5 hours.
Sent from my LG-F400 using Tapatalk
Click to expand...
Click to collapse
ooh. that is sweet thank you for that info. any kernel recommendation?
PS, I know that i shouldn't ask, as per stated on the post regarding DU, but is greenifying with xposed ok? have you tried it?
ronmarccharlesms said:
yes i am rooted . uhmm, wouldn't that leave any traces of "stock" setting? I've read somewhere that one of the reason wiping cache is important is to remove all traces of previous rom, including the apps affected by it..or is it wrong?
and how about the SOT? does it last for 3h or more?and what kernel os recommended with this ROM?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
ooh. that is sweet thank you for that info. any kernel recommendation?
PS, I know that i shouldn't ask, as per stated on the post regarding DU, but is greenifying with xposed ok? have you tried it?
Click to expand...
Click to collapse
I don't use xposed on CM/AOSP roms. Causes system to misbehave sometimes. But feel free to use it. And no, I don't use greenify. As per kernel, leave it to default and see how it performs
Sent from my LG-F400 using Tapatalk
ishanbhatnagr96 said:
Yes 4K is there. As for battery, I average off anywhere between 3.5 to 4.5 hours.
TBH you just have to try it for yourself. If it suits your preference then good, otherwise look for something else. Usage and battery life depends on user to user. This is the only CM based rom which gives me good battery life along with temasek. So you should try everything as it'll give you a better insight
Sent from my LG-F400 using Tapatalk
Click to expand...
Click to collapse
yes thank you, but i am well aware of it eitherway, i think ill try it.
ishanbhatnagr96 said:
Yes 4K is there. As for battery, I average off anywhere between 3.5 to 4.5 hours.
TBH you just have to try it for yourself. If it suits your preference then good, otherwise look for something else. Usage and battery life depends on user to user. This is the only CM based rom which gives me good battery life along with temasek. So you should try everything as it'll give you a better insight
Click to expand...
Click to collapse
This is not cm based, it's based on aosp
Thanks for the answers man
Nitin
The best...
Glad to see new rom for f400.. So far so good thanks for this rom. Its rare to see new rom for korean variant. Keep up the good work dude!!!!
Thanks for the rom...
New build is up: https://www.androidfilehost.com/?fid=24591000424952756
Changelog:
- Synced with DU source
- For a detailed change log, check DU gerrit
Nitin
First of all I would like to thank the OP for his efforts.
Can you please continue porting DU to our f400 variants?. I can help you with testing if you need it
{
"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"
}
PixelExperience for Note 4
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
SE Linux Permissive
DON'T FLASH GAPPS, ALREADY INCLUDED
Download here
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Telegram channel
Stay tuned
Android OS version: 9.0.0_r35
Security patch level: April 2019
Build author: Inkypen
Source code: https://github.com/PixelExperience
Device tree and kernel: https://github.com/triplr-dev
ROM Developer: jhenrique09
XDA:DevDB Information
Pixel Experience, ROM for the Samsung Galaxy Note 4
Contributors
Inkypen, tripLr, ripee
ROM OS Version: 9.x Pie
Version Information
Status: Testing
Created 2019-04-29
Last Updated 2019-04-29
File host changed to AFH, download link updated. Should be no more download errors
https://www.androidfilehost.com/?w=files&flid=293509
You have 2 threads for each of your ROM's
This is confusing......
Please chose one and get the mods to remove the duplicates, for everyones sanity, not just mine
73sydney said:
You have 2 threads for each of your ROM's
This is confusing......
Please chose one and get the mods to remove the duplicates, for everyones sanity, not just mine
Click to expand...
Click to collapse
For some reason XDA double posted my build threads. This thread is the one I get updates for, not the other one. Will ask a mod to close the duplicates.
I saw your comments on the other thread, I cannot fathom why you would download a ROM called "Pixel Experience" and then complain about GApps being included! It's quite literally baked into the ROM as you can't experience the Pixel phone which is made by Google, without the Google apps......
Whether it's intentional or not, reading some of you recent posts you come across as a sterotypical "entitled" user. Nobody forced you to download any builds of any ROM, this is a development forum and as such bugs are to expected. Rather than complain about bugs and missing features, send logcats and commits for the features you want to see. Perhaps you should read the standard disclaimer in the first post of every ROM you will ever download, including RR:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Click to expand...
Click to collapse
Inkypen said:
For some reason XDA double posted my build threads. This thread is the one I get updates for, not the other one. Will ask a mod to close the duplicates.
I saw your comments on the other thread, I cannot fathom why you would download a ROM called "Pixel Experience" and then complain about GApps being included! It's quite literally baked into the ROM as you can't experience the Pixel phone which is made by Google, without the Google apps......
Whether it's intentional or not, reading some of you recent posts you come across as a sterotypical "entitled" user. Nobody forced you to download any builds of any ROM, this is a development forum and as such bugs are to expected. Rather than complain about bugs and missing features, send logcats and commits for the features you want to see. Perhaps you should read the standard disclaimer in the first post of every ROM you will ever download, including RR:
Click to expand...
Click to collapse
I suggest you read my comments again as you are totally misrepresenting what i said., i said in short that some critical G-Apps (like Gmail) were missing, yet some others which are eye candy ar eincluded. I suggested you either fix this or leave G-Apps to the user.
Please dont misrepresent me and then talk down to me, and insult me, it will not go well for you.....if you cant take constructive criticism, perhaps ROM development is not for you. These bugs and oversights should have been evident if you tested your ROM before you simply uploaded them....
For clarity, heres my exact comments from the duplicate thread, please note that thread also included bug reports which i didnt repeat as they had already been expressed:
Tested this ROM, and heres my thoughts/criticisms:
* Inclusion of some G-Apps, while others which are more critical (Gmail most notably) are missing....for the huge download this oversight is really hard to fathom. 748Mb and no Gmail included? Also missing Android Webview.....kind of important
Instead all the stuff i normally weed out by never selecting it in Aroma G-Apps or usign the debloat magisk module if its built into a ROM is included...Device Health/Digital Wellbeing, and the google search app among them...if i wanted active spyware, id install it....instant downvote
For such a massive download, i cant see anything that would make me bother downloading further builds.
I do appreciate the dev building the ROM but, please consider leaving G-Apps up to the user, and thereby reduce the massive download size....
Update: curiously, some of my magisk modules which work on literally every other ROM ive ever used, fail on this one.....bizarre
About to test the dev's other ROM.....
Update: decided not to, apparently it has some of the same issues. Hope the dev can fix them and test before releasing next time....both ROMS cost me nearly 1.2Gb and both buggy....please test thoroughly before uploading.....
Back to RR for me again....
The best i had test at the moment, Stable, smooth, a Little bit of battery friendly, no overheating, no glitches, the only bug quiet anoying for me it's that I'm unable to activate the phone pressing the home botton, but the rest it's working nice as butter, sometimes the camera freeze taking a picture, thas a Little bit uncomfortable. nice job to all devs working on this rom.
73sydney said:
I suggest you read my comments again as you are totally misrepresenting what i said., i said in short that some critical G-Apps (like Gmail) were missing, yet some others which are eye candy ar eincluded. I suggested you either fix this or leave G-Apps to the user.
Please dont misrepresent me and then talk down to me, and insult me, it will not go well for you.....if you cant take constructive criticism, perhaps ROM development is not for you. These bugs and oversights should have been evident if you tested your ROM before you simply uploaded them....
Click to expand...
Click to collapse
I would also respectfully request you read my comments again. At no point did I insult you, merely highlighted the purpose of XDA forums and reiterate the nature of experimental open source software. Your response reinforces the impression of a stereotypical entitled user, you provided no "constructive" criticism at all, and resorted to threats. I pointed out how your posts could be seen as entitled and demanding and offered an alternative way of expressing your issues. That right there is constructive criticism, whereas moaning about wasted bandwidth is not. If you're not prepared to deal with buggy software and need a production grade OS, perhaps ROM testing is not for you?
To address your specific issues with Pixel Experience:
It boots, phone calls, text messages, mobile data, WiFi, sound, vibrator, touch screen all works. ROM is usable, for a given definition of 'usable' which may or may not match your expectations.
You need to understand the difference between functionality and implementation. Any decisions about GApps and which apps are or are not included is down to Henrique Silva who is the lead developer of PE. There is a good reason why certain apps are not included and that's because some phones don't have a large enough system partition to store all the GApps, so 'core' apps are installed instead. Android WebView isn't even needed if you have Chrome installed, as chromium is installed as WebView provider. Henrique is ensuring functionality on as many phones as possible. My part in this is implementation of said functionality. If WiFi doesn't function as expected or you can't make a phone call then that's up to me to fix. That's where testers come in, a lone developer fuelled by coffee and donuts couldn't possibly envisage and test for every possible use case.
I have no intention of engaging in a tit-for-tat back and forth argument with an anonymous stranger I met on the Internet. If you have something constructive to say about anything related to my implementation of these ROMS, then I'm all ears. Got any suggestions for additional features? Sure, I'll listen and perhaps maybe incorporate it if its within my means, otherwise it needs to go to the lead ROM developer. Want to engage in argument about who said what when? No thanks, got enough stress in my life as it is.
Sincerely, have a nice day. Life is too short to get into random arguments with strangers :good:
Inkypen said:
I would also respectfully request you read my comments again. At no point did I insult you, merely highlighted the purpose of XDA forums and reiterate the nature of experimental open source software. Your response reinforces the impression of a stereotypical entitled user, you provided no "constructive" criticism at all, and resorted to threats. I pointed out how your posts could be seen as entitled and demanding and offered an alternative way of expressing your issues. That right there is constructive criticism, whereas moaning about wasted bandwidth is not. If you're not prepared to deal with buggy software and need a production grade OS, perhaps ROM testing is not for you?
To address your specific issues with Pixel Experience:
It boots, phone calls, text messages, mobile data, WiFi, sound, vibrator, touch screen all works. ROM is usable, for a given definition of 'usable' which may or may not match your expectations.
You need to understand the difference between functionality and implementation. Any decisions about GApps and which apps are or are not included is down to Henrique Silva who is the lead developer of PE. There is a good reason why certain apps are not included and that's because some phones don't have a large enough system partition to store all the GApps, so 'core' apps are installed instead. Android WebView isn't even needed if you have Chrome installed, as chromium is installed as WebView provider. Henrique is ensuring functionality on as many phones as possible. My part in this is implementation of said functionality. If WiFi doesn't function as expected or you can't make a phone call then that's up to me to fix. That's where testers come in, a lone developer fuelled by coffee and donuts couldn't possibly envisage and test for every possible use case.
I have no intention of engaging in a tit-for-tat back and forth argument with an anonymous stranger I met on the Internet. If you have something constructive to say about anything related to my implementation of these ROMS, then I'm all ears. Got any suggestions for additional features? Sure, I'll listen and perhaps maybe incorporate it if its within my means, otherwise it needs to go to the lead ROM developer. Want to engage in argument about who said what when? No thanks, got enough stress in my life as it is.
Sincerely, have a nice day. Life is too short to get into random arguments with strangers :good:
Click to expand...
Click to collapse
And again you insult me, among other things calling me "entitled"
You dont get to talk down to me...sorry, thats not happening, maybe when you release something without major issues you might get that privilege, but not before....
Last time, you will insult me and last time i want to hear your crap
Mate, ive flashed, contributed to, and tested more ROMs than youve had hot breakfasts
I wont be testing any more of yours given your attitude..
Especially when you totally discount the fact me asking you to actually test your releases before releasing them as in some countries like mine, bandwidth and data (especially for 700Mb+ ROMS) costs actual money. Your attitude on this, dismissing my data allowance out of hand (moaning about wasted bandwidth )is really quite insulting and rude. Its a valid criticism when its clear you havent properly tested your releases.
Good luck with your work, i wont be testing or recommending anything you release....
And quite frankly if i never come across you again, it will be too soon.....
Get over yourself, you rude self important newbie.
Congrats on being the 1st person ever on my ignore list, fool.
If anyone is interested, new builds with May security patch have been uploaded. Home to wake feature has been enabled. Also added tblte and trlteduos builds. https://www.androidfilehost.com/?w=files&flid=293509
Inkypen said:
If anyone is interested, new builds with May security patch have been uploaded. Home to wake feature has been enabled. Also added tblte and trlteduos builds. https://www.androidfilehost.com/?w=files&flid=293509
Click to expand...
Click to collapse
Can you add "Home to wake" feature to the AEX ROM too?
Thx
Raven_999 said:
Can you add "Home to wake" feature to the AEX ROM too?
Thx
Click to expand...
Click to collapse
That's done, and in AEX there's the even the option to toggle it on/off. Builds are running, will upload shortly.
Inkypen said:
If anyone is interested, new builds with May security patch have been uploaded. Home to wake feature has been enabled. Also added tblte and trlteduos builds. https://www.androidfilehost.com/?w=files&flid=293509
Click to expand...
Click to collapse
Can I dirty flash this over the earlier version?
this is probably obvious but i cant find the settings for disabling hardware key lights and is there an on screen nav bar option?
note edge 915f is working hard only problem is the battery is not fully charged 92% 93 (lineage 16 also did not have this problem)
in this rom, camera works. (unlike other pie roms)
edge n915-t
sm-n910u
not working on sm-n910u (trhplte) :crying::crying::crying::crying:
Does the second sim working?
sm-n9100 trlteduos
mjhassanli said:
not working on sm-n910u (trhplte) :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably because your phone uses an exynos chipset and this forum is for snapdragon variants. Try this forum instead: https://forum.xda-developers.com/note-4/development
Just installed this ROM few minutes ago, so far it's smooth and I really like the transition and system animation than LOS one. But I have some questions: does the kernel support F2FS because it seems to bootloop when installed on F2FS? And what how can I root this ROM? Magisk, SuperSU or AddOnSU from LOS?
Jack123hello said:
Just installed this ROM few minutes ago, so far it's smooth and I really like the transition and system animation than LOS one. But I have some questions: does the kernel support F2FS because it seems to bootloop when installed on F2FS? And what how can I root this ROM? Magisk, SuperSU or AddOnSU from LOS?
Click to expand...
Click to collapse
Flash Magisk zip in twrp and then reboot your phone , this is how to root any rom