[KERNEL][Singularity-5.4][SKA-APK-12.1][SaberMod-6.0][Graphite -03][3-08]

Is everyone enjoying the kernel?

  • YES

    Votes: 22 91.7%
  • NO

    Votes: 2 8.3%

  • Total voters
    24
  • Poll closed .
Status
Not open for further replies.
Search This thread

apophis9283

Forum Moderator / Recognized Developer
Staff member
I just increased the voltages on my s4 though and then it stopped happening. Same with the Nexus 6. I know its voltage related but maybe not kernel specific. TBH I really can't be too sure of anything but I just wanted to chime in that bug.

---------- Post added at 05:58 PM ---------- Previous post was at 05:22 PM ----------

Hey @apophis9283 is it a good idea to have the GPU governor set to performance while CPU governor is lionfish@3ghz overclock? Im a hybrid performance with extra battery savings and so far I'm contemplating modifying GPU settings

Sent from my Nexus 6 using Tapatalk

I would not use performance, use simple_ondemand and use simple tuneables to make it ramp up faster and if you want to stay at those frequencies longer before it ramps down
 
  • Like
Reactions: baboomerang

baboomerang

Senior Member
Aug 13, 2014
76
22
New York
I will no longer support the 3.09 frequency. The max frequency will be 3.03

What happened? Is it stable for anyone? I successfully got 3,033 MHz perfectly stable by overvolting the frequencies 2,256 MHz-3,033 MHz by +45mV now it works flawlessly without crashes
And the rest of the frequencies are slightly overvolted by +10mV. I am afraid to try 3,091 MHz. Which I think I couldn't get working at all ever since HSB.
TL;DR: So whats the reason behind removing 3,091mhz?
 

apophis9283

Forum Moderator / Recognized Developer
Staff member
What happened? Is it stable for anyone? I successfully got 3,033 MHz perfectly stable by overvolting the frequencies 2,256 MHz-3,033 MHz by +45mV now it works flawlessly without crashes
And the rest of the frequencies are slightly overvolted by +10mV. I am afraid to try 3,091 MHz. Which I think I couldn't get working at all ever since HSB.
TL;DR: So whats the reason behind removing 3,091mhz?

No just logically it doesnt make sense. I mean 3.03 to 3.09. Its unnecessary
 
Y

Yoinx

Guest
Gee no posts all day. The suspense is killing me

Straight Shooter
Oh, and just so that the suspense is lifted. What I'm working on is trying to setup a static uci in the ramdisk, and storing the profiles and such for synapse in the synapse app directory. That way they'll be baked up and restored with synapse when using titanium backup.

Unfortunately, this is taking a lot longer than I expected. It works for most everything so far except the apply in boot. That's causing hard reboot loops that I'm trying to narrow down right now... Basically blindly because synapse's boot service doesn't log anything. So logcat and kmsg aren't helping.

However on the positive side... The reboots mean that it is actually trying to set the values on boot... Just that something is messed up somewhere.

Unfortunately, it's turning into a huge time sink so I'm not sure when it'll be ready for everybody. I'm just hoping that it fixed the issue of synapse applying it's settings.

If nothing else, we won't have to deal with modifying ukm anymore. I could add a tunable to a driver in like half an hour, then spend hours trying to get ukm to accept it correctly. It started to get old.

Unfortunately, synapse applies about 300 actions on boot... And I'm going to have to hack its database apart to systematically figure out which action doesn't want to work with its boot service.

Sent from my Nexus 6 using Tapatalk
 
Last edited:

str8str

Senior Member
Apr 1, 2013
3,922
1,046
Kitchener Ontario
Oh, and just so that the suspense is lifted. What I'm working on is trying to setup a static uci in the ramdisk, and storing the profiles and such for synapse in the synapse app directory. That way they'll be baked up and restored with synapse when using titanium backup.

Unfortunately, this is taking a lot longer than I expected. It works for most everything so far except the apply in boot. That's causing hard reboot loops that I'm trying to narrow down right now... Basically blindly because synapse's boot service doesn't log anything. So logcat and kmsg aren't helping.

