[Defy/Defy+][KitKat]Unofficial OmniROM by struq & Kayant 05/02/2014 [struq]

Kayant · Jan 17, 2014

OmniROM is a free, community built, aftermarket firmware distribution of Android 4.4 (Kitkat), which is designed to increase performance, reliability and features over stock Android for your device. It's also about options, which is the beauty of Android.

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. Linked below is a package that has come from another Android project that restore the Google parts.

This a project in collaboration with @struq

we will both be providing builds when we can.

All the source code for OmniROM is available in the Omni-Defy 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).

Screenshots:
=================
http://imgur.com/NQe3bbN,naGaRCY,C534qGA,8IvTKCR,jXRoZbm,ItZOHp9

Installation Instructions:
=================
First time installing OmniROM, or coming from another ROM:
- Read known issues and FAQs
- Copy GApps and OmniROM ZIPs to your SDCard
- Boot into Recovery
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot) Recommend & Advised as you can and probably will end up with a bootloop
- 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:
=================
http://goo.im/devs/Kayant/Omnirom

Bank's Gapps:
http://xdaforums.com/showthread.php?t=2012857

SuperSU:
http://xdaforums.com/showthread.php?t=1538053

Kayant · Jan 17, 2014

More Installation instructions, tips & Changelog

Installation Instructions coming from stock

If you are coming from stock OS (must be rooted with CWM) or an old build of GB, ICS, or JB then flash "defy_twrp_recovery_2.6.3.0.zip" from the links under downloads.
Wipe /data, /cache, and /system in TWRP or use defy_safewipe.zip (Credits to @YetAnotherForumUser for the wipe script)
Flash ROM
Flash Gapps
Reboot

Bugs

Known bugs on CM11 by Quarx2k [here]
screen recording not working
Tell us more if you find it

Changelog

20140111
initial build
12/01/2014
- fix button brightness
- fix homescreen lag
- fix sms quickreply layout
- fix oversize thumbnail cache
- sync omni
17/01/2014
- Fix reboot to recovery
- sync omni
- merge kernel & device tree changes from Quarx & Blechd0se --> support ro_RO iw_IL langs, fix mute button, fix fm radio, fix mac, fix ap security, fix battery problem, include Blechd0se changes.

ART Runtime
ART is experimental, please do not report any bugs while using it.

The banks gapps supports ART.
Flash the ROM only and boot it up once, switch to ART.
Reboot into the ROM. This bootup takes a long time.
Reboot to recovery and flash ART compatible gapps and any other addon
Reboot

Thanks & Donations

Donations
to Quarx
to Blechd0se

Thanks

To all current/past moto & defy devs including @Epsylon3, @maniac103, @Quarx, @walter79, @czechop, @kabaldan @YetAnotherForumUser @Blechd0se, @SlugZero @TJKV and to anymore I missed sorry

Credit

To the Omni team as always for a great rom and vision
To Google for providing us with awesomeness
To Moto not really

but thanks for the defy it's pretty awesomeness
To Goo for free hosting
To XDA for always me to share my hobby.
To @TJKV & @Jiangyi for shamelessly stealing their OP's

Kayant · Jan 17, 2014

reserved two

struq · Jan 17, 2014

struq builds & test builds

Download of my builds
https://drive.google.com/folderview?id=0BxXRoL-XLSpPbE1XeDhhNUN3VFk&usp=sharing

What's the difference between Kayant's and yours?
Basically, no major difference. We are using almost same source and will post builds if any of us have time so as to bring most updated OmniROM. You can expect jumping between the builds without wipe.

Test builds
Vacancy

Bugs
screen record not working

Last update: 28/04/2014

hotdog125 · Jan 17, 2014

The call delay didn't reduce in my initial test. I'll try disabling suspend and changing settings according to proverb2's post.

EDIT 1 - Disabling suspend seemed to have helped reduce the delay by 2-3 seconds.
EDIT 2 - Setting hispeed_freq and inputboost_freq to 1200Mhz almost eliminated the delay.

