yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] jcrompton:
Hey I have been successful at getting this great kernel up and going on a ROM that was created with a systemless root, of course it required getting rid of the systemless root and reverting back to prior system root ...

Thanks again for this kernel --- it really offers a lot of options

BUT ....... I understand completely if you decide to not try to build so compatible with systemless root (that is your choice since it is your kernel) --- however , systemless root is for sure no longer beta and two of the more commonly used ROMs now come with systemless root ... just sayin
[Nexus 6 Android Development] apophis9283:
I just dont see a point in systemless root.

Its like this. This is how itll turn out. People will love it, like a shiny new car that is self driving. After awhile some issues will arise and people will want to go back to the old way, with the person driving.
[Nexus 6 Android Development] apophis9283:
Also, I dont think a kernel can be compatible both ways. I havent looked into it yet, but I may

If anyoone has any info feel free to link
[Nexus 6 Android Development] str8str:
Synapse still won't hold settings after boot for me keeps saying synapse boot not completed so I'm staying with kernel auditor which is much more stable for my experience. All settings restore after boot now every time. Also from what I understand you can't have it both ways for root with a kernel. I myself agree I don't see a point with it and will be staying with normal root. It may have it's niche but not for anything I do or want.

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Weird, Synapse is still holding settings for me. Cant say Ive done anything special to make it work. Just seems to work
[Nexus 6 Android Development] clothednblack:
+1 haven't had any restore issues after a reboot with KA or root problems (as in any app that requires root says I'm not rooted after setting up with synapse ) because I'm using 2.62 SU.

I'm sure I will revert back to 2.52 SU eventually, then I will test synapse again, but for now, this workaround is great.
[Nexus 6 Android Development] apophis9283:
As long as everyone is happy
[Nexus 6 Android Development] clothednblack:
I'm happy, my root issue has absolutely nothing to do with this kernel, I accept full blame but on a different note, I just reverted back to system root so I will test synapse again.
[Nexus 6 Android Development] KonoeKyon:
With the talk of systemless root, just gonna say I've had no issues this far with it. This kernel works just fine with systemless root. I don't think there's anything you need to do to make it compatible with both methods since your kernel is using anykernel to patch the existing kernel.

My opinion is use whichever works for you until chainfire has everything worked out and deems whichever method he decides to continue with stable. Same stuff happens with every new Android release, just need to be patient and wait for everything to be worked out.

Sorry if that's too off topic.

On another note, 1.3 is working well so far, though I'm getting an io read error on one setting for interactivex, the boostpulse tuneable seems to be unreadable. I do my settings using scripts and not synapse though. But you can check it in a file explorer, it won't be able to read or edit the file for boostpulse.
[Nexus 6 Android Development] apophis9283:
Ill try and get it worked out for next release
[Nexus 6 Android Development] str8str:
Yes it is. Oh well no biggie I like kernel auditor better myself anyway. It's getting better all the time with active development unlike synapse

Straight Shooter

---------- Post added at 18:37 ---------- Previous post was at 18:23 ----------

Have to say that this kernel is running like a well tuned engine

Straight Shooter
[Nexus 6 Android Development] apophis9283:
I checked on INTERACTIVEX everything seems good. I have what LK dev has

Edit: I added a few things, fixed a few things and decided to clean up my linux mint OS. Done for the night. You all have a good one and thank you for all the support
[Nexus 6 Android Development] apophis9283:
So just tested the kernel with a CM based ROM. Everything seems fine

Resurection Remix has it going on. Im impressed

Edit: it really has it going on they even have on the go mode. Im so happy to be back on a ROM I actually enjoy
[Nexus 6 Android Development] apophis9283:
Got it all setup, from the top. Using our boot image with Resurrection Remix, their boot animation. Set it up the way I like it, kernel is all setup. So many options my head almost exploded. Everything is running great. Glad to have the theme engine back instead of RRO. Im using a theme from one of the devs of Resurrection Remix. Its really nice
[Nexus 6 Android Development] str8str:
Oh great I'm going to give it a try I miss the theme engine. I'm on despair ubermallow and love it but I'm going to try that one as my secondary rom. Btw I'm really liking umbrelacore getting great battery 0.3% an hour.

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Umbrella core is my favorite. I love it. Havent used any other governor since we brought it in
[Nexus 6 Android Development] apophis9283:
Heres the wrap up for tonight. I brought a ton of stuff in. Its building now but powersave governor should be available soon. Im probably gonna go through some of those governors and get rid of them. Ill also be on the prowl for new governors if I think they would be beneficial. Dont want to add governors just to add them. Ill probably wait until we get closer to the end of the year before I push a new release,
[Nexus 6 Android Development] str8str:
So far so good res remix seems very cool especially with blue hydra theme totally refined from scratch blew me away. Also kernel is running good on it so far

