Related
<<< THESE ARE UNOFFICIAL BUILDS || THE I777 IS NO LONGER SUPPORTED BY THE SLIM TEAM >>>
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
YouTube Channel - Feature demonstrations, reviews, tips & tricks.
Downloads - Download the rom, gapps and other addons.
<<< Download Unofficial i777 Builds Here >>>
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
**Coming from any pre-4.4 firmware...
The installation instructions still apply. Be sure that you are using a kernel with either CWM 6.0.4.4+, or TWRP 2.6.3.0+.
SlimRoms' 4.4.X kernel uses TWRP 2.7.0.1 (included in the firmware), and can be found in the i777 slimkat download repository
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
[ROM][4.4.2][01/04]SlimKat - I9100 [Build 4][WEEKLIES], a ROM for the Samsung Galaxy S II
Bringup&Maintenance credit:
@fronti90 | Michael Braun
@HardCorePawn | Jared Yates
Significant device contribution:
@Entropy512 | Andrew Dodd
@codeworkx | Daniel Hillenbrand
OS Version: 4.4.x KitKat
Kernel: Linux 3.0.x
Based On: AOSP
Known Issues:
SDCard/Fuse Daemon issues (aka "Music Playback Bug"). On extended music play it can suddenly happen that the playback stops.
Camcorder - Zoom on 1080p mode is buggy see below for "workaround"
Notes:
If you are running on ART, and you're having issues with an app... check this list to see whether app is known to have issues with ART.
Zoom on 1080p mode "sometimes" works... if you set camcorder to 1080p, switch to camera, change res so zoom starts working again, and then switch back to camcorder... zoom will work on 1080p :silly: However, if you turn the screen off, or close and re-open the camera, the zoom will be broken again Also, once it stops working on camcorder, it'll probably stop working on camera as well until you change the resolution/picture size
4.4 mini-FAQ
Q) My recovery won't flash the 4.4 zip... aka "Status 7 error"... what do I do?
A) Get the i9100_SlimKat_4.4.2_compat_recovery zip from this post... flash it... reboot to recovery... be amazed by new TWRP recovery... then:
Wipe - Advanced - Select cache, dalvik, system (and Data if you want FULL wipe)
Install Slim ROM + Slim Gapps
Reboot
Profit!
Q) Root doesn't work!
A) From a clean build you need to enable root access for Superuser itself. This is different from some earlier versions of android (4.2 and below) in which Superuser by default had root access on a new install. To do this, go to Settings -> Developer options -> Root access. If an app attempts to request root access before Superuser itself has access, it may cause problems with that app in the future where root requests are silently denied.
Q) Developer Options? What Developer Options? I don't see that in Settings??!?
A) By default, this is conveniently hidden from view... as it does contain settings and options that can (and will) break stuff if you don't know what you're doing. If you require access to this, Settings -> About Phone... Then tap on the Build Number 7 times.
Q) How to change DPI?
A) Currently, this feature hasn't been ported... so either change ro.sf.lcd_density to the desired value in /system/build.prop, or you'll need to install Texdroider DPI from the playstore.
Q) I upgraded and lost my sim unlock, none of the unlock tools are working?
A) Unfortunately, I have nothing but Bad News™ for you Seems Samsung locked everything down and Google played along... Get a "proper" (aka carrier) unlock... or use older versions of Android... There is nothing we can do
Q) Music just randomly stops playing... and then won't work properly until reboot and/or drains battery?
A) Unfortunately, there isn't a whole lot we can do. Due to new SDCard handling and issues with FUSE, there is a strange quirk with Exynos4 devices like i9100 and n7000 where the system freaks out and dies... users have had various levels of success trying some of the following workarounds: 1. format sdcards with ExFAT (apparently can cause issues with backups and/or GPS apps??)... 2. Put all your music on internal SD...
More details can be found in this OmniROM thread...
<<< Download Unofficial Builds Here >>>
Built from Slim Source, no changes whatsoever.
I, Cyril, am not a developer or maintainer of any sort
These are UNOFFICIAL builds, this device is no longer supported by the Slim-team.
The goal is to provide yet another Android 4.4 option for the SGH-i777.
I plan to build as time permits; no sooner than weeklies, and I'll be sure to capture stable releases.
Massive thanks to the @SteveMurphy, @RenderBroken, @razen_kain, @creepyncrawly, @4-2ndtwin, @nimper (and all of the i777 community) for the continued encouragement and support.
Speaking of community support, if the builds develop issues I will need your help finding and ironing out solutions. The biggest tip will be to see whether it's affecting the i9100 or n7000, and what they're doing about it.
If the builds start crashing, well that may be the end of SlimKat on the i777.
Happy Flashing
-Cyril
{
"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"
}
Great work.
Sent from my SGH-S959G
Yes, a very proud day!!!
Awesome! A new ROM to add to my collection. Thanks Cyril :thumbup::thumbup:
Sent out from my RR Kit Kat Phone
Thanks for doing this. I will have to try it out in a few days. I just installed SOKP. Gonna give that a few days.
Anything not working that is easy to see such as GPS, etc. I was on PACROM for a long time and it seems to be killing my battery not to mention the GPS doesn't work on it.
Another new play toy. Awesome! Does this come with the correct modem, kernel, etc? Or do we need to flash them separate? I have all those if needed, just curious. Downloaded the ROM and Slim Minimal GAPPS to have something to play with while the kids are at school tomorrow.
Thanks for the port! Looking forward to trying it out!
Sent from my SGH-I777 using XDA Free mobile app
This is awesome man! Just got home from work. I'm all over it
TheGeekyNimrod said:
Another new play toy. Awesome! Does this come with the correct modem, kernel, etc? Or do we need to flash them separate?
Click to expand...
Click to collapse
Modem and kernel are included, although the latter will be stock.
RenderBroken said:
...I don't think NFC will work properly with KK. There are some security checks in place by the software that our version of NFC wont work with from what I have gathered. SO you may be spinning your wheels for something that won't even work. afaik Keep me updated with your progress though!
Click to expand...
Click to collapse
cyril279 said:
I777 on KK is perhaps NFC challenged, but definitely capable. I use it regularly via superbeam to transfer files in between my wife's i777 and mine...
Click to expand...
Click to collapse
...I777 on KK isn't even NFC challenged apparently. AOSP bluetooth nfc transfer works as designed on slimkat for i777.
oh man thats a happy day i was waiting for something exciting and here you are love your amazing work, gonna download and try it now
cyril279 said:
...I777 on KK isn't even NFC challenged apparently. AOSP bluetooth nfc transfer works as designed on slimkat for i777.
Click to expand...
Click to collapse
I think he's talking about using your phone's NFC to tap & pay at the gas station or other places.
SteveMurphy said:
Modem and kernel are included, although the latter will be stock.
Click to expand...
Click to collapse
Cool deal. Getting ready to flash it now. I'll give it a shot with stock kernel before deciding to use Render's for now. I like Slim builds so I'm pretty stoked to be giving SlimKat a try. Thanks again!
So Far So Good
Just flashed this a little while ago. Had a few issues with root permissions to begin with, even after going to Settings>Developer Options>Root access, but it's fixed now. Install SuperSU and selected to update the binaries, after reboot all was well and was able to uninstall SuperSU to use the built in superuser. Not sure what happened that caused all that, but it's whatever at this point :silly:
So far, I haven't noticed and issues. Even the APN settings for ST worked right out of the box. All my apps are restored and seem to be playing nicely. There were a few (Fast Burst Camera comes to mind) that didn't want to work even with Dalvic on other KK builds for the triple7 but it's all working here. Great job on this build sir. If I notice any bugs or anything that sticks out I'll let you know, but so far this is great. Keep up the good work!
an extra shout out...
I also owe @nimper thanks for quietly nudging me in the right directions several times, even beyond xda, when it's apparent that I'm operating at or beyond the capacity of my Android knowlege base.
cyril279 said:
I'm ahead of myself...
Click to expand...
Click to collapse
I don't have it installed now and it's working fine. I've had this happen in other roms too dating back to 4.2.2. Must be something I'm doing with wipes or other things I flash with roms. Either way, it's resolved and working great. Good on the battery life so far too. I usually notice immediate huge drain when first installing a KK rom. This one is remarkably better IMO.
Now to get down to it and put it through the ringer :highfive:
cyril279 said:
I also owe @nimper thanks for quietly nudging me in the right directions several times, even beyond xda, when it's apparent that I'm operating at or beyond the capacity of my Android knowlege base.
Click to expand...
Click to collapse
Happy to help! I probably don't know any more than you do other than what I pick up from reading the forums and posts from the developers, but every little bit helps.
I ran the build, but I'm still just a messenger.
I certainly can't take any credit for how fluidly this firmware works. The Slim team is definitely crossing t's and dotting i's. There are several apps, (AOSP and third-party) that haven't worked correctly on other KK builds, that work flawlessly on SLIM.
TheGeekyNimrod said:
...All my apps are restored and seem to be playing nicely. There were a few (Fast Burst Camera comes to mind) that didn't want to work even with Dalvic on other KK builds for the triple7 but it's all working here. Great job on this build sir. If I notice any bugs or anything that sticks out I'll let you know, but so far this is great. Keep up the good work!
Click to expand...
Click to collapse
cyril279 said:
I certainly can't take any credit for how fluidly this firmware works. The Slim team is definitely crossing t's and dotting i's. There are several apps, (AOSP and third-party) that haven't worked correctly on other KK builds, that work flawlessly on SLIM.
Click to expand...
Click to collapse
I hear sabermod is supposed to make it faster. Don't know how true that is but i see devs advertising that a lot
Edit: oh and BTW, running flawless all day today. Stock kernel getting great battery life considering i just flashed it last night
{
"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"
}
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?
{
"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
Hello everyone. First off all, I would like to say thank you to all the devs who are doing such a great job in making various roms and giving us the opportunity to experience a vast android world. Now, I know that many of the noob users like me are really confused about installing a custom rom. There are a number of good roms for kenzo now. I'm creating this thread to help me choose the best custom rom to install, as well as for all the users.
So, if you are a dev or an experienced users, please suggest me from the following list. Please provide the authentic feature of your chosen rom, or at-least describe why you have chosen it. Also, please provide known major bug list for the latest build of that rom [Like fingerprint error, FM error, FC, random reboot, xposed unavailability etc] . Don't forget to mention if the rom has OTA support.
List of roms-
1. Unofficial CM13 latest build
2. Unofficial Resurrection Remix latest build
3. Official Resurrection Remix latest build
Really looking forward to your reply.
4. MIUI 7.3.9.0 SE port for Kenzo
How to reply to this thread ---
1. Suggest a rom from above list.
2. Give 2 reasons why this rom is the best
3. Describe major known bugs , plus the bugs you have encountered .
Sohan_Saymum said:
Hello everyone. First off all, I would like to say thank you to all the devs who are doing such a great job in making various roms and giving us the opportunity to experience a vast android world. Now, I know that many of the noob users like me are really confused about installing a custom rom. There are a number of good roms for kenzo now. I'm creating this thread to help me choose the best custom rom to install, as well as for all the users.
So, if you are a dev or an experienced users, please suggest me from the following list. Please provide the authentic feature of your chosen rom, or at-least describe why you have chosen it. Also, please provide known major bug list for the latest build of that rom [Like fingerprint error, FM error, FC, random reboot, xposed unavailability etc] . Don't forget to mention if the rom has OTA support.
List of roms-
1. Unofficial CM13 latest build
2. Unofficial Resurrection Remix latest build
3. Official Resurrection Remix latest build
Really looking forward to your reply.
4. MIUI 7.3.9.0 SE port for Kenzo
How to reply to this thread ---
1. Suggest a rom from above list.
2. Give 2 reasons why this rom is the best
3. Describe major known bugs , plus the bugs you have encountered .
Click to expand...
Click to collapse
Cm13 by thestrix. This rom is not on xda but the thread started by banmeifyouwant refers to this. This is build from official cm13 sources, and is most likely going to recieve ota in near feature. There are no major bugs, only some minor which will not hinder daily use.
Resurextion remix is based on cm13 with more customization options, so unless the parent tree is bug free, resurection remix will not be. Check if the rr version is following the official cm tree or some other. If it is following official cm tree, then it is good else the bugs will be more. Personally i prefer cm over rr. You can always use xposed modules to enjoy extra features.
Miui 7.3.9 se, if you want to use miui go for miui8. Other than that i dont know. People usualy flash rom because they dont want to use the stock rom. Cm is way more better than miui or rr.
But these are my opinion, flash what you like. Android is open source, anybody can have what they wish.
Miui 7.3.9
Reasons
1.Really smooth and battery friendly
2. Fingerprint and all other things work
No bug(not even choose location bug)
archit.bajpai.ab said:
Cm13 by thestrix. This rom is not on xda but the thread started by banmeifyouwant refers to this. This is build from official cm13 sources, and is most likely going to recieve ota in near feature. There are no major bugs, only some minor which will not hinder daily use.
Resurextion remix is based on cm13 with more customization options, so unless the parent tree is bug free, resurection remix will not be. Check if the rr version is following the official cm tree or some other. If it is following official cm tree, then it is good else the bugs will be more. Personally i prefer cm over rr. You can always use xposed modules to enjoy extra features.
Miui 7.3.9 se, if you want to use miui go for miui8. Other than that i dont know. People usualy flash rom because they dont want to use the stock rom. Cm is way more better than miui or rr.
But these are my opinion, flash what you like. Android is open source, anybody can have what they wish.
Click to expand...
Click to collapse
Can you provide the detailed link of the mentioned CM13 ?
Build 20160623
1. No battery bug, its fixed.
2. Wifi mac add is fixed.
3. Recents button working perfectly fine.
4. No fc's on anything.
5. Sot at 82% is showing approx 1 day 9 hrs, so that like more than 4 hrs of constant usge, i don't know, but its better than 20160619 build. On it, sot around 90% was approx 1 day 4 hrs.
6. Gps working, fast and accurate.
7. Voice recognition working perfectly in every app.
8. Sim working perfectly with data, don't know about dual sim as i have only one. Don't know about lte as i am on 3g.
9. Fingerprint is very accurate and fast.
10. IR blaster working fine.
11. Pretty much everything seems fine.
Bugs:
1. Cannot set led notification to blink on custom values like red. It works only when its set on always stay one, as soon as it set to blink, all the colours go haywire.
2. Bluetooth add is still wrong.
3. Headphones working fine, but there is still not sign to show whether its connected or not. Even the volume panel does not show that warning, you know, do not set it at high or you'll go deaf warning.
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
Banmeifyouwant and thestrix are also pusing fast charging and many more better feature in the kernel.
Dual sim and lte are working fine.
Sohan_Saymum said:
List of roms-
1. Unofficial CM13 latest build
2. Unofficial Resurrection Remix latest build
3. Official Resurrection Remix latest build
Really looking forward to your reply.
4. MIUI 7.3.9.0 SE port for Kenzo
Click to expand...
Click to collapse
2. Based on M kernel = relocks bootloader (i didn't test that one).
4. Miui is a very nice Rom, stable, very battery friendly, but is has a large issue with ram management (at least on 2gb variant). For me, it closes all the background apps almost instantly.
3. I'm using RR build...20. So far so good.
But before flashing any of the marshmallow roms I strongly recommend you to make an EFS backup.
Anyway, everything seems to work fine.
I didn't test the gps though.
Also fm radio apk is not included.
Why I picked it over CM13?
Awesome list of features.
It has most of the gravitybox features included as stock, which means that you don't have to install xposed (of course you can, xposed works with this rom), which will result in better performance.
Btw, after installing some CM13 based roms, check the cpu governor settings (it may be set at performance as default).
The thing I love in all almost pure android roms for this phone is speed and awesome ram management (compared to miui).
So that is my opinion.
The best way is always testing it by your own.
Sent from Note 3, Xiaomi Redmi Note 3.
mr.loverlover said:
2. Based on M kernel = relocks bootloader (i didn't test that one).
4. Miui is a very nice Rom, stable, very battery friendly, but is has a large issue with ram management (at least on 2gb variant). For me, it closes all the background apps almost instantly.
3. I'm using RR build...20. So far so good.
But before flashing any of the marshmallow roms I strongly recommend you to make an EFS backup.
Anyway, everything seems to work fine.
I didn't test the gps though.
Also fm radio apk is not included.
Why I picked it over CM13?
Awesome list of features.
It has most of the gravitybox features included as stock, which means that you don't have to install xposed (of course you can, xposed works with this rom), which will result in better performance.
Btw, after installing some CM13 based roms, check the cpu governor settings (it may be set at performance as default).
The thing I love in all almost pure android roms for this phone is speed and awesome ram management (compared to miui).
So that is my opinion.
The best way is always testing it by your own.
Sent from Note 3, Xiaomi Redmi Note 3.
Click to expand...
Click to collapse
As long as the rr is based on the official cm tree, its do able. The rr which was based on santhos m sources have more problem, and will not be able to continue future development.
I had never tried any custormer rom. Now i was on stock miui 8 cn dev rom 6.6.28 on my 3gb 32gb rom redmi note 3 pro(officially unlocked) without any problem. All works and never found any bug on it. Battery friendly, smooth and stable.
{
"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"
}
Sent from my Redmi Note 3 using XDA-Developers mobile app