[KK 4.4.2][ROM]Mackay OMNI ROM (27-Feb-2014)

Status
Not open for further replies.
Search This thread

tsatomas

Senior Member
Feb 5, 2012
2,289
903
Athens
Hi,I have been using the Mackay Omni ROM on my i9000 from the past few days.Overall,the performance is really good but I have encountered two issues.
1) Whenever I try to push the Maximum core clock to 1300-1400 MHz,The phone reboots on its own after a few seconds.Is it because I am using SmartAssv2 as the Governor?
2) I don't get a very good battery life on my phone
I hope you guys can help me out to sort this :)

No you need to use nstools and raise the init voltages for those steps by 25-50 volts
Sent from my One S

Overclocking high is a good reason for instability and battery drain.
We know that every sgs is not capable for high oc as other. You have to find yours better config. You can use voltage for this, included in settings/performance (expand or tab it to see all options), or you can try to increase min/max oc and/or use different governors scheduler.
I prefer min200 max1200 ondemandx/sioplus. If you use volt take it slowly!:cool:

Sent from my GT-P3110 using xda app-developers app
 
  • Like
Reactions: Samurai05

cannondaleV2000

Senior Member
Mar 24, 2013
1,099
963
Overclocking high is a good reason for instability and battery drain.
We know that every sgs is not capable for high oc as other. You have to find yours better config. You can use voltage for this, included in settings/performance (expand or tab it to see all options), or you can try to increase min/max oc and/or use different governors scheduler.
I prefer min200 max1200 ondemandx/sioplus. If you use volt take it slowly!:cool:

Sent from my GT-P3110 using xda app-developers app

Stop trying to sound smart. Overclocking is totally stable if you do it right. For example my vibrant ran at 1.5ghx stable my cappy 1.6 and my new one s runs 1.7ghz stable and seriously what I said just increase init voltages for those steps. I personally think they are to low for most devices. Because when I used Mackey on my vibrant and cappy I alwase had to raise them 25 and 50 volts
 

tsatomas

Senior Member
Feb 5, 2012
2,289
903
Athens
Not arguing, I quote you only to add that is no need to use nstools (which is quite old and not so suite to Mackay), settings is good for this, as well as to answer in more details for help :p
Sent from my GT-P3110 using xda app-developers app
 

jaibar

Senior Member
Feb 2, 2011
1,723
1,047
Underwater, no Sh!t
picasaweb.google.com
Stop trying to sound smart. Overclocking is totally stable if you do it right. For example my vibrant ran at 1.5ghx stable my cappy 1.6 and my new one s runs 1.7ghz stable and seriously what I said just increase init voltages for those steps. I personally think they are to low for most devices. Because when I used Mackey on my vibrant and cappy I alwase had to raise them 25 and 50 volts

He is not trying to sound smart, but giving sound advice. Lucky for you, if you managed to get away with 1.5, 1.6 and even 1.7GHz without any issues. But not all i9000 behave the same- maybe it depends on year/month/batch/whatever- some people do manage to use their phone at higher clocking, others start having issues beyond 1200MHz.

And, from all the things that impact the power usage (and thus battery drain), the most significant one is the CPU clock frequency. No matter how wise you think you tweak your settings, running on high frequency means higher drain- by far. Period.

So for most of us, changing voltages and clocking too high usually means more random reboots, freezes+battery pulling and a general feel that we are not doing well for our tired, old phone :cool: As it is, I don't see any reason why strain with clock rating higher than 1.2GHz, the phone is responsive, battery life is just as good as any. For what? just to get some high antutu ranking to boast with?
 
  • Like
Reactions: tsatomas

popic_u

Senior Member
Dec 17, 2010
62
18
When i go to menu and then to downloads it gives me android.process.media has stopped. Tried clear cache, still isn't working, clean install, the same.

Sent from my GT-I9000 using Tapatalk 2
 

Krusade

Senior Member
Sep 19, 2011
254
33
Mumbai
flashed it now, keyboard density is messed up(tried aosp as well as swiftkey) and also play keeps on auto updating apps via wifi as the settings get back to default with reboot
 

Attachments

  • Screenshot_2013-12-30-16-17-43.png
    Screenshot_2013-12-30-16-17-43.png
    110.8 KB · Views: 427

fmc000

Senior Member
Jan 18, 2008
3,152
1,373
BLN not working on latest OMNI

@kasper_h: do you have an idea why BLN does not work anymore with the latest version with the ariesparts.apk taken from the previous one? Anything I can try?

Also, even the standard CM-Led doesn't work.
 
Last edited:

tsatomas

Senior Member
Feb 5, 2012
2,289
903
Athens
@kasper_h: do you have an idea why BLN does not work anymore with the latest version with the ariesparts.apk taken from the previous one? Anything I can try?

Also, even the standard CM-Led doesn't work.