Straight Shooter
[Nexus 6 Android Development] merikgvr4:
Using pure nexus and your singularity. Tried umbrella core but I'm getting half if my screen different than the other half. Are you guys getting this?

Edit... Went back to zzmove using profile 2. No more screen problems.
[Nexus 6 Android Development] S0UTHPAWK1LLA:
That split screen issue is a hardware issue. It's looks like the left side of the screen is higher than the right side. It's been happening here and there to my phone as well regardless of the kernel. I disabled H/W overlay in the developer settings to get it to stop.. Might be 6P time..
[Nexus 6 Android Development] jcrompton:
Hotplugging

Could you guys give me a quick synopsis and/or thoughts on your own personal use of hotplugging --- [MENTION=2967322]buckmarble[/MENTION] is a pretty smart guy and makes a pretty good case for not using hotplugging at all with this phone.

What you guys using ?
[Nexus 6 Android Development] apophis9283:
Look at posr number 1 or 2 below op
[Nexus 6 Android Development] jcrompton:
Hey thanks ... you are always quick to reply and share!

I guess what I meant was even to share on the whole idea of hotplugging vs not (kinda a rebuttle to the idea that hotplugging isn't necessary or helpful for the Nexus 6)
[Nexus 6 Android Development] apophis9283:
[MENTION=2967322]buckmarble[/MENTION] is pretty smart when it comes to kernels, he even drops by the thread every once in awhile. My thought is some kind of hotplugging would be needed to turn cores on/off. That can be achieved by using a governor that has hotplugging built in and use zen decision or use a governor without hotplugging built in and use a hotplug. Thats just my thoughts. If [MENTION=2967322]buckmarble[/MENTION] would like to chime in Im always open to him commenting in my thread
[Nexus 6 Android Development] KonoeKyon:
Not worth it on this chipset, as was mentioned in that thread, it goes against the efficiency of how the CPU was meant to work. Using hotplugging just makes you sacrifice a lot of performance for a negligible gain in battery life. So it's not worth it.
[Nexus 6 Android Development] apophis9283:
If thats what you want, then use zen_decison. Its not a hotplug but an mpdecision replacement
[Nexus 6 Android Development] EvilDobe:
1) Kudos for you man. Every time I look at this thread you're always posting (long time stalker, first time[I think?] poster here). Amazing support for your product. Gold star for you.

2) Been using blu_active & blu_plug (if you glance quick enough it almost says buttplug). Thought about switching to nightmare or tripndroid just for something different. Any words of wisdom on that setup? Not all that familiar with nightware or tripn.
[Nexus 6 Android Development] apophis9283:
Nightmare is less battery more power. Theres a governor called Darkness that is a "upgrade" of nightmare. Ive always enjoyed Nightmare. Until I ran into UMBRELLA_CORE. Which tends to be more power less battery. Tripndroid is around the battery/performance, so inbetween. I also have the tripndroid I/O scheduler. I do plan to get rid of some of the governors before next release. Maybe look if any of them have been updated, or updated by making an all new governor. If you look at post 2 or 3 (I can never remember) I wrote down some ways to setup the kernel. From power saver to straight performance. Take a peek at that and if you have any more questions, feel free to ask. As far as me interacting with the users, most devs basically say that they made the kernel for themselves and thought they would share. My thought is I created this kernel not only for myself but for the community. I LOVE FEATURES, and most users do too. So we have that in common. Which is why I always accept feedback, either issues you're having to requesting new features, I want this kernel to be fun for everyone. Not just me.

I attached a screenshot of a benchmark I just ran. Its a lot higher than a few builds ago. I dont really believe in them but I decided to run one for a laugh.

I killed HELLSACTIVE (I have enough interactive based governors) and WAVE governor. I added DARKNESS which is nightmare updated and ALUCARD

governor. I may kill NIGHTMARE because I have DARKNESS now. No point in having both and DARKNESS is updated. DARKNESS doesnt have many tuneables though. I guess Im on the fence atm
[Nexus 6 Android Development] str8str:
Am I missing something here? I don't have darkness

