{
"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.
*/
Because of the nature of Xposed framework, NO SUPPORT will be given to those running Xposed framework on Omni 6
CHANGELOG:
Code:
[CENTER]
2016-02-01:
Nightlies started :)
2016-01-22:
-Omni Dialer lookup is back
-Lots of changes/fixes
-Kernel leak fixes
2016-01-06:
First build of the year :)
-Omni JAWS (Just Another Weather System)
-Update to Android 6.0.1 r10 ( Include latest security updates)
2015-12-30:
Last build of the year :)
-Chromium is included in this build, and unless poll results change within the next 2 days, it will remain
-lots of bugfix
2015-12-19:
-New boot annimation
-selinux enforced (use system-less supersu beta to get root)
-some bugfix (check gerrit for the changelog)
2015-12-11:
Android 6.0.1 update
A few backported features and bugfix
2015-12-04:
Silent mode back
some bugfix
2015-11-29:
revert clang usage that was breaking sensors (as seen on CyanogenMOD's github)
Latest commits were actually cherry-picked from mako's device tree on CM-13 github.
2015-11-28:
some QCOM camera fix
some deprecated stuff removal
wifi check added (taken from Nvidia shield)
2015-11-19:
add dex2oat speed filter (speed up initial boot and attempt to fix facebook app cache regeneration at reboot)
2015-11-15:
Update to Android 6 r26
In-call audio fixed, force dex2oat uses no-swap, codecs handling
2015-11-9:
DRM blobs updated (Google play movies works, Netflix should work as well, but I can't test it), some more blobs added ( from Nexus 7 2013 )
2015-11-8 (new build):
Doze power saving mode, drm handling should be fixed, media codec updated
2015-11-8:
Use accelerometer for doze, and custom battery lights
2015-11-7:
First update, bugfix and backports
2015-11-5:
Initial Release[/CENTER]
DOWNLOADS:
Omni 6 Nightlies for Nexus 4 / Mako
You MUST DO A FULL WIPE before flashing nightlies, 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. If you were to flash nightlies over my own builds or your custom made builds, or any other ROM, you would end in a bootloop
GAPPS must be flashed BEFORE initial boot, they will NOT work properly if you flash them afterwards !!!
Don't update gapps on nightlies update, only initial flash requires it. Updating gapps on next nightly would break those, and ROM would become unusable.
You MUST use this version of supersu, latest beta system less
Supersu beta System less
KNOWN BUGS:
Code:
[CENTER]* You tell me[/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 6, ROM for the Google Nexus 4
Contributors
kldoc, MaR-V-iN, Maxwen, Entropy512, Xplodwild, Jiangyi
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Nightly
Created 2015-11-05
Last Updated 2016-04-25
Reserved
Thanks, I will give it a try
A list with the features would be very appreciated.
dragos281993 said:
A list with the features would be very appreciated.
Click to expand...
Click to collapse
Hi! Wow, Marshmallow includes a ton of features, do you want me to make you a list of them? I don´t think so.
Whatever, features in 6.0 are practically the same than the Omni 5.1.1 ones, just some of them are disabled temporaly.
Wanna know what are the features in 5.1.1? Flash the OmniRom nightly for 5.1.1, or, if you want to make the process faster, directly flash this 6.0 build.
Enjoy!
kldoc said:
Hi! Wow, Marshmallow includes a ton of features, do you want me to make you a list of them? I don´t think so.
Whatever, features in 6.0 are practically the same than the Omni 5.1.1 ones, just some of them are disabled temporaly.
Wanna know what are the features in 5.1.1? Flash the OmniRom nightly for 5.1.1, or, if you want to make the process faster, directly flash this 6.0 build.
Enjoy!
Click to expand...
Click to collapse
I simply asked. All the other ROMs have a list with the basic features in the description, so it was a matter of time before someone came here and asked you for one. Also, flashing a ROM in order to find out what features it has, it's counterproductive. I've got free time when I come home from work, and the last thing I want to do is experiment with ROMs that I have no idea what features include and what don't. I usually read the description of a new ROM, see if it has what I'm interested in, and then decide if I feel like flashing it or not.
Sent from my Nexus 4 using Tapatalk
kldoc said:
Hi! Wow, Marshmallow includes a ton of features, do you want me to make you a list of them? I don´t think so.
Whatever, features in 6.0 are practically the same than the Omni 5.1.1 ones, just some of them are disabled temporaly.
Wanna know what are the features in 5.1.1? Flash the OmniRom nightly for 5.1.1, or, if you want to make the process faster, directly flash this 6.0 build.
Enjoy!
Click to expand...
Click to collapse
Wow, dude, it's just a question
Fatal1ty_93_RUS said:
Wow, dude, it's just a question
Click to expand...
Click to collapse
Actually I said him to write that, just is some kind of advice for all the users.
Backing up current ROM, and testing this ROM is something that could take you just 5 minutes.
Sometimes is really tiring to get messages from hundred of users asking about features, when they can be seen on our OmniRom github or by testing it. We don't provide a feature list as almost all ROMs do, we see that unnecesary, but we asure that the experience with our ROM is going to be great.
Actually the features included for Omni are the next ones:
We are not and probably we never were a feature bloated ROM, as other ROMs do as DU or CM does. Our ROM is just a clean AOSP one with minimal but nice features and with an optimized performance.
We, and also me, will be adding some features to it recently, I just finished yesterday on solving issues for my device, now is time for features.
Anyway sorry if reply was some kind of "unrespecful" but this way I wanted to prevent 50 posts asking for the same think.
I wish you to enjoy the ROM and tell us your feedback
Cheers!
Sent from my A0001 using Tapatalk
kernel source?
brandonabandon said:
kernel source?
Click to expand...
Click to collapse
As mentioned in the main thread, everything is on OmniROM's github or OmniROM's gerrit (in case it's not merged yet).
I try myself to publish non-official builds with available source for everything.
There is one (very tiny) difference between device_lge_mako used in this build and the one present in the non merged commit though, i've added "selinux=permissive" to make your life easier with root process while supersu is still not possible with selinux enabled, but this will never get merged, OmniROM intend to provide a secure ROM.
Here is again the link to OmniROM's github (copy of main thread link with url to kernel repo):
https://github.com/omnirom/android_kernel_lge_mako/tree/android-6.0
Have fun !
EDIT: In case the question rise, kernel is based on the work of Dmitry Ginsberg, except that I did track all the commits in his patch and cherry-picked all of them from google's git, only defconfig was taken from his patch. I removed the cpufreq_stats which is supposedly not implemented in Qualcomm S4 pro, even though some devs are trying to make an implementation, I won't probably include any of this in OmniROM's kernel, this for a few reasons, the first one being that I don't have the C/CPP knowledge to fully understand kernel's changes that "might" break things, second one being that I truly wish Nexus 4 kernel to stay as close as possible to AOSP, which is OmniROM's policy anyway
If one would want to submit patches to support some new features in the kernel, they are more than welcome to do so, patches will be reviewed by people with required experience and knowledge
Not going to try this because of rude dev's....
bdasmith said:
Not going to try this because of rude dev's....
Click to expand...
Click to collapse
Thanks op for the thurough explanation. Im looking to optimize and hack a personal build and was experiencing boot issues.
bdasmith said:
Not going to try this because of rude dev's....
Click to expand...
Click to collapse
As mentioned by @herna, he actually told me to write this answer. I am myself not rude by any mean, and try to give my users as much support as I can. I do work on OmniROM as a hobby, as I'm not even an IT professionally speaking. Currently chain testing gapps packages to be able to recommand one that works perfectly on Omni 6 for Nexus 4.
I am truly sorry if the tone of the message actually did offend people, doing so was not my intention. I published this homemade build to show people progress was being done on OmniROM 6 and let people play a bit with it, but since I knew it was a very early build not meant to be used as a daily driver, that's why I did tag the thread with experimental status, to avoid people with very few free time to actually try to use this ROM as a daily driver, or even features, as many things are yet to be fixed, and that's the reason why @herna actually told me to write this, to avoid the need to give support for bugs that are being solved and need time to be fixed. Because we are all doing this in our free time, none of us is getting paid to do this, we do that by passion for Android and its community.
I once again perfectly understand the message was rude, and I'm sorry if this offended people, I, in future, will avoid to answer with such a tone, and give more complete explanations why some questions can't get straight answers.
In the meantime, I really advise people who don't have much free time to spend on ROM flashing to stay away from this build for now, as it's really intended for people with knowledge and free time to get it running well. Rest assured I'll publish new builds as bugs are being solved in order to improve your experience
Have fun with OmniROM !
kldoc said:
As mentioned by @herna, he actually told me to write this answer. I am myself not rude by any mean, and try to give my users as much support as I can. I do work on OmniROM as a hobby, as I'm not even an IT professionally speaking. Currently chain testing gapps packages to be able to recommand one that works perfectly on Omni 6 for Nexus 4.
I am truly sorry if the tone of the message actually did offend people, doing so was not my intention. I published this homemade build to show people progress was being done on OmniROM 6 and let people play a bit with it, but since I knew it was a very early build not meant to be used as a daily driver, that's why I did tag the thread with experimental status, to avoid people with very few free time to actually try to use this ROM as a daily driver, or even features, as many things are yet to be fixed, and that's the reason why @herna actually told me to write this, to avoid the need to give support for bugs that are being solved and need time to be fixed. Because we are all doing this in our free time, none of us is getting paid to do this, we do that by passion for Android and its community.
I once again perfectly understand the message was rude, and I'm sorry if this offended people, I, in future, will avoid to answer with such a tone, and give more complete explanations why some questions can't get straight answers.
In the meantime, I really advise people who don't have much free time to spend on ROM flashing to stay away from this build for now, as it's really intended for people with knowledge and free time to get it running well. Rest assured I'll publish new builds as bugs are being solved in order to improve your experience
Have fun with OmniROM !
Click to expand...
Click to collapse
Thank you for your kind explanation. I'm willing to experiment now
brandonabandon said:
Thanks op for the thurough explanation. Im looking to optimize and hack a personal build and was experiencing boot issues.
Click to expand...
Click to collapse
You actually need this unmerged commit to be able to boot:
https://gerrit.omnirom.org/#/c/15224/
I didn't merge it yet to allow modifications and keep things clean in the meanwhile, stlport is actually needed, that's the main modification to allow boot if you set selinux to permissive, if you want selinux enforced (no root at the moment), you'll also need the selinux policy changes.
This commit doesn't include permissive selinux, because it's not needed for boot, but if you need it, and don't know how to set it, let me know, i'll give you where and how to set it up.
Hope that solve your boot issue If you still have troubles booting despite that commit, please provide some logs so I can see what's wrong
Have fun
for those who might have issues with Google Keep force closing, I discovered that last version from play store actually doesn't work, you need to install an older one:
http://www.apkmirror.com/apk/google-inc/keep/keep-3-2-435-0-android-apk-download/
I've just uploaded 2 screenshots, don't be alarmed by the "!" next to my wifi icon, I'm in China, google services are blocked, that's also the reason why there's a key, vpn ...
Google keep, Gmail and maps didn't work as expected. As you mentioned Keep kept force closing. Maps and Gmail refused to accept sign in. I downloaded the apks from apkmirror. They work fine now.
The rom is awesome as usual. Thanks kldoc. One feature missing or is a new marshmallow feature is that the phone doesn't unlock after entering just the pin. You have to tap enter.
hashtask said:
Google keep, Gmail and maps didn't work as expected. As you mentioned Keep kept force closing. Maps and Gmail refused to accept sign in. I downloaded the apks from apkmirror. They work fine now.
The rom is awesome as usual. Thanks kldoc. One feature missing or is a new marshmallow feature is that the phone doesn't unlock after entering just the pin. You have to tap enter.
Click to expand...
Click to collapse
Thank you for your feedback ! Really happy to see it went rather well for you
Pin code auto-unlock was an option in Lollipop, have to admit I don't like this security wise. Just checked, and yes, Google removed the option.
I had less issue than you with Gapps, I used banks gapps, that I modified to include Google Now launcher, apart from keep, everything ran well from play store, but I use inbox, not gmail, might be the difference here.
Actually making a new build as I write this mail to verify the update process, will post it here once I'm done verifying that nothing is broken.
I managed to trick location, even if it was much more difficult to accomplish than on Lollipop, allowed me to be located in US and enable google now. Google now on tap also works from what i can see.
kldoc said:
I've just uploaded 2 screenshots, don't be alarmed by the "!" next to my wifi icon, I'm in China, google services are blocked, that's also the reason why there's a key, vpn ...
Click to expand...
Click to collapse
Where are the screenshots?
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"
}
What is OmniROM?
OmniROM Gerrit Review
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Important Information
Root access has not been incorporated into the ROM source yet, so you will need to flash SuperSU in recovery SuperSU
For all you Do-It-Yourself-ers, simply follow this guide to initialize a build environment and get your own builds started - OmniROM - Setting Up A Compile Environment
Got a bug report? Want to request a feature?
jira.omnirom.org
Click to expand...
Click to collapse
Installation Instructions
FROM ANOTHER ROMS
Factory Reset/Wipe Data
Format System
Format Dalvik Cache
Install ROM
Install Gapps
Reboot
Profit
UPDATE FROM OMNIROM TO NEWER RELEASE
Settings -> System Updates -> Check for update
You will NOT need to wipe anything with the delta updates :good:
Click to expand...
Click to collapse
Downloads
ROM:
jflte
http://dl.omnirom.org/jflte/
Gapps:
PA 0-Day Gapps
Click to expand...
Click to collapse
Contributors/Credit
The OmniROM Team - Great devs that have taught me just about everything I know about this stuff in such a short amount of time
CyanogenMod
ParanoidAndroid for the GApps package
@jumoog for working with me on the jf family of devices (MOAR Galaxay S4's to be supported soon!)
@SferaDev for ALL the work on adding Samsung RIL support
@CNexus for his awesome boot.img tools and helping me out
@Evisceration for his insane kernel pwnage
Testers
@CPA Poke
@LamboDroid19
@RockMan195
@crzygrmn
@uberstupd
@Pump Ac7i0n
And anyone else I apologize I forgot on this list but thank you
Source
OmniROM Source
XDA:DevDB Information
OmniROM, a ROM for the Verizon Samsung Galaxy S 4
Contributors
jakew02
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Rooted, Custom Recovery
Based On: AOSP
Version Information
Status: Alpha
Current Stable Version: -
Current Beta Version: -
Created 2013-12-05
Last Updated 2014-05-02
Changelog
Changelog
OmniLog - jfltevzw
Q&A
Frequently Asked Questions
Q: Why don't I have root access after installing OmniROM?
A: OmniROM does not have an official, prebuilt root method yet, so you'll just need to flash SuperSU in recovery and you'll have 100% working root access. SuperSU can be found here: SuperSU
Q: Where is <insert feature here>, like CM/AOKP/PA/etc have??
A: Omni is still very early in development, but moving at an incredibly fast rate. New feature, bug fixes, and device support are added just about daily. Check it out here: OmniROM Gerrit Review for the latest and greatest
Q: How do I start/stop screen recording?
A: Volume UP + Power will start screen recording. Simply drag the notification bar down and click the button to stop.
Q: HALP NFC doesn't work!!
A: We know.
Thanks!! Nanding now..
gleggie said:
Thanks!! Nanding now..
Click to expand...
Click to collapse
im pushing another update to fix RUIM quickly
Works perfectly.
builds up now sorry sorry :angel:
I've had Omni on my flo for a while now and love it, I got excited when I started seeing jf come up in gerrit and was wondering when this day would come. Thank you for working towards supporting this device!
edit
Just did a fresh install of this ROM. Couple issues I've already come across..
My screen after a restart won't go to sleep after the specified time or by pushing the power/sleep button.
Not sure if this is related, but I have enabled active display and got an FC error upon my first notification and had to battery pull.
Update: After turning off Active display I can now put my phone to sleep without issue.
So... I've read the 'this is what custom roms should be' press release three times now, and I still have no idea what differentiates Omni from other ROMs. Is it a custom interpretation of AOSP code, like Cyanogenmod, or features ladled over Cyanogen code, like most other ROMs? Does it offer any of the fiddly knobs of Paranoid Android, or is this going to be a feature-avalance like AOKP or PAC?
I know things are still early days for Omni, but what am I looking forward to when I flash your ROM?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Trygon said:
So... I've read the 'this is what custom roms should be' press release three times now, and I still have no idea what differentiates Omni from other ROMs. Is it a custom interpretation of AOSP code, like Cyanogenmod, or features ladled over Cyanogen code, like most other ROMs? Does it offer any of the fiddly knobs of Paranoid Android, or is this going to be a feature-avalance like AOKP or PAC?
I know things are still early days for Omni, but what am I looking forward to when I flash your ROM?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OmniROM is based on straight AOSP code, if you look in the source on github, you will see that VERY few repositories are actually forked from AOSP at all (put external in the search bar for Omni's public repos). Omni is designed to have many features and options that are all able to be toggled by the user. Omni is about choices, and giving the end-user the choices to make the ROM function the way that THEY want it to. 99% of features added to OmniROM come with a toggle to turn it on or off, hence "choices" :good:
The changelog pretty much gives a breakdown of all the features, because since the first 4.4 build, i did not make any releases until we fixed some major issues. This ROM is just about 100% stable. I say "just about" because if I reported my actual experience, which is literally ZERO issues, on nexus 5 and galaxy s 4, people would hang me and start bombarding me with "well what about this error I have that no one else does".
Best advice, make a backup and flash it. if you don't like it, then just restore your backup. no harm no foul. but i'm willing to bet you stick on this for a bit. There are a ton of features that are unique to OmniROM that other ROMs do NOT have.
also, pretty HUGE status update will be coming tonight (hopefully) as well
I'm freaking stoked I've been wanting to try OmniROM!
Sent from my SCH-I545 using Tapatalk
Thanks for the reply!
Source code is still gibberish to me, so I really appreciate the communication.
Sent from my SCH-I545 using XDA Premium 4 mobile app
I've been hoping that someone would bring this over to us so I could try it out. Been running it most of the day today with almost no issues. Haven't really had a chance to play with it a lot, but so far it's been pretty solid. It did lock up on me once when switching to ART (using the Banks gapps), but after reflashing with PA gapps and sticking with Dalvik I haven't had any issues. Battery life is solid, and having the extra kernel tweaks with the built in kernel is much appreciated. Looking forward to the updates, thanks!
Sent from my SCH-I545 using Tapatalk
Trygon said:
Thanks for the reply!
Will this rely heavily on Xposed for customization, or is there an Aroma style solution in the works?
Source code is still gibberish to me, so I really appreciate the communication.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, Xposed Frameworks mods will be up to the user to install and implement as they see fit. Generally, I think Omni has a fairly good amount of features already implemented, all with toggles to activate/deactivate, but as always, Xposed will be able to offer a little bit extra of things that we won't support out-of-the-box. I would be wary of using Xposed though, as you will need to ensure that the mods you are installed are updated for 4.4 Aroma will NEVER be implemented into OmniROM source, as it is not 100% stable and is not supported by all devices that Omni supports, and therefore would cause serious, serious issues. I'm sure people will make their own kangs of this eventually and there may be one with Aroma installer, but this will not ever implement that.
Also, some things to look forward to in the near future:
Omni File Explorer - OmniROMs native root file manager
native root support (you will no longer need to flash SuperSU in recovery)
OpenDelta - Omni's OTA Updater
NFC fix *properly*
Multi-Window
a big surprise in the next few hours
Ironclad Lou said:
I've been hoping that someone would bring this over to us so I could try it out. Been running it most of the day today with almost no issues. Haven't really had a chance to play with it a lot, but so far it's been pretty solid. It did lock up on me once when switching to ART (using the Banks gapps), but after reflashing with PA gapps and sticking with Dalvik I haven't had any issues. Battery life is solid, and having the extra kernel tweaks with the built in kernel is much appreciated. Looking forward to the updates, thanks!
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I would be VERY cautious of using ART as of now, it is still highly experimental in AOSP source and google needs to make a lot of improvements before I would use it standard
Thanks for all these update, it is greatly appreciated.. looking forward to the surprise tonight!
OMG we have Omni! Thanks so much! Let you know how everything's working tomorrow... glad to see your from Philly too :thumb:
Could disabling the 3-dot overflow be possible in a future update since this device has a capacitive menu key?
Sent from my Nexus 7 2013 using XDA Premium 4 mobile app
I was just thinking about Omni-ROM and here it is! You sir are awesome. Keep up the good work. I will flash right away once button lights work.
Sent from my SCH-I545 using xda app-developers app
{
"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"
}
Euphoria is mainly an AOSP based ROM with inclusions from other great projects like CM, Slim, Omni and many others. Euphoria is designed to increase performance and reliability over stock android for your device and at the same time merging best features that exists.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, 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 simply laugh at you. A Lot.
*
*/
Installation instructions:
Installing Euphoria-OS for the first time, or coming from another ROM
- Make sure you're running a proper working ClockworkMod-Recovery/Team Win Recovery Project
- Copy Gapps and ROM ZIP to your SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET
- Flash Euphoria-OS zip from SDCard
- Flash Gapps zip from SDCard
- Reboot
- Don't restore system data using Titanium Backup!
Upgrading from an earlier version
- Copy the ROM ZIP to your SDCard
- Boot into Recovery
- Flash the ROM zip from SDCard
- Reboot
Download 5.1:
Euphoria-OS-1.1-mondrianwifi-20150414.zip
Gapps Download 5.1:
http://209.95.39.164/Gapps/Lollipop/5.1/
Changelog
https://plus.google.com/u/0/106575705593326563158/posts/PHW36Vnr8yF
Source
https://github.com/Euphoria-OS-Legacy
Follow Us!
ROM OS Version: 5.1 Lollipop
Based On: AOSP
Thanks to:
Euphoria-OS Team
@crpalmer & CM for Device & Kernel tree
blazze11 - for bootanimation and drawables
eurochild - for providing us awesome graphics
Thanks to all the ROMs/Teams out there.
Looks great so far. Will have to try ressurrection tomorrow.
Thanks for all your work!
Thanks Sumit...will you be still doing the 325 version for this one? Thanks
mac231us said:
Thanks Sumit...will you be still doing the 325 version for this one? Thanks
Click to expand...
Click to collapse
Yes, I will do it for SM-T325 as it is working pretty satisfactorily and I got the keyboard bug fixed in resurrection remix rom for our device. I am happy and little relaxed. Will be compiling a build in a day or two. Cheers, Sumit
Looking forward to trying this one out tonight!
Did you create your own device files for this rom or did you use pre existing CM12.1 device files?
If you made your own, have you published them to github?
Nekromantik said:
Did you create your own device files for this rom or did you use pre existing CM12.1 device files?
If you made your own, have you published them to github?
Click to expand...
Click to collapse
oh here we go again..no offence
just hope all if ok with whatever Sumit has done as there are almost ZERO developers here...saw something similar happen on another device..and the lone developer was ejected and that was it...leaving behind some silly board that remained occupying space on some server somewhere with no support whatsoever
anyway hope all is ok...Sumit has been doing a great job AND DOES NOT EVEN HAVE A DONATE BUTTON..unlike some I have seen esp from my Note days who just create repositories and links to other folks works and collect 27000 thanks (literally) and put up a donate button while saying donations are not needed (really?)
again no offence to you if you are trying to help him out here (some folks just needle others for the sake of it..not saying you are)
Nekromantik said:
Did you create your own device files for this rom or did you use pre existing CM12.1 device files?
If you made your own, have you published them to github?
Click to expand...
Click to collapse
mac231us said:
oh here we go again..no offence
just hope all if ok with whatever Sumit has done as there are almost ZERO developers here...saw something similar happen on another device..and the lone developer was ejected and that was it...leaving behind some silly board that remained occupying space on some server somewhere with no support whatsoever
anyway hope all is ok...Sumit has been doing a great job AND DOES NOT EVEN HAVE A DONATE BUTTON..unlike some I have seen esp from my Note days who just create repositories and links to other folks works and collect 27000 thanks (literally) and put up a donate button while saying donations are not needed (really?)
again no offence to you if you are trying to help him out here (some folks just needle others for the sake of it..not saying you are)
Click to expand...
Click to collapse
Hi There,
I am using the same CM device and kernel tree that it available @ https://github.com/cyanogenmod
I only changed some make files to compile this and other roms i wish to bring in the future. Since I intend to bring many more roms for our device, I dont want the extra hassle of pushing it to github. Honestly, I dont even know how to do so. Have successfully compiled temasek, blisspop and xenonhd using the same device and kernel tree for our device.
Hope that puts everything to rest.
Cheers, Sumit
mac231us said:
oh here we go again..no offence
just hope all if ok with whatever Sumit has done as there are almost ZERO developers here...saw something similar happen on another device..and the lone developer was ejected and that was it...leaving behind some silly board that remained occupying space on some server somewhere with no support whatsoever
anyway hope all is ok...Sumit has been doing a great job AND DOES NOT EVEN HAVE A DONATE BUTTON..unlike some I have seen esp from my Note days who just create repositories and links to other folks works and collect 27000 thanks (literally) and put up a donate button while saying donations are not needed (really?)
again no offence to you if you are trying to help him out here (some folks just needle others for the sake of it..not saying you are)
Click to expand...
Click to collapse
I was simply, asking as I needed some help as I was trying to compile my own ROM. DONT jump to conclusions, that really annoys me when people do that online.
vasumit said:
Hi There,
I am using the same CM device and kernel tree that it available @ https://github.com/cyanogenmod
I only changed some make files to compile this and other roms i wish to bring in the future. Since I intend to bring many more roms for our device, I dont want the extra hassle of pushing it to github. Honestly, I dont even know how to do so. Have successfully compiled temasek, blisspop and xenonhd using the same device and kernel tree for our device.
Hope that puts everything to rest.
Cheers, Sumit
Click to expand...
Click to collapse
Ah ok. I used CM trees for Omni but it wont even start the build. Ha
Nekromantik said:
I was simply, asking as I needed some help as I was trying to compile my own ROM. DONT jump to conclusions, that really annoys me when people do that online.
Click to expand...
Click to collapse
Hence my repeated "no offence" ..."again no offence to you if you are trying to help him out here (some folks just needle others for the sake of it..not saying you are)"
Thanks hope more devs can join in here..meanwhile I could not even get the framework-res.apk to install (apktool if...)...lol
EDIT managed to get past the brut error (whatever reason was failing on install on earlier cm12 framework-res.apk install..in decompiling latest 4/14 cm12 mms it appears this code is now there (was not a week or two back unless am mistaken)
http://review.cyanogenmod.org/#/c/89427/
will see if it actually works
Hi Friends,
Compiled an Euphoria build for SM-T325 owners. Try it and let me know how it works.
Euphoria-OS-1.1-mondrianlte-20150415.zip
Cheers, Sumit
vasumit said:
Hi Friends,
Compiled an Euphoria build for SM-T325 owners. Try it and let me know how it works.
Euphoria-OS-1.1-mondrianlte-20150415.zip
Cheers, Sumit
Click to expand...
Click to collapse
Hello Sumit..thanks for your work. Your ROM works very well (for the things I use for, scores of apps and basic calling, sms, mms, internet..no Netflix though or any audio stuff)...
few things noticed..not sure if I missed something as I was doing this at work (there did not seem to be options for adding tiles to the pull down quick settings)...EDIT...duh...found that!
also when trying to change lcd density it came up with preset options which is fine but no custom (when I did the change through build prop editor and rebooted, I then saw my new density that I had put in the editor now shown in the list of densities, which I then had to choose to enforce it)...
a third thing is that it crashed suddenly when barely setting it up (was in playstore)..now this is something I have experienced with the Cm12.1 (not cm12) builds (random crashes here and there) (have also had the screen go off into deep sleep a few times on cm12.1-the device could not be woken and had to go to recovery to start things again..have not used this build long enough to see if it happens but suspect it could or maybe inherit this from cm12.1 (again my suspicion)...
fourth thing interesting is that if you recall the CM package that I mentioned about having data auto on off for mms send/receive? It has just made its way into the latest 4/15 CM12 (not 12.1)...I have been checking both versions for some time almost every 2 days so know this just got inserted into CM12 (do not recall seeing it in 4/14)...it is not in cm12.1 (and hence? not in your build)...I tried it out on the 4/15 build and it works like a breeze..attached here is the screenshot of the mms data options from the 4/15 cm12 nightly for the mondrianlte. With that and the fix for the echo (not speakerphone yet though) the CM seems to be ready in my world for daily use.
EDIT think this auto data on off option feature may have come in earlier and I simply did not notice..can't be sure am second guessing myself now..the apk and mms service are identical in size going back to 4/11 and 4/10 is when I may have even looked at in detail in terms of actually running it for some time..but definitely cm12.1 does not have that feature yet
http://review.cyanogenmod.org/#/c/67611
minor...crdoid had an add power menu or add go to sleep (think it is the latter) button in the nav bar..nice to have-understand maybe lot of work for that. not a big deal.
So far, this is what I have to report. Thanks for your work. I will keep checking the build again later tonight hopefully. Appreciate if you could look into the above.
copying and pasting the mms.apk and the mmsservice.apk from the priv_app folder of one of the latest cm nightlies to the crdroid march 23 t-325 LTE rom (which is 5.0.2?) and then setting permissions works..no issues (needless to say but I tried-g they do not work on cm12.1 or the 5.1 builds) as of today 4/16 still no mms auto data on/off option in cm12.1 mondrianlte
unfortunately cannot decompile the cm12.1 mms.apk as cannot even install the framework-res.apk resources...get apktool brut error..this is a known issue here
http://forum.xda-developers.com/showpost.php?p=60000934&postcount=94
EDIt
found this it works to install and decompile 5.1 apks
http://forum.xda-developers.com/showpost.php?p=59436776&postcount=2812
A little teaser for all paranoid android fans out there.
#stayparanoid
since 12.1 seems to have not yet merged the mms mod (as in cm12) I took the mms apk and mmsservice files from this S3 build that has it fixed...and put it in cm12.1 latest 4/20 build and it works! sms and mms (auto data on off for send/receive) Now will put it in your Euphoria build later today.
http://forum.xda-developers.com/gal...cial-cm12-nightlies-d2att-4-7-t3075452/page13
edit
one thing latest cm12.1 builds (well at least 4/17 and 4/18) have exchange email sync error issues (non stop popup)...4/16 and earlier work..not sure of 4/19 and 4/20 to see if they fixed anything
Hi! Wanted tot try this today but the gapps link show an empty webserver directory. Could you provider the correct version please?
Thanks!
Rom update
Hello Friends, its time for an update,
Download: Euphoria-OS-1.1-mondrianwifi-20150422.zip
Changelog: Android base updated to Lollipop 5.1.1_r1, added governor zzmoove, intellidemand, smartmax, intelliactive and many more also included scheduler ZEN, VR, SIO, FIOPS in the mix. This is just an experiment. Using default CM kernel tree and just added some governors and schedulers. THATS ALL, nothing more, nothing less.
Also Gapps link has been updated in the OP.
Cheers, Sumit
Thanks Sumit. Now for my usual request (sorry) but can you have one for the t325..or perhaps have a flashable patch if possible? Thanks (either Euphoria or Resurrection...appears Resurrection has more options? ..wondering but maybe your Euphoria is more up to date) anyway thanks for your work! You almost alone are keeping this development area ticking!
Sent from my SM-T325 using XDA Free mobile app
Rom works fine
Even after dirty flashed from cm 12 with wiping system and cache only.
Used slim gapps .
Only intelliactive governor gives me random reboots.
I havent tried others yet
Thanks
Will this work on T520 10.1 ?
{
"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"
}
Disclaimer:
Code:
/*
* 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.
*
*/
Krexus was born out of a simple necessity. The latest releases of stock Android (namely lollipop and marshmallow) were pretty close to my idea of a perfect android ROM, yet missing some elements, which are meant to be included in stock Android, at least for me. Starting from a clean AOSP environment, only specific features and fixes are included, which are personally tested, with one goal in mind. To create a stock like android ROM, "as it should be".
This means, and I mean it, a ROM like how stock nexus image should be, for me.
This isn't going to get bloated. Most UI "features" are already there.
This isn't going to start picking commits relentlessly, I will test them personally and only add things that 1) work like they should 2) would fit in a stock ROM.
This isn't going to be updated very quickly. Only security and bug fixes will be pushed out ASAP.
This is going to follow Google's & AOSP guidelines as closely as I can.
And lastly, this is first and foremost a ROM about Nexus 5 (hammerhead). This is my personal device, this is where I test the ROM. angler, bullhead, flo, mako, shamu builds are provided AS-IS, and bugs/missing stuff/features especially for them will be put on the lowest priority and will depend on my free time. I will only guarantee the nexus 5 ROM and its abilities.
That said, welcome aboard!
Google+ Community
Krexus kernel (aosp stock)
PushBullet Channel
DOWNLOAD LINKS: AndroidFileHost
DOWNLOAD LINKS: BasketBuild
CHANGELOG
XDA:DevDB Information
Krexus, ROM for the Google Nexus 5
Contributors
KreAch3R
Source Code: https://github.com/krexus
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Created 2015-12-26
Last Updated 2016-08-29
Features List
This is an attempt to include every important (to the end user or dev) feature and/or advancement merged into this ROM, compared to AOSP. A lot of them are work of others, whom I truly thank; many of them are modified by me to specifically fit these ROM's needs; and a few of them are my original work (which I'm proud of and I will bold ).
I want to point out two things here:
This list isn't completely uptodate. I am creating new stuff all the time
You should really install the ROM to get the feeling of it
Screenshot IMGUR Album! (or you can check the screenshots in DevDB screenshot tab)
Check this google+ post for a better updated feature list
Or, if you don't like google+, here is the direct link
For something extra, check this out
Of course, there are many, many more... just browse krexus github: https://github.com/krexus/
Video Review of the ROM: Thanks +https://plus.google.com/+AVKAppReviews
F.A.Q.
Check this google+ for a better updated version
If you don't like google+, here is a direct link
This will be the post where I am going to write any new updates for my ROM. First of all, welcome!
For XDA, this is a new ROM. But for Google+, it isn't. I have been testing it and releasing some builds in this private community, so make sure to ask to join for the latest info! I created this thread to let more people try my ROM, only now that I feel that it is in an almost perfect condition.
As as I said, my idea is to create a better stock ROM, and this is my target goal.
Another one of my target goals is to make the release of a new build almost automated. Right now, the compilation of the 6 devices build list is finishing, and is uploaded to basketbuild, using clever smart scripts. This also updates the changelog in my site, so I don't have to write a new post every time a new build is released. Everything should just work!
Speaking of releases, the ROM comes with an updater, so you don't even have to check the community or this thread for new links. But follow the pushbullet channel if you want!
I've been copy/pasting information for the past half hour, so this new thread is bound to have mistakes and inconsistencies. Let me know and I'll fix it!
Some other important points:
You have to flash SuperSU and GApps.
If you have a question, you should check out google+, in case it's there.
For the Devs: check my vendor folder, I have been developing some automation scripts which, I think, you will like!
I am an one man team, sorry for any slow responses.
Yes, this ROM is released for 6 devices, not hammerhead only. You can grab the zips from Basketbuild. I haven't created XDA threads for them (yet) because I don't own them.
I hope you like the ROM!!!
First
Welcome here?.
To users,
I've been using this ROM since it has started and it is really THE BEST rom for me. Super stable, and contains only necessary features.
Sent from my Nexus 5 using Tapatalk
Crytech said:
First
Welcome here.
To users,
I've been using this ROM since it has started and it is really THE BEST rom for me. Super stable, and contains only necessary features.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you! And thank you especially for the ROM feedback. :good: Go ahead new thread reader, give it a try
Yeah, Krexus thread will come for grouper soon also
Sent from my Nexus 5 using Tapatalk
Ooh, always tempting to try out a new ROM...
Thanks for this simple and light weight ROM Does it include Google UI Sounds or AOSP sounds?
Trying this out. Thanks
Creative9170 said:
Thanks for this simple and light weight ROM Does it include Google UI Sounds or AOSP sounds?
Click to expand...
Click to collapse
I am going for a better stock, so it should surely have them. They are also mentioned in the features post. Welcome to Krexus!
Awesome work my friend.
This rom is the fastest and most stable I've tried. It really is "Stock, as it should be".
Thank you very much for everything. :good:
KreAch3R said:
Krexus was born out of a simple necessity....
Click to expand...
Click to collapse
Awesome new rom mate !
I suppose you have a little Java and C++ to get all that stuff rolling.
I would like to thank you to push up a new rom here. I smell it to become well known as it seems very, very good.
However, i am not flashaholic, AT ALL, and i'm running Chroma since a month, and i will wait a bit to make the jump.
Just a few questions :
- Are you using the stock toolchain ?
- Did you edited AOSP hammerhead kernel source ?
Thanks for the time you spent to read my comment. Keep up good stuff, i will follow you !
"Kalesnukta" (i dont have greek keyboard )
dekefake said:
... i am not flashaholic ...
Click to expand...
Click to collapse
Yes? You called me? what can I do for you? :silly:
Will test it, and report back tomorrow night.
Thanks for this ROM!!
btw @dedefake I remember you from the Dev-Preview-time
I suppose the right question was did you port the google stock sounds or the AOSP sounds? because AOSP sounds doesn't ring too much in the ears(audio quality is off)
Great ROM dev,
Great R/W speed and smoother than butter
A huge thanks
BIade said:
Yes? You called me? what can I do for you? :silly:
Will test it, and report back tomorrow night.
Thanks for this ROM!!
btw @dedefake I remember you from the Dev-Preview-time
Click to expand...
Click to collapse
Aaaaha lol yeah i will test it soon
Yeah i did some zips of them
Jax Teller said:
Awesome work my friend.
This rom is the fastest and most stable I've tried. It really is "Stock, as it should be".
Thank you very much for everything. :good:
Click to expand...
Click to collapse
Thank you for being an amazing tester!
dekefake said:
Awesome new rom mate !
I suppose you have a little Java and C++ to get all that stuff rolling.
I would like to thank you to push up a new rom here. I smell it to become well known as it seems very, very good.
However, i am not flashaholic, AT ALL, and i'm running Chroma since a month, and i will wait a bit to make the jump.
Just a few questions :
- Are you using the stock toolchain ?
- Did you edited AOSP hammerhead kernel source ?
Thanks for the time you spent to read my comment. Keep up good stuff, i will follow you !
"Kalesnukta" (i dont have greek keyboard )
Click to expand...
Click to collapse
Thank you for the kind words! I have got some Java knowledge by working on the Android source, but no C++ yet. It's a byproduct, not the goal anyway.
To answer your questions:
1. Yes, toolchains are stock, and they aren't changing any time soon. I have never personally seen any difference with them, only (in a few cases) weird bugs, so I am following Google on this one.
2. Kernels are stock, too. I am trying to be modular and only provide a ROM. I believe that everyone uses his phone differently and you can't be a jack of all trades; that's why you have to flash your SuperSU, and your GApps, and your kernel. Only *mako* is having its own kernel, because Google dropped support.
And thank you, "Kalimera"
phantom146 said:
I suppose the right question was did you port the google stock sounds or the AOSP sounds? because AOSP sounds doesn't ring too much in the ears(audio quality is off)
Great ROM dev,
Great R/W speed and smoother than butter
A huge thanks
Click to expand...
Click to collapse
I am using the latest marshmallow Google stock sounds I can find. I hate the default AOSP ones, they sound so kitkatish.
Another question:
Are this odexed or deodexed? I hope its odexed from priv-app down to system files for faster boot time and app launching
My turn to welcome the perfectionist KreAch3R
Using Krexus before even "public" release as a daily driver, performance and simplicity, what else to ask !
Many thanks George for sharing your work with us :good:
( Thanks Jax Teller for pointing the thread on time, i was off since yesterday )
KreAch3R said:
Thank you for being an amazing tester!
Thank you for the kind words! I have got some Java knowledge by working on the Android source, but no C++ yet. It's a byproduct, not the goal anyway.
To answer your questions:
1. Yes, toolchains are stock, and they aren't changing any time soon. I have never personally seen any difference with them, only (in a few cases) weird bugs, so I am following Google on this one.
2. Kernels are stock, too. I am trying to be modular and only provide a ROM. I believe that everyone uses his phone differently and you can't be a jack of all trades; that's why you have to flash your SuperSU, and your GApps, and your kernel. Only *mako* is having its own kernel, because Google dropped support.
And thank you, "Kalimera"
Click to expand...
Click to collapse
Okay awesome as i seen you pushed sources to github. I will test your rom soon and build my own ones using Uber toolchain if i like it, but im sure i will like it
Androidov 1.0M
Since cyanogenmod removed some features which I used I was looking for some other room which will satisfy my needs. I've tried couple of ROM's provided here but I was very bad surprised. Some users and maintainers probably don't read between the lines, providing unsecure builds to the community by settings Selinux to permissive... or cherry-pick features which can compromise your security. That wasn't problem until I asked " Why permissive?" and the answer was "I like permissive!" ... or some ROM maintainers which answer you just " I am the maintainer and I will do whatever I want ". Well... go on boys!
Anyway... I builded my own ROM. As I use my surnia as one and only I am focusing on stability en security. Because I don't like permissive... this ROM is with Selinux enforced. It is based on Cyanogenmod 13 as it runs more stable than Cyanogenmod 14.1 at this moment. As I do with every software... I will wait about 1 month until I update it to 14.1 - until then much bugs will be gone.
I don't want to bloat this ROM so I will keep the changes as minimal as possible. This ROM is not meant to provide as much features as possible... just pick the best one and include them.
This first build is meant to be tested. It runs stable for 3 days on my phone and I didn't noticed any issues. If you encounter any issues, please let me know.
Every suggestion for features to be included is highly appreciated!!!!
I will update this ROM WEEKLY! As providing nightly builds is not really needed in this case as the changes are minimal and in my case it isn't worth investing my time in setting up a build-bot for it.
Next build I will provide will be reorganized - I will direct all the features in the Settings app under "Extra features" section. I will organise my last changes, commit them to my github and will provide a link with build instructions. It will take me some time as I am working till late next 2 weeks.
Credits
I am not java developer... well I have basic knowledge, but I can't call my self e java developer. I forked features which are already included in some other ROM's and I changed some lines in the code in order to integrate them.
So thats why I want to thank:
Cyanogenmod Team
Android Ice Cold Project (AICP)
SlimRom Team
Sources
Well... here you go:
https://github.com/rpangelov/android
Features
AdAway - Well... maybe I could have replaced the host file and include it in the build... but you won't be able to stop or update the adblocker. In some cases this can cause problems... so I decided to prebuilt AdAway. AdAway is adblocker which does the same - it replaces your host file with one downloaded from the app server. It provides you the choice to stop the adblocker by restoring your original host file or update it with newer version.
KernelAdiutor - there you got even more options and statistic. It provides even init.d emulation! This is cool if you want to run ViPER4Android for example, which is good! Pay attention - it EMULATES init.d function. init.d is disabled in this build as it is suggested again - for security reasons.
Disable fullscreen keyboard in landscape - you can find this option in Language and Input options -> Advanced settings. Because surnia is 4,5'' screen, I use it sometimes in landscape mode and I don't like when keyboard is fullscreen...
{
"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"
}
Suggest more features and I will add them if they are good to use!
Download
Update: Here I provide the last test build Download
It isn't finished, but I aborted developing this rom for this moment, as cyanogenmod is death. I will rebase the rom. Merry christmas! I will keep you in touch.
Placeholder threads for ROMs/Kernels are not permitted. Closed - can be reopened when code available to download. Remember sources and credits too...
Re-opened to allow file links to be added...
this rom volte supported?
I think u should base this ROM on CM14.1 as it is alot more stable now and also this ROM will gain traction as most users (like me) want to run the latest version of Android for its features and to show their friends (like me). Also as far as security is concerned however secure the ROM is it is rooted so u can't call it secure. Anyway that's my opinion. Good job on the ROM. It works perfectly fine on my device and it is pretty stable. Keep up the good work! I'm not trying to insult ur work, I know it's hard to build ROMs (Speaking from experience and clearly u r better than me at doing it) but I just had a few suggestions and opinions I wanted to share.
Sent from my XT1521 using XDA Labs
ayush rao said:
I think u should base this ROM on CM14.1 as it is alot more stable now and also this ROM will gain traction as most users (like me) want to run the latest version of Android for its features and to show their friends (like me). Also as far as security is concerned however secure the ROM is it is rooted so u can't call it secure. Anyway that's my opinion. Good job on the ROM. It works perfectly fine on my device and it is pretty stable. Keep up the good work! I'm not trying to insult ur work, I know it's hard to build ROMs (Speaking from experience and clearly u r better than me at doing it) but I just had a few suggestions and opinions I wanted to share.
Sent from my XT1521 using XDA Labs
Click to expand...
Click to collapse
About the building... it's not hard, but I needed to clobber couple of times, because I didn't set proper my IDE. The new tools introduced ninja and jack are cool, but I had issues with running jack properly.
I had 3 issues:
1. Hardware fault - as the PC I build on is assembled out of box with lot's of second hand parts I have 2x2GB RAM and 1x4GB RAM. The first issue I came through was segmantation fault's caused by the difference between the Mhz of the RAM modules.... so I had to take out the 4GB module as it was faster than the other two - 1333mhz.
2. As I thought... JACK will run out of memory... and it did. AOSP recommend 16GB of RAM and I have 4 at the moment... which isn't the problem at all, but the builds are generating slow. Anyway... I tried to set 3GB of ram for jack by exporting variable for JACK, but this is probably not that good, because it continued to complain about not enough memory. SO i set this 3GB of ram directly into prebuilts/sdk/tools/jack_server_setup.mk and it was good.
3. What I didn't expected... is that jack wasn't able to reach server, because "the port was used by another PID"... and this PID was JACK it self... so I just deleted ~/.jack-settings . By running jack once more, it will generate exactly the same file with the same settings, but it all works fine. So no idea where this issue is coming from...
I build on Debian Testing as I don't like Ubuntu, and Debian stable doesn't provide the updated packages needed to build Android N. If you have any issues or questions about building CM 14.1 or this ROM, let me know.
I Agree with that. Since CM 14.1 is official I am updating the rom and took me a while, but it is all good.I am testing now the new build - I've already updated the repo's on github. After couple of hours I will upload the new build of all works good. I need to check some log's. Will keep you in touch!
rpangelov said:
About the building... it's not hard, but I needed to clobber couple of times, because I didn't set proper my IDE. The new tools introduced ninja and jack are cool, but I had issues with running jack properly.
I had 3 issues:
1. Hardware fault - as the PC I build on is assembled out of box with lot's of second hand parts I have 2x2GB RAM and 1x4GB RAM. The first issue I came through was segmantation fault's caused by the difference between the Mhz of the RAM modules.... so I had to take out the 4GB module as it was faster than the other two - 1333mhz.
2. As I thought... JACK will run out of memory... and it did. AOSP recommend 16GB of RAM and I have 4 at the moment... which isn't the problem at all, but the builds are generating slow. Anyway... I tried to set 3GB of ram for jack by exporting variable for JACK, but this is probably not that good, because it continued to complain about not enough memory. SO i set this 3GB of ram directly into prebuilts/sdk/tools/jack_server_setup.mk and it was good.
3. What I didn't expected... is that jack wasn't able to reach server, because "the port was used by another PID"... and this PID was JACK it self... so I just deleted ~/.jack-settings . By running jack once more, it will generate exactly the same file with the same settings, but it all works fine. So no idea where this issue is coming from...
I build on Debian Testing as I don't like Ubuntu, and Debian stable doesn't provide the updated packages needed to build Android N. If you have any issues or questions about building CM 14.1 or this ROM, let me know.
I Agree with that. Since CM 14.1 is official I am updating the rom and took me a while, but it is all good.I am testing now the new build - I've already updated the repo's on github. After couple of hours I will upload the new build of all works good. I need to check some log's. Will keep you in touch!
Click to expand...
Click to collapse
Nice to know. Dude why don't you use Linux Mint. It's pretty amazing and has all the required packages. For all the builds I've done (2) I've used Ubuntu and it has never let me down. Also it works very well on old and unpowered hardware.
Sent from my XT1521 using XDA Labs
ayush rao said:
Nice to know. Dude why don't you use Linux Mint. It's pretty amazing and has all the required packages. For all the builds I've done (2) I've used Ubuntu and it has never let me down. Also it works very well on old and unpowered hardware.
Sent from my XT1521 using XDA Labs
Click to expand...
Click to collapse
I will give Mint a try... maybe. I won't use ubuntu because many of reasons... but lets classify them all by - I dont like company products... so my choise will always be for community developed product. I use Debian ever since version 3.0.... so let's say for more than 10 years, so I am really used to it and won't change it for any other OS as in my personal opinion, this is the most stable peace of software you can get.
Anyway... I completed the build, but it is running unstable because of errors in the landscape mode of the keyboard - I didn't implemented it good... as I am not java developer this is my learning process into java. I have traced the issue, checked out the logs and I know which line is causing the problem. This peace of code was not a problem when I builded CM 13, but some things differs in CM 14.1. Anyway... I've founded different implementations of this feature in other rom's, but I have to research it and try it out, because no other rom has proted this feature to nougat at this moment. I am doing my best to get it work properly, but I can't give exact time how long it will take. It won't be long, but it can take me couple of days to fix the issue.
If you have any other suggestions for other handy features, feel free to share it
Greetz
So... as cyanogenmod is shutting down... expected move as 3 weeks ago Steve Kondik lefted cyanogen inc. I will move this ROM to "LineageOS" - the cyanogenmod community follower. Check the website - http://lineageos.org/ This is good, because cyanogenmod was making bad deals... and this was bad for the whole android community as Cyanogenmod is the leader in ROM community. Well... in my point of view - bad deals comes when business is involved... the quality of the product becomes second... and the main priority is money profit. Anyway... every community based product will be better. So I am happy because of this move.
Let's be patient and see what's coming. I won't develop this ROM any further as Cyanogenmod (the base of this rom) is shutting down. As I don't know what the new ROM will provide, is for me hard to say how this ROM will continue.
What about this ROM now? Well... I didn't made any big changes to it. If some one wants, I can give a link to test build based om Nougat - it runs stable, with only feature provided - disable fullscreen keyboard in landscape. No prebuilt apps or anything else.
VoLTE Supported...
And add some screenshots
Deepak5310 said:
VoLTE Supported...
And add some screenshots
Click to expand...
Click to collapse
Yes, VoLTE supported. I didn't provided screenshot's, as they will be the same as Cyanogenmod.
rpangelov said:
Yes, VoLTE supported. I didn't provided screenshot's, as they will be the same as Cyanogenmod.
Click to expand...
Click to collapse
CM 13 based
Deepak5310 said:
CM 13 based
Click to expand...
Click to collapse
I am editing the post - wait couple of minutes and you will see new link with build CM 14.1 based.
PS: As I don't develop it any further, because I will move it to another base-rom, CM14.1 based build was meant to be tested, but it runs stable. I use it without problems.
rpangelov said:
I am editing the post - wait couple of minutes and you will see new link with build CM 14.1 based.
Click to expand...
Click to collapse
Thanks sir
{
"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"
}
Code:
/*
* Your warranty is... still valid?
*
* 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.
*
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review ( http://review.lineageos.org ).
Important:
This thread is for stock LineageOS 13.0 and any mods, kernels or Xposed framework will not be supported.
If features, options or code is NOT in the official source code, it will not be in my builds.
Recommended Firmware:
Most recent firmware for OOS 3.6.1 is recommended.
Known Bugs:
None
Installation:
Download the zip(s)
Install a compatible Recovery (TWRP recovery recommended)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon http://opengapps.org/ ( I tested nano and stock pkgs)
Reboot
Note: Built in root is available in Dev Options, but I'd use magisk
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
Downloads:
AFH
How to enable Volte.
You can read the full instructions HERE
XDA:DevDB Information
LOS 13.0 Unofficial, ROM for the OnePlus 2
Contributors
monark88, LineageOS Team & Contributors
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: OOS 3.6.1
Based On: LOS-13.0
Version Information
Status: Stable
Created 2018-01-21
Last Updated 2018-06-24
I know some of you may wonder why even post something as old as marshmallow. I still get a lot of use from LOS 13, and have been building it for myself for a while. I figured I'd upload the latest with Jan security patches, for those who want it. Happy flashing.
Not sure about the support we'll get from LOS going forward. They never merged February security patch, but they may have just been busy. We'll see.
does it have hal3 with hdr and all that cool quality we used in marshnallow?
chxei said:
does it have hal3 with hdr and all that cool quality we used in marshnallow?
Click to expand...
Click to collapse
It does, HAL3 and hdr
I run mine with amplify, greenify, android n-ify, gravitybox, and alert slider app
monark88 said:
LOS 13.0 Unofficial, ROM for the OnePlus 2
Click to expand...
Click to collapse
wow, this is great!
thank you mate!
You can get volte by flashing the kenzo patches. Just saying.
I also built this ROM myself to which I had mentioned in another post. Good job!
Any chance you're able to build with release keys instead? This will then allow some apps (its quite minimal) to run correctly.
Woodzrul said:
I also built this ROM myself to which I had mentioned in another post. Good job!
Any chance you're able to build with release keys instead? This will then allow some apps (its quite minimal) to run correctly.
Click to expand...
Click to collapse
The download link now points to a signed version. You can download it here:
https://www.androidfilehost.com/?fid=673956719939814327
using 22nd Jan build since yesterday.
I missed so much the great customization that CMTE brings to LOS!
as far as I can see 'til now, there's no issue at all with your ROM.
excellent work, thank you!
utkarsh102 said:
You can get volte by flashing the kenzo patches. Just saying.
Click to expand...
Click to collapse
More info on this, please?
Kenzo is redmi note 3 iirc
Would the .zips work for OP2?
GuyGotMadNameGame said:
More info on this, please?
Kenzo is redmi note 3 iirc
Would the .zips work for OP2?
Click to expand...
Click to collapse
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
utkarsh102 said:
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
Click to expand...
Click to collapse
I'll add this to the first post
utkarsh102 said:
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
Click to expand...
Click to collapse
Thanks for this. I updated first post.
Does anyone know of any cm13 theme which properly themes all the essential apps?
This ROM has been a really good ride for the past month or two for me - very stable and actually there is not much new in Android 7.x which really matters. LineageOS unfortunately made 14.x unstable by reworking the kernel in the middle. It's ok for the most time but then some random event happens and it will drain your battery in few hours.
I think I will stay on this ROM assuming Android security patching still happens in future. Thanks monark88!
aiwan3 said:
This ROM has been a really good ride for the past month or two for me - very stable and actually there is not much new in Android 7.x which really matters. LineageOS unfortunately made 14.x unstable by reworking the kernel in the middle. It's ok for the most time but then some random event happens and it will drain your battery in few hours.
I think I will stay on this ROM assuming Android security patching still happens in future. Thanks monark88!
Click to expand...
Click to collapse
I've got a new build, but nothing is significantly changed. I've been working on a custom kernel for MM, with extra governors and upstream merges. I'm running this ROM myself, so you can bet when there is a security patch, I'll upload it for us all.
I'm with you on anything above android 6.0. When LOS 14.x kernel was reworked, I was on RR unofficial. I remember the drastic changes. I compiled this not soon after and have been on it since. I've watched on the forums as everyone has scrambled after HAL3, and balancing HAL3 with HDR (or the lack there-of) and all the non-sense that goes with it.
Meanwhile we've got manufacturer supported blobs and code for everything our phone was meant to do, in a nice stable OS.
If you're reading this, and thinking about trying it, just download the ROM, flash xposed (or use xposed magisk) and get Android N-ify, Amplify, Greenify, Alert Slider, and GravityBox. You'll be kicking it on the OP2 old school, updated, and stable.
That's right. Many people don't seem to be very methodical when testing new ROMs. Mostly noted on comments about battery life. I don't use my phone much as the majority of my daily work / comms happens on PC - so its easy for me to see changes when I update the phone. I don't use gapps either, so my testing is purely based on the kernel and the ROM performance. This ROM can go up to 5-6 days in idle / light usage, whereas the latest official LineageOS 14.x is probably around 4 days same use. Feel free to test. Same applies to boeffla-kernels, they consume much more battery on idle than the LineageOS stock.
I'm not a developer myself but it's easy to understand that all this hacking for newer Android versions than the source code provided by manufacturer, can very easily lead into problems. It could be ok, but unfortunately many people always think that the latest is always better. I think it's fair to say that new android versions just complicate the menus and slow down devices more than the useful features provided. As long as security is updated, I don't really see any need for Oreo in my phone.
It's nice to hear that you are also testing for new things in kernel, I might test them if provided as separate update.zip. However I assume most people using LOS 13 or your build are probably after stability.
Hold on right here...i need a minute to comprehend...so, basically, if i flash this, i will get the most stable android experience there is, it will most likely improve my battery live over N/O roms, i will have all the OOS 3.6.1 OP2 features working (including things such as slow motion, HDR and panorama), the latest security patch will be installed and the only drawback is that it will be a MM release? whats the catch ?
Jackill said:
Hold on right here...i need a minute to comprehend...so, basically, if i flash this, i will get the most stable android experience there is, it will most likely improve my battery live over N/O roms, i will have all the OOS 3.6.1 OP2 features working (including things such as slow motion, HDR and panorama), the latest security patch will be installed and the only drawback is that it will be a MM release? whats the catch ?
Click to expand...
Click to collapse
Lol, for the most part (and in my opinion) yes.
The catch is that if you like the latest cutting edge features, we don't have that built-in here. All we offer is a stable phone that has ALL of the features working in some form or another, without wondering what will break in the next build.
For the record, I still flash Oreo ROMS on MultiROM to stay aware, but I run this as a daily driver.