Regarding my previous answer please check this: in performance/advanced put backlight timeout value to 5000 , tick apply on reboot AND untick bln notification. Worked for me

Sent from my GT-I9000 using xda app-developers app
 
  • Like
Reactions: fmc000

fmc000

Senior Member
Jan 18, 2008
3,152
1,373
Regarding my previous answer please check this: in performance/advanced put backlight timeout value to 5000 , tick apply on reboot AND untick bln notification. Worked for me

Sent from my GT-I9000 using xda app-developers app

Ahh, the AND part did the trick. So far it seems to work, many thanks!!! Maybe it's conflicting with MacKay Settings? So far this and the fast charge options are the only overlaps that come to my mind.
 

tsatomas

Senior Member
Feb 5, 2012
2,289
903
Athens
Ahh, thee AND part did the trick. So far it seems to work, many thanks!!!

Further to this, I installed bln control app to check and it says that this liblghts does not support bln. So it seems that for bln to work Kasper must have a look. Till then we can use the cm led(untick bln). Glad it worked for you too :)

Sent from my GT-I9000 using xda app-developers app
 

fmc000

Senior Member
Jan 18, 2008
3,152
1,373
Further to this, I installed bln control app to check and it says that this liblghts does not support bln. So it seems that for bln to work Kasper must have a look. Till then we can use the cm led (untick bln). Glad it worked for you too :)

Sent from my GT-I9000 using xda app-developers app

Strange, I have BLN control Pro and it says that all is fine. But I'm even more confused now because all is working now and Performance/Settings/Advanced/Backlight Notification got ticked by itself! To summarize:

* BLN ticked in MacKay Settings
* Notification Lights active in Settings/Display
* Performance/Settings/Advanced/Backlight Timeout set to 5000
* Performance/Settings/Advanced/Backlight Notification ticked
* Performance/Settings/Advanced/Set on Reboot active
 

tsatomas

Senior Member
Feb 5, 2012
2,289
903
Athens
@fmc000 maybe using BLN pro triggered it, or it is the Christmas spirit! I shall try this: enable bln reboot and check the free bln, wait 5min.
Edit. BLN for me does not work in any case(and free app insist that liblights not support). But the ROM notification light works when I tick both the time out(5000)reboot and notification light in display(bln untick). I don't know:confused: but as long as it work somehow, its good.
Sent from my GT-I9000 using xda app-developers app
 
Last edited:

tsatomas

Senior Member
Feb 5, 2012
2,289
903
Athens
What are these options in Mackay Settings:
1. Navbar
2. Touchwake

1. Navbar is navigation bar where you have software buttons similar to hardware(home menu back).
2. Touchwake is an option that allow you to touch and awake the screen for a short time after it is locked.