EDIT 3 - I repeated the tests (atleast 10-15 times) in different situations (a lot of apps open, lot of apps installed, etc.) and I found that disabling suspend almost completely eliminated the call delay. I have about 200 apps installed, and the delay is a maximum of 2 seconds.

I think that the fix works IF suspend is disabled. Of course, I will wait for other users to test before jumping to conclusions.

Rawwr · Jan 17, 2014

right now on struq's build

testing Kayant's build tonight

struq · Jan 17, 2014

hotdog125 said:
The call delay didn't reduce in my initial test. I'll try disabling suspend and changing settings according to proverb2's post.

EDIT 1 - Disabling suspend seemed to have helped reduce the delay by 2-3 seconds.
EDIT 2 - Setting hispeed_freq and inputboost_freq to 1200Mhz almost eliminated the delay.

Thanks for the report.

To explain a bit, what this fix does is preventing incall ui from being killed from memory. So in continuously repeated tests it won't help as incall ui will not be killed in such a short time even without the fix. But it should help to avoid some extremely long load time of incall ui (I had this when I was on CM11 before) after some heavy memory usage.

I'll try the cpu governer tweaks later. Does it impact battery life?

TJKV · Jan 17, 2014

Hot! My defy just discharged almost fully after 10 days, will charge up and test!
I just finished building slimkat too but unfortunately ran out of space when it got to squisher and it aborted :/
Will cleanup and finish it tomorrow.

Kayant · Jan 17, 2014

TJKV said:
Hot! My defy just discharged almost fully after 10 days, will charge up and test!
I just finished building slimkat too but unfortunately ran out of space when it got to squisher and it aborted :/
Will cleanup and finish it tomorrow.

Also looks like you forgot the supporting patches in the build system

---> https://github.com/Quarx2k/android_build/commits/cm-11.0

If that doesn't work just revert those patches. We did for omni as the build system is different to CM's and it was causing problems in recovery.

hotdog125 · Jan 17, 2014

struq said:
Thanks for the report.

To explain a bit, what this fix does is preventing incall ui from being killed from memory. So in continuously repeated tests it won't help as incall ui will not be killed in such a short time even without the fix. But it should help to avoid some extremely long load time of incall ui (I had this when I was on CM11 before) after some heavy memory usage.

I'll try the cpu governer tweaks later. Does it impact battery life?

Thanks for the explanation. I waited for about 30-40 minutes before calling again just to check. There was hardly any delay, the screen lit up almost immediately. The tweaks didn't affect battery life much for me. And the fix seems to be working very well only with suspend disabled for some reason.

Sent from my Nexus 7 using Tapatalk

Rawwr · Jan 17, 2014

found a strange bug

clock in the status bar sometimes disappear :cyclops:

TJKV · Jan 17, 2014

Kayant said:
Also looks like you forgot the supporting patches in the build system ---> https://github.com/Quarx2k/android_build/commits/cm-11.0

If that doesn't work just revert those patches. We did for omni as the build system is different to CM's and it was causing problems in recovery.

Hehe yes I just reverted them in device repo

If slim guys take those patches from cm by any chance I'll undo it...just want to avoid maintaining more forks than I need to.

DragonautMk · Jan 17, 2014

What's specially from this rom?

Ermh... the screen is from Nexus 4 with 3.4 kernel xD Please,add more screen of this Rom

level_666 · Jan 17, 2014

DragonautMk said:
What's specially from this rom?
Ermh... the screen is from Nexus 4 with 3.4 kernel xD Please,add more screen of this Rom

Search before asking.
http://omnirom.org/

And it doesn't matter if the screenshots are from mako, it's the same screens that you will get, since it's the same rom. It's like taking and sshot from a Lenovo pc or HP, the system will be the same (assuming it has w8).

imharshadpatel · Jan 17, 2014

otg bug