However on the positive side... The reboots mean that it is actually trying to set the values on boot... Just that something is messed up somewhere.

Unfortunately, it's turning into a huge time sink so I'm not sure when it'll be ready for everybody. I'm just hoping that it fixed the issue of synapse applying it's settings.

If nothing else, we won't have to deal with modifying ukm anymore. I could add a tunable to a driver in like half an hour, then spend hours trying to get ukm to accept it correctly. It started to get old.

Unfortunately, synapse applies about 300 actions on boot... And I'm going to have to hack its database apart to systematically figure out which action doesn't want to work with its boot service.

Sent from my Nexus 6 using Tapatalk
OK well I have faith in ya you can do it.

Straight Shooter
 
  • Like
Reactions: blacklight1025

apophis9283

Forum Moderator / Recognized Developer
Staff member
There will be a realease tonight, not including Yoinx's work. I added PMC governor. Stands for Performance May Cry. I dont want to hear anyone complaining about it. Its is meant to be a super battery saver. Let me get all this crap together and ill get it posted

If I forget to add anything to the op let me know.
 
Last edited:
  • Like
Reactions: Mr_S and rpsgrayfox

baboomerang

Senior Member
Aug 13, 2014
76
22
New York
Oh, and just so that the suspense is lifted. What I'm working on is trying to setup a static uci in the ramdisk, and storing the profiles and such for synapse in the synapse app directory. That way they'll be baked up and restored with synapse when using titanium backup.

Unfortunately, this is taking a lot longer than I expected. It works for most everything so far except the apply in boot. That's causing hard reboot loops that I'm trying to narrow down right now... Basically blindly because synapse's boot service doesn't log anything. So logcat and kmsg aren't helping.

However on the positive side... The reboots mean that it is actually trying to set the values on boot... Just that something is messed up somewhere.

Unfortunately, it's turning into a huge time sink so I'm not sure when it'll be ready for everybody. I'm just hoping that it fixed the issue of synapse applying it's settings.

If nothing else, we won't have to deal with modifying ukm anymore. I could add a tunable to a driver in like half an hour, then spend hours trying to get ukm to accept it correctly. It started to get old.

Unfortunately, synapse applies about 300 actions on boot... And I'm going to have to hack its database apart to systematically figure out which action doesn't want to work with its boot service.

Sent from my Nexus 6 using Tapatalk

Give me your paypal donation link. I will THROW MONEY AT YOU to add your fix to synapse.
 
Y

Yoinx

Guest
Give me your paypal donation link. I will THROW MONEY AT YOU to add your fix to synapse.

I'd never turn away money.

However, the prospect of money wouldn't affect me fixing it or not. I'm determined to fix it regardless.

Right now though it's really beating me pretty good. Things that should work don't... and logical troubleshooting isn't really yielding the results I want.
 
Last edited:

apophis9283

Forum Moderator / Recognized Developer
Staff member
I'd never turn away money.

However, the prospect of money wouldn't affect me fixing it or not. I'm determined to fix it regardless.

Right now though it's really beating me pretty good. Things that should work don't... and logical troubleshooting isn't really yielding the results I want.

Dont let him fool you. He loves it when it rains money.
 

Mr_S

Senior Member
Dec 21, 2012
1,632
491
OT

Great work @Apophis and @Yoinx... You have worked hard on this kernel for time now...I am going to test next build....

Sent from my Nexus 6 using Tapatalk
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 85
    28hool3.jpg


    I PRESENT TO YOU, SINGULARITY KERNEL:)

    (Team Singularity consists of apophis9283 and Yoinx)

    ##JUST TO PROTECT MY A**##
    THIS KERNEL COMES WITH NO WARRANTY. I WILL NOT BE HELD LIABLE FOR ANY DAMAGE TO YOUR PHONE OR GET FIRED FROM WORK BECAUSE THE ALARM DIDNT GO OFF. BY DOWNLOADING THIS KERNEL YOU TAKE ALL THE RESPONSIBILITY THAT COMES WITH IT.

    ##### TO CONTROL THIS KERNEL AND ALL ITS FEATURES WE HAVE A MODIFIED KERNEL AUDITOR FOR YOUR ENJOYMENT #####
    ##### MORE INFO AND DOWNLOADS IN POST 2 #####

    #####FEATURES#####

    -WORKS ON BOTH AOSP AND CM BASED ROMS

    #COOKED WITH#
    -SABERMOD-6.0-CORTEX-A15

    -03 Opitimizations

    -GRAPHITE

    -LZ4 Compression

    -F2FS SUPPORT

    -NO FORCE ENCRYPTION

    -PERMISSIVE

    -CHOOSE BETWEEN BCL_ENABLED/BCL_DISABLED--(Must be using our Kernel Auditor from post 2)

    What is BCL?
    BCL polls the battery monitor system for various values such as voltage, current and temperature through the battery. This driver is meant to help prevent possible reboots, but with it removed on several devices we have seen no issues. The way it prevents reboots is by setting thresholds and when the threshold is passed or tripped, it will throttle or unplug cores.

    #MSM_LIMTER#
    (Complete control over your CPU)
    (Per core control over min/max)
    (You can set governors for each core)
    (MIN CPU IS 223MHz - MAX CPU IS 3096MHz)

    #####OUR FREQUENCY TABLE#####
    < 35800 35800 762 >,
    < 98300 98300 762 >,
    < 223200 223200 762 >,
    < 300000 300000 1144 >,
    < 345600 345600 1144 >,
    < 422400 422400 2288 >,
    < 499200 422400 2288 >,
    < 576000 499200 3051 >,
    < 652800 499200 3051 >,
    < 729600 576000 5996 >,
    < 806400 576000 5996 >,
    < 883200 576000 5996 >,
    < 960000 960000 8056 >,
    < 1036800 1036800 8056 >,
    < 1113600 1036800 8056 >,
    < 1190400 1036800 8056 >,
    < 1267200 1036800 10101 >,
    < 1344000 1036800 10101 >,
    < 1420800 1036800 10101 >,
    < 1497600 1036800 10101 >,
    < 1574400 1574400 12145 >,
    < 1651200 1574400 12145 >,
    < 1728000 1651200 12145 >,
    < 1804800 1651200 12145 >,
    < 1881600 1651200 16250 >,
    < 1958400 1728000 16250 >,
    < 2035200 1728000 16250 >,
    < 2112000 1728000 16250 >,
    < 2188800 1728000 16250 >,
    < 2265600 1728000 16250 >,
    < 2342400 1728000 16250 >,
    < 2419200 1728000 16250 >,
    < 2496000 1728000 16250 >,
    < 2572800 1728000 16250 >,
    < 2649600 1728000 16250 >,
    < 2726400 1728000 16250 >,
    < 2803200 1728000 16250 >,
    < 2880000 1728000 16250 >,
    < 2956800 1728000 16250 >,
    < 3033600 1728000 16250 >,


    #GOVERNORS
    -ABYSSPLUGV2
    -ADAPTIVE
    -ALUCARD
    -BARRY_ALLEN
    -BIOSHOCK
    -BLU_ACTIVE
    -CONSERVATIVE
    -CONSERVATIVEX
    -DANCEDANCE--(DEFAULT GOVERNOR)
    -DARKNESS
    -DESPAIR
    -DYNAMIC_INTERACTIVE
    -ELEMENTALX
    -HYPERX
    -INTELLIACTIVE
    -INTERACTIVE
    -INTERACTIVE_PRO
    -LIONHEART
    -LIONFISH
    -LULZACTIVE
    -MYTHX_PLUG
    -NIGHTMARE
    -ONDEMAND
    -ONDEMAND_EPS
    -ONDEMANDPLUS
    -PERFORMANCE
    -POWERSAVE
    -PEGASUSQ
    -PMC --(PERFORMANCE MAY CRY) Its a real battery saver but lag is possible
    -RAGINGMOLASSES
    -SMARTMAX
    -SMARTASSV2
    -SMARTASSH3
    -SMARTMAX_EPS
    -UMBRELLA_CORE
    -WAVE
    -WHEATLEY
    -XPERIENCE
    -ZZMOOVE --(PROFILE 6 IS DEFAULT)

    #MPDECISION REPLACEMENT
    ZEN_DECISION--(DEFAULT)

    #HOTPLUGS
    -ALUCARD_HOTPLUG
    -AUTOSMP
    -BLU_PLUG
    -INTELLI-PLUG_5.0
    -MAKO
    -MSM_SLEEPER
    -BRICKED_HOTPLUG


    #THERMAL
    FRANCO THERMAL (YOINX ADDITIVES)

    #I/O SCHEDULERS
    -BFQ
    -CFQ--(DEFAULT)
    -DEADLINE
    -FIOPS
    -FIFO
    -NOOP
    -ROW
    -SIOPLUS
    -TRIPNDROID
    -VR
    -ZEN

    #GPU
    -UC/OC (MIN 100MHz/MAX 700MHz)

    #####OUR GPU FREQUENCY TABLE#####
    IDLE AT 25MHz
    100MHz
    150MHz
    220 MHz
    300MHz
    389MHz
    430MHz
    500MHz
    600MHZ
    700MHz

    #GPU GOVERNORS
    -CACHE_HWMON
    -CPUBW_HWMON
    -MSM-ADRENO-TZ
    -USERSPACE
    -POWERSAVE
    -PERFORMANCE
    -SIMPLE_ONDEMAND
    -MSM_CPUFREQ

    #GOVERNOR TUNEABLES
    -ADRENO_IDLER TUNABLES
    -SIMPLE_ONDEMAND TUNABLES

    #GPU SPECIAL ITEMS
    -A BUTTON YOU CAN SELECT TO INCREASE PERFORMANCE FOR GAMING

    #TCP CONGESTION CONTROL
    -HTCP
    -RENO
    -BIC
    -CDG
    -CUBIC
    -WESTWOOD--(DEFAULT)
    -HIGHSPEED
    -HYBLA
    -VEGAS
    -VENO
    -SCALABLE
    -LP
    -YEAH
    -ILLINOIS
    -SOCIOPATH

    ###OTHER FEATURES###

    -CPU BOOST DRIVER

    -ADD RANDOM

    -DISABLE I/O STATS

    -I/O TUNABLES

    -ROTATIONAL

    -NR REQUESTS

    -UKSM

    -LOW MEMORY KILLER

    -WAKE FEATURES- WITH TUNEABLES. Huge thanks to Yoinx.

    -KEXEC

    -READ AHEAD SIZE IS 1536 (I would leave it at that)

    -I/O TUNABLES

    -KCAL

    -Z-RAM

    -VIRTUAL MEMORY

    -MEMORY TWEAKS

    -POWER SUSPEND OPTIONS

    -USE FB NOTIFIERS

    -USB FASTCHARGE

    -TONS OF WAKELOCKS YOU CAN CONTROL

    -ADAPTIVE LMK

    -LMK PROFILE

    -WIFI SCAN INTERVAL

    -VM HEAPSIZE

    -ALLOW PURGING OF ASSETS

    -GENTLE FAIR SLEEPERS

    -ARCH POWER

    -USING MM WIFI DRVERS WITH EXTRA COMMITS THAT HOPEFULLY MAKE IT ACT BETTER


    ###INFO###

    ##### FOR INFO ON GOVERNORS AND HOTPLUGS LOOK AT POST 3. IT HAS A PAGE THAT WILL INFORM YOU. #####


    #####SINGULARITY-UKM#####
    We have the UKM options to match the features we have in the kernel. As well as Live stats. Included are (If its a temperature its in both Celcius and Fahrenheit)

    -CPU PVS/SPEED Level
    -BATTERY TEMPERATURE
    -CPU FREQUENCY
    -CPU TEMPERATURE
    -GPU FREQUENCY
    -GPU TEMP
    -MEMORY (TOTAL AND FREE)
    -UPTIME
    -UNUSED STATES
    -TIME IN STATES
    -WAKELOCKS

    ###SHOW YOUR SUPPORT###

    Flashable Zip that makes your boot logo say SIngularity

    They are attachments at the bottom of the OP

    Use SINGULARITY_BOOTLOADER_SPLASH.zip to flash our boot logo

    142zujs.png


    Use STOCK_BOOTLOADER_SPLASH.zip to go back to stock boot logo


    ### CHANGELOG/SOURCE ###

    https://github.com/Team-Singularity/Singularity/commits/apophis



    #####KERNEL DOWNLOAD#####

    ##### TO CONTROL THIS KERNEL AND ALL ITS FEATURES WE HAVE A MODIFIED KERNEL AUDITOR FOR YOUR ENJOYMENT #####
    ##### MORE INFO AND DOWNLOADS IN POST 2 #####


    Mod Edit


    #####CREDITS#####
    YOINX FOR SKA, THE APP TO CONTROL OUR KERNEL
    FOR HELPING OUT HELLSGOD
    DESPAIR FACTOR FOR THE INFO ON BCL
    FOR SINGULARITY BOOT LOGO DROIDPHILEV
    FOR ALL THE WORK FROM OTHERS I USE
    THANKS TO THEM ALL
    22
    To figure out what combo of settings are good for battery/performance you can go to this site. It even breaks them down into what they are and how they act.

    http://androidmodguide.blogspot.com/p/blog-page.html
    18
    Y
    Yoinx
    Singularity - Kernel Adiutor v12

    So, @apophis9283 gave me the second post. Yeah, apparently he knows "knows people in high places"? So he says anyway.

    Anyway. Given the huge issues we were having with UKM and Synapse, we're now just going to be heavily modifying Kernel Adiutor to have the options that we want. However, this is my first delve into app development... I've always been more of a kernel guy (C mostly).

    Keep in mind that this is a Work In Progress. Some features have not been included yet, others are broken from upstream (automatic downloading and flashing of zips). Hopefully everything will be added/fixed quickly, but I offer no ETA's.

    *Important Note: Many Roms (especially CM based) have a long delay in the amount of time that the BOOT_COMPLETE broadcast takes before it's sent. Most roms include, as part of init, default values that get set on boot complete. This interferes with this app setting it's values on boot. To work-around this, increase the delay for setting values on boot to something around 20 seconds. On AOSP based roms this doesn't appear to be an issue.

    Without Further Ado,
    Here's the download link for V12

    Also, the link to our Github for legal reasons ;)
    The Github commit history will also serve as a changelog. I'll try to keep the commit messages clear so that it's obvious what's added/changed. I'll also do my best to add markers in the form of empty commits in the history so that it's easy to see what's been changed since the last version that you installed.

    These apks will be signed by me, so you will not be able to update them from the playstore.


    Our github shows where it was forked from, but just as an additional courtesy and to render proper credits. The original github is here none of this would be possible with Grarak's work. While the about page in our app is modified (to help reduce erroneous info being submitted to his github and g+) the rate app and donate popups still point to his links so that he can get proper respects.

    Eventually, I may submit my changes to him as pull requests... But I'm unsure the coding is clean enough to really do so.


    *edit*
    Starting with V4, I've added support for High Brightness Mode intents to toggle the mode from apps like tasker.

    Toggle on: com.singularity.kerneladiutor.action.HBM_ON
    Toggle off: com.singularity.kerneladiutor.action.HBM_OFF
    9
    I don't think it would be impossible. However, it's probably going to be a good bit of work to get up and going. I wouldn't expect it too quick.

    Ill track everything down tomorrow. Start work on it
    9
    OK, very exciting day for Singularity, Kernel Version 3.6 is live in the OP. If you look at post 2 you will see a modified Kernel Auditor that has our features available. HUGE HUGE THANKS TO YOINX. AMAZING WORK. Check it out. No more UKM and Synapse not holding settings after a reboot. He worked really hard on it and it is a work in progress. Enjoy the hell out of it.

    Thank the hell out of post 2. He deserves it

    Checkout the downloads section, not working yet but you get the idea


    IF YOU HAVE KERNEL AUDITOR ALREADY INSTALLED YOU WILL NEED TO DELETE THAT ONE FIRST THEN INSTALL OURS

    Also the link for the kernel in the op is now a direct link

    BCL is now togglable