Straight Shooter
[Nexus 6 Android Development] apophis9283:
No you arent missing anything. Ive been busting my ass on the kernel. Youre gonna see some governors removed but some new ones added. Darkness has been added and nightmare removed. Im still busting ass to get the other ones going. I was gonna keep this all locked up and release it around christmas time but I have a lot merged in and a lot of stuff removed / added. Hang in there and ill try to get you something by days end
[Nexus 6 Android Development] str8str:
Been playing around with xperience governor and really liking it

Straight Shooter
[Nexus 6 Android Development] apophis9283:
HELLSACTIVE and WAVE governors are gone. HELLSACTIVE is just another INTERACTIVE governor which the kernel has plenty of. Wave just drew the shortest straw. I may still kill a few more I havent decided. Ill decide once I get the new ones running
[Nexus 6 Android Development] apophis9283:
Finally, Singularity V-1.4 and SINGULARITY-UKM-V-1.2 is up in the OP. Im pretty sure I changed all the things that needed changing in the OP ( To reflect the governors I got rid of and ones I added. Even through in a nice new shiny Hotplug for anyone who would like to use it. Im done for the night, I hope you all enjoy it. Some of it was a pain in my a**. Enjoy!
[Nexus 6 Android Development] str8str:
Thanks for all your hard work it is much appreciated.

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Hopefully you all will like the new features
[Nexus 6 Android Development] KonoeKyon:
Thanks for the update, going to give alucard a try, I used to run his kernels on some older devices and ran that or nightmare on them. Usually with this device I run elementalx or interactivex.
[Nexus 6 Android Development] apophis9283:
Im using darkness. Ever since I flashed it, Ive become fond of it.
[Nexus 6 Android Development] baboomerang:
Hey, big things fixed!

Somehow, flashing this new UKM over the old one fixed my synapse problem? Thanks dude! Note for anyone having the issue of synapse not applying boot settings.

1. Disable Stability Check

2.Delete Synapse

3.Flash UKM 1.3

4.Flash UKM 1.4 right ontop of 1.3

5.Reboot

6.ReInstall Synapse

7.PROFIT!?!?!??!?!

EDIT: Seems like it saved the boot settings only once. After a second reboot, my settings were wiped again :(

I'll see what is the problem and tell the kernel [MENTION=4392154]apophis9283[/MENTION] what causes it ( So he can put it in the FAQ :cool: )
[Nexus 6 Android Development] apophis9283:
If you need anything you can get with me on Hangouts. steaven.android@gmail.com

If any of you need anything you are welcome to get with me on Hangouts
[Nexus 6 Android Development] baboomerang:
Sorry for sending you so many comments about the kernel, but I noticed one small detail missing ( probably intentional but idk )

For the bricked hotplug mechanism, I noticed there isn't a cpu4 hotplug out :p

I will always test every single detail about the kernel possible and give you feedback for as long as I have a functional nexus 6 device XD
[Nexus 6 Android Development] apophis9283:
The cores arent measured like that. Cores are measured as 0-3

Although something may not be right. Ill look into now.
[Nexus 6 Android Development] baboomerang:
It kinda looks confusing at first but this is what I see on my screen:

[COLOR="Lime"]Runqueue Threshold Hotplug [B]CPU1[/B][/COLOR]
[COLOR="Gray"]Runqueue Threshold Unplug [U][I]CPU0[/I][/U][/COLOR]
[COLOR="Cyan"]Runqueue Threshold Hotplug [U][I]CPU2[/I][/U][/COLOR]
[COLOR="DarkGreen"]Runqueue Threshold Unplug [B[U]]CPU1[/U][/B][/COLOR]
[COLOR="Orange"]Runqueue Threshold Hotplug [U][I]CPU3[/I][/U][/COLOR]
[COLOR="Teal"]Runqueue Threshold Unplug [I][U]CPU2[/U][/I][/COLOR]
[COLOR="Red"]Runqueue Threshold Hotplug [B][I][U]CPU4[/U][/I][/B]??!?!?!?!?![/COLOR]
[COLOR="Sienna"]Runqueue Threshold Unplug [B][I][U]CPU3[/U][/I][/B][/COLOR]
[Nexus 6 Android Development] apophis9283:
Im not debating somethings wrong. Look at your cpu frequencies. They go from 0 to 3

I also just posted in response to you. I still think somethings not right I will look into it now
[Nexus 6 Android Development] apophis9283:
Ok! SINGULARITY-UKM-V-1.3 is up. It completely fixes hotplugs. It will look more like 2 builds ago. I tested it and looked it over, everything looks beautiful and everything is completely functional. You dont need to flash the kernel and you can flash 1.3 over 1.2
[Nexus 6 Android Development] :
Thats what you see on what screen where?

In synapse? In another kernel app? In your logcat? In dmesg?

If that's just popping up on your screen randomly, you have far bigger issues than the hotplug numbering.
[Nexus 6 Android Development] apophis9283:
Its fixed already.
[Nexus 6 Android Development] :
Can you link to the case he made for not using it?

The only reason that hotplugging is ever a bad thing is when the hotplug driver tries to be too aggessive in unplugging cores.

Basically, think of it in the same context of the idea of a lightbulb. If you're going to be turning it off, then back on a second later, it took more energy to turn it back on than what was saved. If it's being turned off and left off for awhile, you saved energy. However that amount of energy saved needs to outweigh the initial turn-on cost.

It's the same idea with cpu hotplugging.

I saw a later post in this thread talking about how the chip is designed to run with all cores online and actually runs less efficiently when hotplugged. That seems like pure speculation, as it's not how most arm chips work. I wouldn't put too much faith into it unless people can provide whitepapers proving such claims.

---------- Post added at 12:29 AM ---------- Previous post was at 12:27 AM ----------

Figures. I'm just trying to catch up on the last few days worth of posts on awful internet.
[Nexus 6 Android Development] apophis9283:
9

Released a kernel and ukm build today. Think youll like it
[Nexus 6 Android Development] apophis9283:
Havent posted screenies but this is what my phone looks like
[Nexus 6 Android Development] apophis9283:
I decided to sync Resurrection Remix. I like making my own builds and adding stuff. Its been awhile since I worked on a ROM, have a feeling I might screw something up
[Nexus 6 Android Development] DreamFX:
You should try VRtoxin.
[Nexus 6 Android Development] apophis9283:
I like RR. I added a few things like tile vibration
[Nexus 6 Android Development] str8str:
How's it running? Compared to the original

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Havent flashed it yet. I wanted to add a few things to my kernel. Mainly this (which should extend battery life)

https://github.com/team-vortex/Singularity/commit/1b2b5760551548fc44a5f0bfeadc284e7f3a1695
[Nexus 6 Android Development] jcrompton:
I've had some problems with RR -- Just an hour or so ago I had RR running your latest kernel and had 2 random reboots. The other main issue that is happening is that with the reboots and sometimes even without the reboot I lose LTE data. The phone shows signal but there is no data .... cycling airplane mode immediately brings back my LTE signal (the issue is the random loss and the fact that even though I'm showing signal incoming calls are being sent to voicemail --- a problem when you use your phone for business)

I installed Elite kernel and even upon first boot I saw the same issue (so , not that you might have thought it was < it's certainly not the kernel )

I also had another issue I didn't mention until now -- when I tried to put my script in the system/etc/init.d folder on RR the phone would not boot. I had to reinstall the ROM. If I just ran the script once booted it worked fine. Weird I know but I'm trying to make it work since I love the ROM and the kernel!
[Nexus 6 Android Development] apophis9283:
Im about to flash my build now
[Nexus 6 Android Development] baboomerang:
I found the ultimate fix for synapse not saving settings

I just quoted you to get your attention :P

Somehow your UKM also installs a second copy of busybox that only synapse uses.

I did some google-fu and followed what XDA [MENTION=1863016]rachanta[/MENTION] said:

TL;DR

DONT UPDATE BUSYBOX!

UNINSTALL Busybox App,

DIRTY FLASH YOUR ROM + REFLASH LATEST UKM.

I did just that, then copied the included UKM busybox to my xbin folder and Synapse boot completed successfully!

Apophis, would there be any way to implement such a fix into your UKM flash script? Though I consider the possibility of not doing so because not many people have this problem.
[Nexus 6 Android Development] apophis9283:
Id have to look at it all. Honestly probably wont be doing anything til after Christmas.
[Nexus 6 Android Development] klabit87:
I am new to this kernel and am loving it!

Excellent battery life. better than any other I've tried.

Just one question though. I'm sure you recommend UKM but what exactly does it do?

Ive looked at it and it appears to be a way to control the kernel?

Just looking to clarify. kernel 1.3 worked great and updated to 1.4 earlier and have had 2 random reboots. no undervolt or anything special that could cause that. I dont think anyways.

Just wondering if I should flash the UKM

Thanks for your time.
[Nexus 6 Android Development] str8str:
So if I read this correct with this added when the battery says full it will actually be full?

Straight Shooter
[Nexus 6 Android Development] apophis9283:
When you plug it in to go to sleep, it gets full, then to save the battery quits charging then when it gets low enough it charges again. As we have a battery that cant be removed it would save the life of the battery a bit. It reduces the amount of time the phone charges after being on the charger for so long. Reduce the amount of charges is a good thing.
[Nexus 6 Android Development] wase4711:
was that with test 2?

thanks
[Nexus 6 Android Development] apophis9283:
Yes Im getting great battery. I may wait to rebase until "M"
[Nexus 6 Android Development] apophis9283:
OP updated, out of testing. You wanted better battery life, its here. See screenshot. Also still smooth, didnt have to sacrifice much to get way better battery.
[Nexus 6 Android Development] wase4711:
dont blame you for waiting!

I'll try this on EOS and Bliss now..
[Nexus 6 Android Development] DreamFX:
8 days left lol.
[Nexus 6 Android Development] apophis9283:
In case you were wondering what Im running, heres my setup

Frequencies are 35MHz MIN and 2899MHz MAX

MSM_LIMITER is 960MHz suspend

10 Defer time

CPU process scheduling is Power-Aware

Power efficient Workqueues checked

Governor conservativex

I use MSM_MPDecision stock settings

I undervolt -10 across the board

read ahead size 2048 using SIOPLUS

NR Requests 2048

GPU 110 min 700 max. I use powersave. I know a lot of you are thinking powersave may cause issues. I play games all the time, none of them are really cpu and gpu intensive games but I have no lag what so ever

Under memory dirty background ratio and dirty ratio are both at 50%

drop caches and laptop mode both enabled.

swappiness is at 50%

vs cache pressure is at 100%

For TCP Ive been using Illinois.

Fsync off

Use FB notifiers checked

fast charge off

wakelocks

Host wakelock set at 2

bluesleep wakelock off

sensorind wakelock on

BCMDHD set to 2

UKSM

sleep is at 600ms

cpu governor medium

For LMK I use aggressive, ( not everyone may like this. Use default if you done want your apps killed aggressively)

I crank up wifi scan interval to 300 secondss

VM heapsize 1024MB

check allowing purging of assets

Thats my setup, but play with it. You may find something you like better.
[Nexus 6 Android Development] berndt_toast:
What settings are you using for that battery life? Governors, I/O schedulers, Hotplug, etc...

And Because I didn't read the post right above me, it's written in great detail. Thanks.
[Nexus 6 Android Development] apophis9283:
ive tried to make what I use stock. Im still working on that
[Nexus 6 Android Development] wase4711:
not sure if it was coincidence or the kernel, but on EOS, after flashing your kernel, I was unable to send and receive text messages in either Messenger, or Messages; It was working fine prior to that on BluSpark Kernel

Thanks!
[Nexus 6 Android Development] apophis9283:
I use anykernel as the zip. Meaning it uses whatever ramdisk you already have. Maybe flash the rom, then flash my kernel. Blu spark may use his own ramdisk. Im new to kernels but that may be what happened
[Nexus 6 Android Development] wase4711:
not a problem; I'm gonna try it on Blisss Pop now, I assume it should work perfectly on that Rom :o
[Nexus 6 Android Development] apophis9283:
Yep, I just finished up setting defaults in Defconfig. Im poking around doing some small maintenance
[Nexus 6 Android Development] Psych0t1c20:
Ok check this out. So I flashed the kernel. I wiped cache, and dalvik beforehand, so I restart, and the bootanimation is going REALLY slow. Then the ROM loaded up but says the system isn't responding. I flashed a different kernel and no issue. Tryna figure this out because I wanna use this.
[Nexus 6 Android Development] apophis9283:
I use anykernel zip. So it uses whatever ramdisk you have. Best thing I can tell you is to flash your rom again, then flash my kernel
[Nexus 6 Android Development] Psych0t1c20:
Anyway I can edit the ramdisk because I just flashed the blisspop update 20mins prior, and the whole slow bootanimation happened off a clean flash.
[Nexus 6 Android Development] apophis9283:
So you didnt flash a custom kernel after bliss?
[Nexus 6 Android Development] Psych0t1c20:
No. IT was straight whatever kernel they have. Then 20mins I saw this and flashed.
[Nexus 6 Android Development] apophis9283:
Then somethings weird. It should be fine. im running blisspop I made last night and its ran fine. Go into blisspop settings and look into dev options and see if ignore force closes is checked. Im about to upload a new build. Its only a small version bump to 1.1. I changed the compression method

Edit NVMD it wont boot using this compression