[ROM][OFFICIAL][Flo/Deb]OmniROM 4.4 Nightly Builds

Search This thread

dre1187

Senior Member
Apr 14, 2011
506
617
Toronto
omnirom_logo-big_layout_transparent-250px-150x150.png

OmniROM is a free, community built, aftermarket firmware distribution of Android by @XpLoDWilD, @Chainfire, @Dees_Troy & Team. OmniROM is designed to increase performance, reliability and features over stock Android for your device as well as optimizations and customizations.


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

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

All the source code for OmniROM is available in the OmniROM Github repo.

Homepage:
=================
http://omnirom.org/

Wiki:
=================
http://docs.omnirom.org/Main_Page

Gerrit:
=================
https://gerrit.omnirom.org/

Bugtracker:

=================
http://jira.omnirom.org

IRC:

=================
irc.freenode.net #omnirom

Be Advised:
=================
Root access is not included by default as of yet. Please flash SuperSU for root (See below).
If problems arise from your use of custom kernels, "performance scripts", etc. etc., we can't be responsible.

Installation Instructions:

=================
First time installing OmniROM to your Nexus 7, or coming from another ROM:
- Read known issues and FAQs
- Make sure you're running latest Team Win Recovery Project - WITH SELINUX SUPPORT!
- Copy GApps and OmniROM ZIPs to your SDCard
- Boot into Recovery
- Wipe / Factory Reset
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- Reboot
- Don't restore system data using Titanium Backup!

Upgrading from earlier version of OmniROM:
- Copy the OmniROM ZIP to your SDCard
- Boot into Recovery
- Flash the OmniROM zip from SDCard
- Reboot

Downloads:
=================
Nightly builds:
http://dl.omnirom.org/flo
http://dl.omnirom.org/deb