@struq using ur experimental build 16/1 in my mb526. I used usb stick with otg. it worked fine. but after that my phone was not recognising charger. a manual reboot solved it. i know the usb otg is bugged but such problem never happed with me in cm11.
the good thing is , the rom is working good. there is some call delay. setting min c.p.u. frequency to 600mhz gave me some relief.

Edit: screen recording not working. missing defy parts. @struq and @Kayant Can i extract defy parts apk from any rom liks SK or PA and then use it. because defy parts specially baseband switcher is must for me. or we can have defy parts in setting like cm11 in future builds.

NeoPreacher · Jan 17, 2014

maybe I'm a bit blind, but where is the safe headset volume preference? or isn't it included yet?

Kayant · Jan 17, 2014

imharshadpatel said:
@struq using ur experimental build 16/1 in my mb526. I used usb stick with otg. it worked fine. but after that my phone was not recognising charger. a manual reboot solved it. i know the usb otg is bugged but such problem never happed with me in cm11.
the good thing is , the rom is working good. there is some call delay. setting min c.p.u. frequency to 600mhz gave me some relief.

Edit: screen recording not working. missing defy parts. @struq and @Kayant Can i extract defy parts apk from any rom liks SK or PA and then use it. because defy parts specially baseband switcher is must for me. or we can have defy parts in setting like cm11 in future builds.

Defy parts is in the launcher in Omni.

struq · Jan 18, 2014

hotdog125 said:
Thanks for the explanation. I waited for about 30-40 minutes before calling again just to check. There was hardly any delay, the screen lit up almost immediately. The tweaks didn't affect battery life much for me. And the fix seems to be working very well only with suspend disabled for some reason.

Sent from my Nexus 7 using Tapatalk

disabling suspend seems to give me battery drain overnight, will try again.

imharshadpatel said:
@struq using ur experimental build 16/1 in my mb526. I used usb stick with otg. it worked fine. but after that my phone was not recognising charger. a manual reboot solved it. i know the usb otg is bugged but such problem never happed with me in cm11.
the good thing is , the rom is working good. there is some call delay. setting min c.p.u. frequency to 600mhz gave me some relief.

Edit: screen recording not working. missing defy parts. @struq and @Kayant Can i extract defy parts apk from any rom liks SK or PA and then use it. because defy parts specially baseband switcher is must for me. or we can have defy parts in setting like cm11 in future builds.

Sorry, I don't have a otg cable so i can't debug. @Kayant can you do this?
Will look into the screen recording thing.

NeoPreacher said:
maybe I'm a bit blind, but where is the safe headset volume preference? or isn't it included yet?

not found = not included

In my test sceranio, ZRAM makes the whole system less responsive and reboot more, although it does give more free mem. I want to disable ZRAM by default next build. What do you think? @Kayant

Kayant · Jan 18, 2014

struq said:
disabling suspend seems to give me battery drain overnight, will try again.

Sorry, I don't have a otg cable so i can't debug. @Kayant can you do this?
Will look into the screen recording thing.

Nope I don't have a otg cable.

struq said:
In my test sceranio, ZRAM makes the whole system less responsive and reboot more, although it does give more free mem. I want to disable ZRAM by default next build. What do you think? @Kayant

Are you talking about this?
https://github.com/Quarx2k/android_...mmit/2a2674f2360d716baf06e96f76168b6f925a5f4b

Rawwr · Jan 18, 2014

Bugs i noticed in kayant's build,
Camera isnt working, it shows cant connect to camera (green lens)

Battery behavior is weird, when i put it on charge it was on 67℅
Rebooted the phone it showed charged
Then i rebooted again it was back to 68%

Volume keys didnt changed the volume ( although vol2wake worked) rebooted and it worked,

Clock disappears sometimes from status bar and comes back again,

Pls fix the camera bug

Sent from my MB526 using XDA Premium 4 mobile app

[Defy/Defy+][KitKat]Unofficial OmniROM by struq & Kayant 05/02/2014 [struq]

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts