yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] apophis9283:
Look at my github by the link in the OP. If i can get this to build ill push a 1.4.1 as Ive added a few more commits
[Nexus 6 Android Development] DreamFX:
Will do. Also you're using Linaro 6. You should update your thread title to reflect.
[Nexus 6 Android Development] apophis9283:
Its in the OP. Im flashing 1.4.1 right now. If its good ill update OP and push to my github
[Nexus 6 Android Development] apophis9283:
Ok ive updated to 1.4.1

you all have a goodnight
[Nexus 6 Android Development] sonofevil77:
Great job. This thing is flying and not heating up like usual.

Sent from my Nexus 6
[Nexus 6 Android Development] apophis9283:
Hows 1.4.1 running for everyone?
[Nexus 6 Android Development] Georgiafan1969:
Running smooth and man this kernel has my phone zooming,great job dude.:good:
[Nexus 6 Android Development] apophis9283:
Thanks. Glad you're enjoying it
[Nexus 6 Android Development] dusk1911:
Hey .. Is this kernel Se permissive ?
[Nexus 6 Android Development] apophis9283:
yes
[Nexus 6 Android Development] wase4711:
Still having issues trying to double tap/wakeup the phone while taking off the charging stand...any suggestions?

Using latest Bliss Pop Rom, and your kernel settings

thanks
[Nexus 6 Android Development] apophis9283:
Theres a setting in blisspop for it. Enable it. Not sure if it causes issue with kernel setting
[Nexus 6 Android Development] modernbummer:
Ah, that's right! [emoji2]
[Nexus 6 Android Development] :
Don't you tell people I'm a great guy...

It'll make my epic dickhead posts... somehow less dickheaded.
[Nexus 6 Android Development] apophis9283:
Its me I remember you. I did sabermod AOKP builds
[Nexus 6 Android Development] apophis9283:
You will now be able to turn BCL on/off in UKM. Yoinx wrote it up and I submitted it to kernel auditor. So its up to him. I suggest a little pressure. Thee will only be one build from here out.
[Nexus 6 Android Development] :
LOL.

Man, why do these users hate me. You announce that I fixed something, a few people like it.

Me, I'm just sitting over here like "Can a mofo get some thanks?"

Maybe it's because I'm not a people person?
[Nexus 6 Android Development] apophis9283:
I missed mythx_plug governor. Feels good to have it back. My partner in crime Yoinx makes miracles.
[Nexus 6 Android Development] str8str:
You guys are the best. Thanks for everything much appreciated as always. Yes this means you to voinx

Straight Shooter

---------- Post added at 01:36 ---------- Previous post was at 01:32 ----------

Wow you guys don't fool around. Good job??

Straight Shooter
[Nexus 6 Android Development] :
Since you're is if the few competent guys out there that notices the difference between bcl enabled and disabled, think you might be willing to test a build? Needs to have bcl toggled manually in sysfs.
[Nexus 6 Android Development] str8str:
Sure

Straight Shooter

---------- Post added at 07:07 ---------- Previous post was at 07:05 ----------

I'll get to it in afternoon. Let me know

Straight Shooter
[Nexus 6 Android Development] apophis9283:
I suppose youll need a build. Ill get one together soon and upload to a private site.

Just some info. HYPER is gone and HYPERX has been brought in. MYTHX_PLUG is back and a governor called PSYCHOACTIVE.

The governors are probably done now. I think my goal of making this kernel the swiss army knife of all kernels is almost complete
[Nexus 6 Android Development] apophis9283:
Sent you a PM with a private link to the test build
[Nexus 6 Android Development] apophis9283:
Finally got Software CRC control to show up in UKM. Damn thing was driving me nuts. If you thought the last build had a lot of changes, you are in for a treat next build
[Nexus 6 Android Development] apophis9283:
Thank You Mr. Voss, Very much appreciated
[Nexus 6 Android Development] modernbummer:
No, sir. Thank you!
[Nexus 6 Android Development] baboomerang:
In a week [MENTION=4392154]apophis9283[/MENTION] gets like a thousand "thanks" from everyone XD. I remember when you had like 2,000 thanks and now you have 6,000! Nice work though, and judging from the thread are we using kernel adiutor instead of synapse now? Have you gotten the settings to stick between reboots? Anyways keep up the good work! I always watch your thread daily :P
[Nexus 6 Android Development] apophis9283:
Use whatever you wish. I still use Synapse and UKM. No it still doesnt hold after a reboot. I just have a ton of stuff for the next release. from aditions to fixes to just updating stuff. Its all there. I really think you all will enjoy the next release.

Also caught the GPU dipping to 27MHz. Fixed that.
[Nexus 6 Android Development] str8str:
OK

Straight Shooter

---------- Post added at 17:55 ---------- Previous post was at 17:40 ----------

Sent you a pm as well

Straight Shooter
[Nexus 6 Android Development] str8str:
Been running test for a while running good I really like smartassv12 very quick and smooth fur multi tasking

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Oh you dont even have half of what Ive done.
[Nexus 6 Android Development] papanut:
You guys know how to dangle a carrot
[Nexus 6 Android Development] str8str:
Read my PM and let me know

Straight Shooter
[Nexus 6 Android Development] apophis9283:
UKM still isnt ready for BLC.
[Nexus 6 Android Development] modernbummer:
So I've tried to enable sweep gestures in kernel adiutor, but they don't seem to work for me. However, they do work when enabled in EX Kernel Manager. Anyone else experiencing this?
[Nexus 6 Android Development] str8str:
OK cause voinx said has to be enabled using sysfs thought he meant the test build

Straight Shooter

---------- Post added at 22:28 ---------- Previous post was at 22:25 ----------

Check your hang outs

Straight Shooter
[Nexus 6 Android Development] apophis9283:
If Yoinx and I cant get the UKM BCL thing. Ill locally revert the added BCL commits and then do like i did before and make 2 builds
[Nexus 6 Android Development] str8str:
10/4. Have a look at this please. Had s random reboot

When I unplugged the phone from charging. Using test.

https://www.dropbox.com/s/egmlw4b5w9m1wmf/logcat.log?dl=0

Straight Shooter
[Nexus 6 Android Development] :
I only see like 4secs of log, and it all deals with the camera.
[Nexus 6 Android Development] apophis9283:
Fstab is the reason F2FS isnt working. Ill try to add that today among other stuff

Edit: Added and I made sure it was encryptable and not force encrypt. Im gonna even test it on my phone before release
[Nexus 6 Android Development] apophis9283:
I have to update f2fs when i get home, then ill have to revert some BCL comits and make one with bcl and one without. There will be a release today. No longer dangling carrots
[Nexus 6 Android Development] apophis9283:
OP has been updated. We werent able to get BCL in UKM yet, so there is 2 separate builds like last time. We both have a ton of time in this latest build so we hope you enjoy. Theres just so much in it. You can always check our Github. Hope you guys enjoy it. Its been updated to V-3.4 and UKM to V-1.8. All that was added in UKM was the ability to toggle Software CRC. Its off by default but if for some reason you want it on now you can. Also 3 new governors MYTHX_PLUG, PSYCHOACTIVE and HYPERX (Took the place of HYPER). Theres all that and so much more. Enjoy!
[Nexus 6 Android Development] Jiggs82:
I've never seen a kernel be updated as much as this one is haha great work as always keep it up :p
[Nexus 6 Android Development] apophis9283:
When I push updates its always more than just 5 or 6 commits. Look at the changelog for 3.4. Youll see
[Nexus 6 Android Development] str8str:
All gonna be on next build?

Straight Shooter
[Nexus 6 Android Development] apophis9283:
No, all on this build I just pushed
[Nexus 6 Android Development] str8str:
So 3.4 that's the last one correct

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Yes, Fresh off my ssd today
[Nexus 6 Android Development] zhuchella:
Where can I find UKM to flash?
[Nexus 6 Android Development] klabit87:
It's in the op as an attachment.
[Nexus 6 Android Development] nazfalas:
3.4 is smooooooth. Thanks for the many updates.
[Nexus 6 Android Development] apophis9283:
UKM stuff is no longer an attachement. Its a link in the OP with a brief description. Also changed my OP image.

Edit edited AUTOSMP to be a little more optimized. Changed a few things in Anykernel. ZZMOOVE updated to Snapdragon version
[Nexus 6 Android Development] baboomerang:
Woa, this kernel has all the features and MORE THAN BEFORE. You are seriously the only person that has done this great job. BTW I seem to have trouble running my phone above 2.9 GHz. Can anyone overclock their phone to stable 3.0GHz +? I even tried to raise my voltages and phone still randomly rebooted even at low frequencies. Maybe that was BCL playing with settings? Im not sure.

Anyone on Nexus 6 with 3.0 GHz Overclock Stable?
[Nexus 6 Android Development] :
More than likely is just the way your chip is binned. Some of the people on this phone with higher bin values have a hard time with overclocks while people with lower bin values get much higher stable overclocks.
[Nexus 6 Android Development] baboomerang:
I have PVS Bin 4 and Speed Bin 2 I think thats pretty low :3

a buddy of mine has a PVS 0 and Speed Bin 4 Im so jealous :D

I admit though I haven't tried overclocking with BCL disabled/updated versions of Singularity ( I was attempting way back when it was called HSB )
[Nexus 6 Android Development] :
Yeah at those values you shouldn't have an issue.

Its very possible that bcl hotplugging your cpu may have caused issues. The cpu cores that bcl hotplugged tended to come back with the performance governor (ironically since it unplugged them thinking that there was too much current draw to begin with).

If that was the case, it could have caused a reboot when running with an overclock.
[Nexus 6 Android Development] apophis9283:
what settings do you have for msm_limiter?
[Nexus 6 Android Development] KonoeKyon:
I've run mine stable at 3.03 on other kernels and 3.09 on this kernel without issues, for almost a year now. Just requires testing to get the right voltages for your device, but not everyone's phone can handle 3GHz.

If you have the time and are patient with it, slowly test each frequency above stock until you reach one that isn't stable, then raise voltages by a small amount until it's stable, and continue to the next frequency. If you reach a point where it's not stable and you can't get it stable then it's possible your phone may not be able to handle it.

My device is PVS bin 7 BTW.
[Nexus 6 Android Development] baboomerang:
I'm using kernel adiutor and I have my min max as 35mhz to 3,091mhz.

So far it seems stable for a short amount of time at 3.0ghz but if performance governor is enabled the whole system crashes instantly.

Meaning small intervals of 3ghz is stable but not continuous. 2.9ghz is perfectly butter smooth for me though.
[Nexus 6 Android Development] apophis9283:
Thats because performance forces your cpu to be at the highest frequency all the time. Bad idea. I doubt anyones phone could run that for an extended period of time.
[Nexus 6 Android Development] KonoeKyon:
I've forgotten mine being set at 3GHz min/max after benchmarking without any issues, no crashes or the such for the majority of a day.

Again once you get the voltages worked out for your device, provided it can handle it, it should be stable. If you can't stay at max freq for extended periods of time, it's not a stable OC.
[Nexus 6 Android Development] :
Its not so much a matter of it staying stable at max freqs.... Its more of a matter of not frying the chip. You're running a chip that has no cooling method (at least not much of any cooling method) above it's stock frequencies. It's not designed to be run like that and the extra heat can cause damage.