Sent from my GT-I9000 using xda app-developers app
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 97
    I have been sharing my CM7/CM9/CM10/CM10.1/CM10.2/CM11-based builds for several devices. MackayROM was first based on CyanogenMod sources, but I decided to move over to Omni as base for my ROM.

    About Omni: Omni is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
    Disclaimer: 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.

    If you run into errors, I may not be able to solve it!

    If you know a solution to a problem, either upload it yourself to Gerrit Code Review or contact me through pm.

    The ROM is based on Omni sources with the following changes:
    -Mackay Kernel:
    -Set of cherries picked from gerrit (differing by the day)
    -Some additional patches I did myself to the source code

    Feature request are OK, but remember:
    1. I try to stay close to stock
    2. I will not include additional apps, unless they can be build from source
    3. The time I spend on features depends on how much I like them myself

    Although it is possible to enable ART, this is not advisable:
    -Takes long to convert from Dalvik to ART on first boot
    -Needs more RAM
    -Can cause soft reboots
    But off course, YMMV -> light users may have better luck

    Changelog of 27-Feb-2014
    -Omni codebase of 26-Feb (e.g. new bootanimation :))
    -QS Ribbon is gone

    -Custom kernels can be used only if specific for OmniROM => currently none

    Full changelog of compared to stock Omni
    Omni sources of 31-Jan-2013

    All features compared to stock kernel:
    Separate kernel thread: http://xdaforums.com/showthread.php?t=2532813
    -Mackay kernel:
    -Christopher86's cortex-A8 optimized Linaro toolchain (January version)
    -O3 optimization
    -updated to linux kernel version 3.0.101
    -SLQB memory allocator (default, should be slightly faster)
    -XZ compression of kernel & initramfs
    -396MB RAM
    -SIOplus scheduler
    -Added Lagfree governor
    -ROW scheduler (tweaked, default scheduler)
    -FIOPS scheduler (tweaked)
    -XZ compression of kernel & initramfs
    -many improvements to IO schedulers in general
    -Deadline tuning (thanks to DerTeufel)
    -Ondemand tuned (updated based on code of stratosk)
    -SmartassV2 governor
    -OndemandX governor
    -Interactive governor (updated to android 3.4 code + fixes)
    -Wheatley & Lulzactive governors
    -Conservative tuned
    -Call volume hack (use “Settings>Mackay Settings”* to set volumes)
    -Reduced battery polling interval
    -Fast charge (activate through “Settings>Advanced Settings”* or the QuickCharge toggle in MackayROM)
    -WiFi PM_FAST mode selection (activate using “Settings>Mackay Settings”*)
    -Battery life extender (set through “Settings>Mackay Settings”*)
    -CustomVoltage (set using NSTools)
    -USB OTG support (needs external power supply)
    -1100-1400MHz OC steps
    -Custom kernel splash (Thanks to Malcho)
    -Updated charging logo to match open charger
    -Disabled swap & zram
    -Improve memcopy/memmove
    -Improve the performance of memcpy and memmove
    -Kill task closest in size to memory needed to free
    -LOAD_FREQ (4*HZ+61) avoids loadavg Moire
    -Entropy tweaks: http://lwn.net/Articles/489734/
    -backport CPUIDLE from 3.5
    -arm/crypto: Add optimized AES and SHA1 routines
    -Unaligned CPU access
    -Improvements to RWSEM code
    -Improvements to binder code
    -Improvements to tmpfs
    -Added frandom (much faster random number generator)
    -Updated to lowmemorykiller with PID whitelist (thanks to stratosk)
    -Many parts of the code build as module to reduce effective kernel size
    -Updated wifi driver to 5.90.195.114
    -Updated GPU driver to DDK 1.8@2198402
    -Proportional Rate Reduction for TCP
    -Introduce timer slack controller
    -Zram patched
    -Low RAM switch option (default off)

    To see the additions on top of Omni, check github (additional patches are always shown on top):
    Settings
    OmniGears
    Frameworks

    Fresh install:
    Can be flashed on top of any ROM:
    -Do a factory reset
    -Wipe /system
    -Flash ROM
    -Boot the phone
    -Reboot recovery
    -Flash gapps & superSU
    -Reboot your phone

    Update:
    -Flash ROM
    -Reboot your phone
    (no wipes or other things needed, just flash & reboot)

    -Custom kernels can be used only if specific for OmniROM => currently none

    Credits:
    -Omni team for in incredible job on the ROM base
    -OmNomteam: great group of Omni fanatics
    -teamhacksung/pawitp for making KitKat work on our ancient phone
    -stratosk/DerTeufel/Mialwe for the inspiration I got from their kernels
    -rootax for providing a high-speed server for high quality downloads
    -Malcho for his kernel splash & bootanimation

    Downloads:
    Rootaxbox

    For those who want to theme it even further, Bejda made a Mackay splash screen!
    http://xdaforums.com/showthread.php?t=2214468

    XDA:DevDB Information
    [KK 4.4.2][ROM]Mackay OMNI ROM, a ROM for the Samsung Galaxy S I9000

    Contributors
    kasper_h
    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 3.0.x
    Based On: Omni

    Version Information
    Status: Beta

    Created 2013-12-15
    Last Updated 2014-02-27
    28
    Changelog of 17-Dec-2013
    -Based on omni source of 17-Dec-2013
    -Google backup/restore in ROM fixes
    -Fixed the Mackay Settings FC (so you can enable navbar, change colour, change vibration intensity, to name a few request of the last days :))
    -CM calculator with more features
    -CM Exchange & Email - my corporate Exchange account works fine for me now
    -Many minor patches merged (see my github for details)

    Downloads:
    XDAfileserver
    Rootaxbox
    23
    I don't have the space issue myself on Omni. If someone who has this issue can send of logcat when the problem occurs, I may be able to find the solution. Anyway, I have an updated version:

    Changelog of 15-Feb-2014
    -Omni codebase of 15-Feb
    -New kernel (no more CMA, zram & KSM updates, fix for colour problems)
    -Fixed front camera FC issue
    -Updates to ActiveDisplay & Lockscreen notifications

    Downloads:
    Rootaxbox
    22
    Changelog of 21-Dec-2013
    -Based on omni source of 21-Dec-2013
    -Fixes to PIN screen
    -Added quick pulldown for QS back
    -Added back button kills app back in development settings (could already be programmed through settings>buttons, but this should be a better solution)
    -Updates to DSP Manager
    -New volume panel colours (to match kitkat)
    -Improved some animations

    Downloads:
    XDAfileserver
    Rootaxbox
    20
    Changelog of 28-Dec-2013
    -Omni codebase of 27-Dec
    -Added a basic QS toggle modification patch (based on AOSPA -> press the new edit button above the toggles to modify the QS toggle screen -> press to remove/add / hold to move around)
    -Some ActiveDisplay fixes
    -Some Camera fixes

    Downloads:
    XDAfileserver
    Rootaxbox