Gapps: (Using PA's for now)
http://forum.xda-developers.com/showthread.php?t=2397942

SuperSU:
http://forum.xda-developers.com/showthread.php?t=1538053

XDA:DevDB Information
OmniROM, a ROM for the Nexus 7 (2013)

Contributors
dre1187, xplodwild, entropy512
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP

Version Information
Status: Testing

Created 2014-01-27
Last Updated 2014-01-29
 

dre1187

Senior Member
Apr 14, 2011
506
617
Toronto
Gave it a try....

Downloaded deb version
Followed instructions.... stuck on the Google logo

:confused:

Yeh I am pretty sure I know what the problem is will fix shortly. Thanks for the heads up

Edit: new deb build up should fix boot problem

Sent from my Nexus 4 using Tapatalk
 
Last edited:
  • Like
Reactions: Larz2.2

Sleepy!

Senior Member
Jul 20, 2010
4,757
391
Yeh I am pretty sure I know what the problem is will fix shortly. Thanks for the heads up

Edit: new deb build up should fix boot problem

Sent from my Nexus 4 using Tapatalk

So what's the big difference between these and your unofficial builds?
Apart from Open Delta support in the official ones and the linaro toolchain used for the unofficial one, that is...

Sent from my Nexus 7 using Tapatalk
 

dre1187

Senior Member
Apr 14, 2011
506
617
Toronto
So what's the big difference between these and your unofficial builds?
Apart from Open Delta support in the official ones and the linaro toolchain used for the unofficial one, that is...

Sent from my Nexus 7 using Tapatalk

Unofficial is rooted, with cherry picks multi-window, lock screen notifications, dalvik tweaks, etc and bulletproof kernel to add sweep and tap wake functions

Official builds are stable and pure omni with no cherry picks or additional tweaks.

I am debating shutting down the other threads now that this is up.

Sent from my Nexus 4 using Tapatalk
 
Last edited:

duryard

Senior Member
Jun 15, 2010
1,174
209
68
Exeter
www.iscasilver.co.uk
Oh Wow !!!!

I have been waiting to try Omni for a while but the official rather than the un-official.

So glad I found this thread. Its one of the best Roms I have run on my N7. Only beaten by Clean rom but as the dev has moved on and not developing for the N7 now, this Omni is my daily. Thanks a lot dev :highfive::highfive::highfive:
 
  • Like
Reactions: dre1187

Top Liked Posts

  • There are no posts matching your filters.
  • 25
    omnirom_logo-big_layout_transparent-250px-150x150.png

    OmniROM is a free, community built, aftermarket firmware distribution of Android by @XpLoDWilD, @Chainfire, @Dees_Troy & Team. OmniROM is designed to increase performance, reliability and features over stock Android for your device as well as optimizations and customizations.


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

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

    All the source code for OmniROM is available in the OmniROM Github repo.

    Homepage:
    =================
    http://omnirom.org/

    Wiki:
    =================
    http://docs.omnirom.org/Main_Page

    Gerrit:
    =================
    https://gerrit.omnirom.org/

    Bugtracker:

    =================
    http://jira.omnirom.org

    IRC:

    =================
    irc.freenode.net #omnirom

    Be Advised:
    =================
    Root access is not included by default as of yet. Please flash SuperSU for root (See below).
    If problems arise from your use of custom kernels, "performance scripts", etc. etc., we can't be responsible.

    Installation Instructions:

    =================
    First time installing OmniROM to your Nexus 7, or coming from another ROM:
    - Read known issues and FAQs
    - Make sure you're running latest Team Win Recovery Project - WITH SELINUX SUPPORT!
    - Copy GApps and OmniROM ZIPs to your SDCard
    - Boot into Recovery
    - Wipe / Factory Reset
    - Flash OmniROM zip from SDCard
    - Flash GApps zip from SDCard
    - Reboot
    - Don't restore system data using Titanium Backup!

    Upgrading from earlier version of OmniROM:
    - Copy the OmniROM ZIP to your SDCard
    - Boot into Recovery
    - Flash the OmniROM zip from SDCard
    - Reboot

    Downloads:
    =================
    Nightly builds:
    http://dl.omnirom.org/flo
    http://dl.omnirom.org/deb

    Gapps: (Using PA's for now)
    http://forum.xda-developers.com/showthread.php?t=2397942

    SuperSU:
    http://forum.xda-developers.com/showthread.php?t=1538053

    XDA:DevDB Information
    OmniROM, a ROM for the Nexus 7 (2013)

    Contributors
    dre1187, xplodwild, entropy512
    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 3.4.x
    Based On: AOSP

    Version Information
    Status: Testing

    Created 2014-01-27
    Last Updated 2014-01-29
    14
    Would have been useful to mention this to the rest of the team. I saw you PM me on IRC Monday but you have not been on since then for the remainder of the week.

    Are you not on the maintainers mailing list? I haven't seen a response to the email I sent Wednesday evening regarding flo.

    Any build from 7/8 to 7/14 or so should be OK. General issue here is that the proper way to update a device with upstream merges is for the maintainer to do an upstream merge and push the merge as individual commits using Gerrit review bypass. Problem was, Andre didn't have the proper access to do this, and a Gerrit bug caused the process to still fail when pulser THOUGHT he'd given Andre access. As a result, on 7/8, xplodwild reverted the device tree changes until Andre's Gerrit access could be fixed, since the device tree changes break without a kernel update.

    Around 7/14, Andre's gerrit access was fixed (the issues were caused by an annoying Gerrit bug). Andre pushed the kernel update but didn't re-push the matching device tree changes, resulting in a broken configuration again. Then I guess he left on business and wasn't heard from for two weeks. On Monday he PMed me asking me why xplodwild had reverted the changes, and then disappeared from IRC for the remainder of the week.

    I don't mind if people leave for extended periods of time, but in such events, I want to know if a maintainer is going to be gone so we can take care of any issues that arise rather than assuming they're going to fix it. (I've held off on fixing flo myself because I wanted to make sure Andre's gerrit access was sorted, but if he doesn't fix it by tomorrow I can't wait any more...)
    Sorry all for the delay but it has been now fixed and merged. The next nightly for 8/2 will have working WiFi. Again I apologize for the length of time it took to get fixed, I will ensure it won't happen again or give heads up to all.

    Andre
    11
    I will take a look at it tonight and see what the issue is...sorry guys been away on business
    6
    I will take a look at it tonight and see what the issue is...sorry guys been away on business

    Would have been useful to mention this to the rest of the team. I saw you PM me on IRC Monday but you have not been on since then for the remainder of the week.

    Are you not on the maintainers mailing list? I haven't seen a response to the email I sent Wednesday evening regarding flo.

    Any build from 7/8 to 7/14 or so should be OK. General issue here is that the proper way to update a device with upstream merges is for the maintainer to do an upstream merge and push the merge as individual commits using Gerrit review bypass. Problem was, Andre didn't have the proper access to do this, and a Gerrit bug caused the process to still fail when pulser THOUGHT he'd given Andre access. As a result, on 7/8, xplodwild reverted the device tree changes until Andre's Gerrit access could be fixed, since the device tree changes break without a kernel update.

    Around 7/14, Andre's gerrit access was fixed (the issues were caused by an annoying Gerrit bug). Andre pushed the kernel update but didn't re-push the matching device tree changes, resulting in a broken configuration again. Then I guess he left on business and wasn't heard from for two weeks. On Monday he PMed me asking me why xplodwild had reverted the changes, and then disappeared from IRC for the remainder of the week.

    I don't mind if people leave for extended periods of time, but in such events, I want to know if a maintainer is going to be gone so we can take care of any issues that arise rather than assuming they're going to fix it. (I've held off on fixing flo myself because I wanted to make sure Andre's gerrit access was sorted, but if he doesn't fix it by tomorrow I can't wait any more...)