Really, I'd be less concerned of stability and reboots and more concerned over permanently damaging the hardware. Ideally the thermal throttles *should* help save it... But that's all software based. If the chip freezes up and stops processing but stays locked at max frequency (yes, it's technically possible) there's not really any sort of hardware watchdog to shut it down.

I mean really... Its a quad core computer running at 2.6ghz in your pocket. It's it really worth the risk of damage to get that extra... What, 500 mHz.

With any other governor, sure... Whatever. But overclocking and running performance for an extended period is just asking for trouble.
[Nexus 6 Android Development] KonoeKyon:
I'm not saying it's worth it or not but that it's possible and has been done. The question was about stability, which is what I was talking about. It was unintentional to leave it at max frequency, but it was stable locked at 3GHz that is the point I was trying to get across. Honestly there's no real performance gain with overclocking unless you look at benchmark numbers, and even then it's not much. Sorry if I had offended you or anyone or something of the such.

I OC because I like to push devices to their limit, to see what is possible. Will it shorten it's lifespan? Sure. Will the chip burn up on me? Always a possibility, and if that happens I just buy a new phone to play with. It's not a matter of it being worth it or not, it's just like pushing anything else to its limits, be it a phone, a computer, a car.. It's just a hobby and I accept the risk. So on that note I don't recommend overclocking unless you accept that you could potentially damage your phone.
[Nexus 6 Android Development] :
No offense taken.

I was just following you up with the scared straight side of it for the people who don't necessarily understand what they're doing and just like to slide all the sliders as high as they go.

They're out there and normally if they even actually read anything they might only look at one or two posts around it. So just wanted to make sure that was posted nearby.
[Nexus 6 Android Development] apophis9283:
I LOVE pancakes FYI
[Nexus 6 Android Development] str8str:
Do me a favor and try out psychoactive governor.

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Why?
[Nexus 6 Android Development] str8str:
If you would of just tried it to you would know already. It reboots the phone and I want to verify that's all

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Yeah just tried it. It will be removed next build
[Nexus 6 Android Development] apophis9283:
i had people message me about fast charging and F2FS. I just completely got rid of all that code. I just compiled to make sure no code was left behind. As my wife and her mom are heading to mass.. Ill have a bit of time. To try and iron out these issues
[Nexus 6 Android Development] adio201:
Anyone running bcl on nexues 6
[Nexus 6 Android Development] apophis9283:
I have run it with and without
[Nexus 6 Android Development] adio201:
Dose that really make a difference on performances and battery?
[Nexus 6 Android Development] apophis9283:
I prefer bcl disabled. There tends to be more speed without it. Try them both. Then choose for yourself
[Nexus 6 Android Development] baboomerang:
Actually, this

JUST HAPPENED TO ME OVERNIGHT

. I left the phone though on lionfish governor but overclocked to 3,033mhz. I left the phone in sleep mode to my side and I woke up 6 hours later with an

INTENSE BURN ON MY LEG

. I used an infrared scanner and it reports temperatures as

HIGH

as 157-189 degrees Fahrenheit. My phone's battery went from 96% to 12% in 4~6 hours. Does my phone still work? Yes, and I can still run games perfectly smooth :silly: Will I be more cautious next time? Definitely.
[Nexus 6 Android Development] :
Wow man, that sucks. Ironic that it happened after I posted that though... Like I jinxed it.

Hopefully you don't have a legitimate burn and you meant it was just really hot.

But, it's something that people need to be aware is possible. Hence why everything in phone modding is always at your own risk.
[Nexus 6 Android Development] apophis9283:
Were you running Performance? People lets use a little caution when dealing with OC and other tuneables. Ive ran 4 antutu test back to back with OC using mythx_plug and gpu on performance. Never got any heat like that. I do not use BCL.
[Nexus 6 Android Development] apophis9283:
BCL will no longer be an option. All builds will have BCL
[Nexus 6 Android Development] KonoeKyon:
Any reasoning for the change? Did you manage to get the toggle working in synapse? Anyway eagerly waiting to see what your next update brings. :good:
[Nexus 6 Android Development] apophis9283:
Recant my statement after talking with Yoinx. There can still be 2 builds until a toggle can be worked out
[Nexus 6 Android Development] zhuchella:
apophis9283

What governors do U use for CPU and GPU for smooth and battery life ? What max freq do U set for CPU and GPU ?
[Nexus 6 Android Development] nazfalas:
Stock settings work pretty well for that.
[Nexus 6 Android Development] apophis9283:
A few of my favorites lionfish, interactive_pro, dynamic_interactive, smartassv2. GPU I leave default. As far as oc for cpu around 2.88
[Nexus 6 Android Development] modernbummer:
I second that. This thing flies right out of the gate.
[Nexus 6 Android Development] str8str:
Now that's some serious battery life

Straight Shooter

---------- Post added at 10:15 ---------- Previous post was at 10:06 ----------

Straight Shooter

---------- Post added at 10:19 ---------- Previous post was at 10:15 ----------

I've noticed smartass governors lock the frequencies at max

Straight Shooter
[Nexus 6 Android Development] apophis9283:
shouldnt

https://github.com/Team-Singularity/Singularity/blob/MM/drivers/cpufreq/cpufreq_smartassh3.c

https://github.com/Team-Singularity/Singularity/blob/MM/drivers/cpufreq/cpufreq_smartassv2.c

https://github.com/Team-Singularity/Singularity/blob/MM/drivers/cpufreq/cpufreq_smartmax.c
[Nexus 6 Android Development] modernbummer:
Seems that's where mine is at most of the time as well on smartassV2.
[Nexus 6 Android Development] apophis9283:
SmartassV2 is know for being a (performance) governor. Very low thresholds to rise to the highest frequency BUT it should not lock in the highest frequency. Thats what Performance does. It would also depend on what your max frequency is. I will lower the frequencies for those who use close to stock frequencies

Edit just lowered the ideal frequency for wake

https://github.com/Team-Singularity/Singularity/commit/445a5cddc4082e05edde976fd6a6321dc25fa2e5

This has explanations for almost every govenor and hotplug. Maybe read it before choosing a governor

http://androidmodguide.blogspot.com/p/blog-page.html

11: SmartassV2:

Version 2 of the original smartass governor from Erasmux. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
[Nexus 6 Android Development] baboomerang:
I had lionfish governor. The problem is that if the phone gets to a certain frequency under too low of a voltage, it stays in a zombie state. Its off in that nothing responds on the phone but its stuck at max frequency doing absolutely NOTHING. Its on in terms of GPU + CPU but the whole device is basically in a coma. There is no throttling so it just burns itself out if left too long.

I know this happens because I used to undervolt my Galaxy S4 like crazy and something very similar happens but on lower frequencies.
[Nexus 6 Android Development] :
Not exactly what happens... But similar enough on a non-technical level that it doesn't really make a difference.

The problem is that the glitch that causes this with chips is pretty uncommon... So most people won't ever see it or believe it happens.

I probably wouldn't either if hadn't personally observed it happening before while data tracing through boards (not this phone).

*edit*

The reason that i had put the warning out there about this originally wasn't because I expect that it would happen often or even anything that the kernel does would cause it. In my experience, it's basically just a hardware glitch that stops clicking data through the chip (probably missing a reset pulse) but that's purely a hardware glitch.

The concern is that the electronics in the phone are technically supposed to be able to run at stock values for extended periods without damage. So if this happens at stock values, it's annoying but not a big deal. However, if you're overclock to 3.09 it's an extra 100mv over 2.6 (10%) which also equates to more power dissipation (heat).

Assuming that all consumer electronics typically have a 5% tolerance on components... There's no guarantee that anything would handle the extra power in a chip lock situation when you're boosting it above even typical tolerances. Of course the hardware we have may be able to handle more and is just being restricted by motorola to extend the life of the components. I don't know. That would require a full teardown and looking up the specs for at least the major components, and 'ain't nobody got time for that'.

Just something to be aware of when ocing.
[Nexus 6 Android Development] baboomerang:
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 [MENTION=4392154]apophis9283[/MENTION] 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
[Nexus 6 Android Development] apophis9283:
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
[Nexus 6 Android Development] str8str:
My favorite is still umbrella core. Really good governor with all the qualities for performance and battery Love it

Straight Shooter
[Nexus 6 Android Development] apophis9283:
I will no longer support the 3.09 frequency. The max frequency will be 3.03
[Nexus 6 Android Development] baboomerang:
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?
[Nexus 6 Android Development] apophis9283:
No just logically it doesnt make sense. I mean 3.03 to 3.09. Its unnecessary
[Nexus 6 Android Development] apophis9283:
There is something in the pipeline that you all will love. Please do not thank this post. Wait until its time and Yoinx explains it all. I want every bit of thanks to go to him. He took a lot of his time to make this happen.
[Nexus 6 Android Development] str8str:
Gee no posts all day. The suspense is killing me

Straight Shooter
[Nexus 6 Android Development] :
That's because he gets over-excited and premature posts.

It's a medical thing.
[Nexus 6 Android Development] apophis9283:
Im gonna test the new stuff. Itll be awhile. I wouldnt expect a release tonight