yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Yank555:
msm_hotplug v2 is for big.LITTLE devices.

But there's intelliplug in my shamu kernel if you want hotplugging.

JP.
[Android Builders Collective] indian84:
Monsieur JP,

About to flash today's build. I believe I have to flash the ROM and forget about it right? No need to do anything with kernel tuning app right??
[Android Builders Collective] harpin14789:
lol, I'm sorry. I thought that Nathan was going to release an N rom so I was excited. I was way out of context. :silly:
[Android Builders Collective] Yank555:
Yup, settings are handled in boot process.

LOL ;)

JP.
[Android Builders Collective] indian84:
Merci.
[Android Builders Collective] pkelly517:
Nathan,

Any chance you'll run that super script of yours to build AllTheThings? Your repository seems to be a little light lately ?

Thanks
[Android Builders Collective] indian84:
JP,

All done and setup. Let's see how it feels. Will let you know my impressions after using the phone tomorrow
[Android Builders Collective] VictorLapin:
Some testing of msm_hotplug_v2 on bullhead here as well
[Android Builders Collective] Grondinm:
Hey guys. I'm back. See my updated post #3
[Android Builders Collective] limjh16:
That took a little longer than expected (jk)
[Android Builders Collective] jesssiii:
Chance of getting the kernel with new hotplug settings in flashable zip I could use with PureNexus? Nathan's Ninja kernel has it?

Nexus 6P
[Android Builders Collective] nathanchance:
This one does: https://www.androidfilehost.com/?fid=24651430732237430
[Android Builders Collective] Aayushya:
Hi [MENTION=2033478]Yank555[/MENTION],

Just had a question, is your YAOSP based purely on AOSP, or does it have required CAF commits for non-nexus devices? I'd love to share this with my friends over at the Moto G forums. :)
[Android Builders Collective] Yank555:
YAOSP is purely based on AOSP ... you could try to use a CAF base and grab all the commits, but will be challenging.

Did that once, when Slim6 was barenaked, that was pretty easy, but now it would be way more challenging / timeconsuming.

JP.
[Android Builders Collective] csolanol:
Are sources adapted for msm8992 soc available anywhere?.

Ty.
[Android Builders Collective] nathanchance:
[MENTION=1863016]rachanta[/MENTION] has them on his Github: https://github.com/rachanta/racer-n5x/commits/nougat
[Android Builders Collective] csolanol:
Sorry but i don't se yank's msm_hotplug commits there. :confused:
[Android Builders Collective] rachanta:
[MENTION=2511007]csolanol[/MENTION]

RACER nougat branch has jollaman999's msm_hotplug adapted for fingerprint
[Android Builders Collective] Yank555:
Nope, those are what I started with I think, without that fp add'on, again I think.

msm_hotplug v2 has totally different handling of big cores, I've recoded that part, you can see most of the change here and here, but I squashed it to a v2 and continued updating from there, so don't pick those, they are incomplete and were just backups for my WIP.

Also I had previously updated msm_hotplug to respect thermal throttling (here) as on s810 you could reach shutdown temp when stressing the device as msm_hotplug would up cores faster than msm_thermal could down them.

To have the most current v2, you'd need to pick this squashed commit.

To use it on s808, you just have to change "BIG_CORES" to 2 here.

JP.
[Android Builders Collective] VictorLapin:
Will be pushed to YAOSP today, working pretty fine here.

Racer's msm_hotplug was a starting point, so many thanks to you guys. All credits provided, of course.
[Android Builders Collective] csolanol:
Ty very much.

Getting target_big may be used uninitialized error

Is it safe to build the kernel with KBUILD_CFLAGS: -Wno-maybe-uninitialized in Makefile?.

Thanks.
[Android Builders Collective] Yank555:
Do you have the line number ? Shouldn't be an issue to fix that warning, odd I don't get it on angler, as it's pretty not much liking any warning ;)

JP.
[Android Builders Collective] csolanol:
Error:

../../../../../../kernel/xiaomi/msm8992/drivers/soc/qcom/msm_hotplug.c: In function 'big_updown':
../../../../../../kernel/xiaomi/msm8992/drivers/soc/qcom/msm_hotplug.c:484:20: warning: 'target_big' may be used uninitialized in this function [-Wmaybe-uninitialized]
error, forbidden warning: msm_hotplug.c:484
/home/csolanol/stockslim/kernel/xiaomi/msm8992/scripts/Makefile.build:308: fallo en las instrucciones para el objetivo 'drivers/soc/qcom/msm_hotplug.o'
make[5]: *** [drivers/soc/qcom/msm_hotplug.o] Error 1
/home/csolanol/stockslim/kernel/xiaomi/msm8992/scripts/Makefile.build:455: fallo en las instrucciones para el objetivo 'drivers/soc/qcom'
make[4]: *** [drivers/soc/qcom] Error 2
/home/csolanol/stockslim/kernel/xiaomi/msm8992/scripts/Makefile.build:455: fallo en las instrucciones para el objetivo 'drivers/soc'
make[3]: *** [drivers/soc] Error 2
/home/csolanol/stockslim/kernel/xiaomi/msm8992/Makefile:822: fallo en las instrucciones para el objetivo 'drivers'
make[2]: *** [drivers] Error 2
Makefile:130: fallo en las instrucciones para el objetivo 'sub-make'
make[1]: *** [sub-make] Error 2
make[1]: se sale del directorio '/home/csolanol/stockslim/kernel/xiaomi/msm8992'
build/core/tasks/kernel.mk:264: fallo en las instrucciones para el objetivo 'TARGET_KERNEL_BINARIES'
make: *** [TARGET_KERNEL_BINARIES] Error 2
[Android Builders Collective] limjh16:
You could still try same commits for purenexus, since they are SOMEWHAT the same. It can be a good starting point.
[Android Builders Collective] ezio84:
Something about the SuperSu drama :D

Today i tried phh's opensource superuser (CLICK) on stock N, it works like a charm.

I've done it following the manual way:

- remove supersu (steps HERE );

- flash the the modded boot.img from HERE (if you want to keep encryption, the "noverity" one is enough)

- reboot

- install the supersuser manager from playstore (CLICK ).

To automate the process, without the need to flash the modded boot.img (useful if you have a custom kernel), you can just use the superuser-rXXX.zip file from HERE: it patches the existing boot img you have.

In the zip there's also a customizable config.txt file where you can enable/disable eng, nocrypt and dmverity (by default it sets the "eng" variant of SU).

The Playstore superuser manager is still needed.

PS: to handle systemless mode, xposed and Pay compatibility, take a look at Magisk: CLICK.

I haven't tried it, too lazy :D :D
[Android Builders Collective] Yank555:
Are you certain you actually have msm_hotplug v2, because for me big_updown starts at line 512 ?

Anyways, you should be good if you replace that function with this :

static void big_updown(unsigned int fast_lane_req)
{
unsigned int online_little, online_big;
unsigned int target_big;
unsigned int avg_load_little_cpus, avg_load_big_cpus;

online_little = num_online_little_cpus();
online_big = target_big = num_online_big_cpus();

if (online_big > 0) {
avg_load_little_cpus = 0;
avg_load_big_cpus = load_at_max_freq_big() / online_big;
} else {
// if no big core is up, use average of all little cores as load average for big kick in
avg_load_little_cpus = load_at_max_freq() / online_little;
avg_load_big_cpus = 0;
}

if (fast_lane_req == 1) {
// If fast lane has been requested, up everything we have
target_big = BIG_CORES;
} else if (online_little == LITTLE_CORES) {
// Only if all little are up, up big cores depending on load, one at a time
if ((avg_load_little_cpus >= hotplug.kick_in_load_big && online_big == 0 ) ||
(avg_load_big_cpus >= hotplug.online_load_big && online_big < BIG_CORES) ) {
// if the average load of big cluster is above threshold,
// up one more big core if there is one left to up
target_big++;
} else if (avg_load_big_cpus <= hotplug.offline_load_big && online_big > 0) {
// if the average load of big cluster is below threshold,
// down one more big core if there is one left to down
target_big--;
}
} else {
// If not all little cores are up, big cores can only be down'ed
if (avg_load_big_cpus <= hotplug.offline_load_big && online_big > 0) {
target_big--;
}
}

if (online_big != target_big) {
if (target_big > online_big)
big_up(target_big);
else if (target_big < online_big)
big_down(target_big);
}
}

Will update and repush the branch.

JP.

Edit : Repushed branch, new squashed commit is here.
[Android Builders Collective] angelcalibur:
Hi all!

i have a little question!

As i see, some builder here make build for differents device (like Yank555 for exemple), and i want to know if i can do this for our AOSP 7 for :

Samsung S4 device

Samsung galaxy note 10.1 2014 edition (sm-p600)

LG Gpad 8.3 device

But this in the same folder:

Home/Angel/AOSP7/

So with that, i will have in device :

Samsung (same folder for my S4, galaxy Note, Galaxy S1 if i build for it...)

LG

and another maybee

Do you think it's possible? it's just to save space in my Hard disk.
[Android Builders Collective] VictorLapin:
Sure it's possible, you just need to have all devices specific repos and do a lunch between compiling
[Android Builders Collective] angelcalibur:
ok, thx for your answer victor! :good:

I will sync source tonight and try it!
[Android Builders Collective] limjh16:
What drama is there about SuperSU? All I know is to keep 2.76 since its last version chainfire will release by himself lol. But by using some SU other than SuperSU some settings will be missed, such as rom nightlies survival script, or su.d
[Android Builders Collective] ezio84:
Yes 2.76 and .77 work well now, but having a good opensource alternative for the future if things will get worse is not a bad idea [emoji14]
[Android Builders Collective] rignfool:
You should...

In a nutshell... It mounts a 'magisk' image that allows you to add things to system, without actually adding them...

It allows system level mods to remain after initial install, since they are installed elsewhere and mounted during boot...

It also allows for modifying the build.prop during post-data-fs or something like that...
[Android Builders Collective] limjh16:
.77? Is that by CCMT?
[Android Builders Collective] ezio84:
Interesting! Will try it too.

---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------

Nope, last beta still by CF ;)
[Android Builders Collective] Yank555:
Well there a few thoughts that pop to mind :

2.76 will die with N coming, and you won't have a Chainfire made SuperSU left, you will have to move on or along

using bake-in su as I do on YAOSP, settings will survive ROM update just fine, and no need to flash anything neither ;)

ok there is no su.d, but who actually uses it (and in case, there's still init.d, or it could still be added easily)

JP.
[Android Builders Collective] limjh16:
1. I'm not getting my hopes up for n lol

2. Yup bake in su is koush one actually IMO, at least CM one is

3. su.d for MEEEEEall arise users!!! I know [MENTION=5790246]VictorLapin[/MENTION] is one
[Android Builders Collective] Yank555:
Well he has it running using baked-in su I think, so I suppose it's working using a different script running system.

[MENTION=5790246]VictorLapin[/MENTION] or you running SuperSU ?

JP.

Note : using the same as Slim, and I think it's same as CM, haven't checked.
[Android Builders Collective] limjh16:
Yup then it's koush su, I checked alrd lol. Phh su is adapted from koush so its about the same.
[Android Builders Collective] VictorLapin:
I don't use Dolby Atmos Add-on, and Viper runs pretty fine with baked-in su and selinux enforcing.
[Android Builders Collective] limjh16:
what about setprop? Or do you just use tweakprop? or none even??
[Android Builders Collective] VictorLapin:
Default stuff
[Android Builders Collective] limjh16:
oh well lol guess im the only guy using su.d

I guess ill have to settle for tweakprop for N lol
[Android Builders Collective] VictorLapin:
And then "su.d for all arise users!!!" slogan transformed into "su.d for me!!!" :D:D
[Android Builders Collective] limjh16:
http://xdaforums.com/showpost.php?p=68540406&postcount=12515

:)
[Android Builders Collective] JaylanPHNX:
I use a couple su.d mods. ARISE and a script that keeps my theme ready apps from showing updates in Play Store.

I have to 6p.
[Android Builders Collective] indian84:
[MENTION=2033478]Yank555[/MENTION]

Hey JP. Chiming in to report about the latest build. I'm enjoying it a lot. I'm at almost 24 hours of usage on first charge cycle, with more than 3 hours of SOT and 45% battery remaining.

I was planning to go Stock Nougat for few days. But nkw don't want to move to Nougat.

Can't wait to see what you cook for YAOSP 7.0.

Cheers.

:highfive:
[Android Builders Collective] Yank555:
Good to hear it's doing great. Yep I feel a better SOT as well. Although I had one random reboot again ... no idea what it comes from.

Anyways, msm_hotplug v2.1 is cooking ... some simplification, and some a little more advanced things, like downing the least loaded big core first (not necessarily in the order cpu7,cpu6,cpu5,cpu4) plus some code review ... let's see if I didn't derp somewhere, quite a few changes again ;)

JP.

Edit :

If you wanna test, YAOSP angler can be downloaded here.

The commit for 2.1 can be found here.

Note, I still have a few things I want to change, but not tonight or I know I'll get little sleep and work tomorrow ;)
[Android Builders Collective] JaylanPHNX:
Ah, so you're having a few random reboots, too. My wife had a couple and I was worried maybe some setting I'd tweaked for her had caused it.

From my Tab Pro 8.4
[Android Builders Collective] galakanokis:
I haven't experienced any reboots yet, have used the phone a fair amount since I flashed it yesterday as well. Very little idol drain, 1% overnight which is nice as I have been experiencing some terrible drain when connected to 5Ghz wifi.
[Android Builders Collective] Yank555:
Nope so far only rr I ever had on angler was with hotplug in and active ... let's see if this 2.1 helps, not that I've run into anthing major ... except the spinlocks I could remove.

JP.
[Android Builders Collective] Mikulec:
Well I tried Ninja kernel with the hotplug baked in, and its laging like hell if you do some heavy tasks like playing games. I wonder if I have screwed some settings or nobody plays games. :)
[Android Builders Collective] Yank555:
I don't, but beta tester does and reported lower temps while gaming, didn't report any lags...

Maybe thermal throttling ?

JP.

Edit : My settings : https://github.com/YAOSP/device_huawei_angler/commit/07b37bf18d82861c2cbb4032948711872ad61638
[Android Builders Collective] Mikulec:
Definitely thermal throttling. Will try other games that doesnt stress the CPU so much.

EDIT: checked the settings in Kernel Adiutor and the ones that are there are the same as yours (except the "IO is bussyô, that was turned off)
[Android Builders Collective] ariefabuzaky:
In last line msm_hotplug/load level " 3 160 100" i cant sett like your value
[Android Builders Collective] Yank555:
It's load_levels ... works here.

JP.
[Android Builders Collective] jisoo:
Can I take this opportunity to suggest using phh's SuperUser as built-in? You only need to include the following 3 example commits:

- system_sepolicy additions: https://github.com/kimjisoo/system_sepolicy/commit/5443db6cf15de7f9bd2eb56542f3a4f4ac96e7e9

- system_core additions: https://github.com/kimjisoo/system_core/commit/2049ab2a4591b53d7a02fd362d50c51ac5ca1884

- adding su to device ramdisk (need to do for each device you build) https://github.com/kimjisoo/system_core/commit/2049ab2a4591b53d7a02fd362d50c51ac5ca1884

Obviously you also need to add the SuperUser.apk either from Play Store or F-Droid (or build yourself).

I've been using this in my MM builds, and right now have it running in my Nexus 7 Nougat build as well. It works well, and I really wish ROMs would move over to this (or CM's in-built su which is fine as well) instead of recommending users flash a closed-source implementation like SuperSu.
[Android Builders Collective] limjh16:
well CM's built in su is also slim's built in su which is YAOSP's built in su which is Koush's SU
[Android Builders Collective] theesotericone:
Right. Which at one time was the go to SU. Then about three years ago koush stopped work on it altogether. That left the ball in CF's court. A smart guy that was always there when needed with a working SU. Also the guy that came up with a root method for almost any major phone on XDA. I like, trust and respect CF. The funny thing is, since we all did, no one felt a need to question why the single biggest vulnerability to our phones was beyond scrutiny, ie closed source.

What's funny to me now is the hustle to find an alternative to SSU. Sure he sold it. Sure the new company is questionable. Sure they could create some nasty stuff to gather personal info. But why now? Why not three years ago? That's how much trust we put in CF. Now that he's stepping away from SSU it's like the sky is falling. The sky's been falling for years it just took him selling his project for us as a whole to see it.
[Android Builders Collective] ThrillerAtPlay:
On that note, does anyone know if there will be any official or unofficial forks of TWRP that replaces the SuperSU install with Phhusson's Superuser? Or better yet, ways to bake it into builds from source?

If not, does anyone have the list of commits to patch the built-in CM/Slim/Slim derivatives into AOSP Roms? I have banging my head against the keyboard trying to get Slim to correctly initialize the radio/gps socket on Clark. I'd be happy if I could get build PureNexus with root built-in.
[Android Builders Collective] Yank555:
You might have a look in my repos, that's exactly what I have.

It's squashed with PGM, so it won't go staight in, but since PN has PGM already, shouldn't be a biggy to get it in and will save you the hassle to go hunt the various commits on Slim's repos.

JP.

---------- Post added at 07:01 AM ---------- Previous post was at 06:55 AM ----------

Well community is partly built on trust, CF has a good reputation and since he was no company, his intentions were deemed 'honorable'.

Now that is no more the case, a company will not put efforts into a product w/o return on invest in form of profit, honor or public recognition are irrelevant.

Once the app is sold (SuperSU pro) for a few bucks, that user brings no more profit ... hence they will (have to) be looking for other ways of income, and many things are possible, esp. given root opens all doors.

But by that I don't mean (or rather hope) stealing information to be part of those things, but indeed, who knows.

Koush's su is working fine, and built from source, manager baked into PGM hence the ROM, thus my choice.

JP.
[Android Builders Collective] ariefabuzaky:
Are you using governor profile or you let it stock ?
[Android Builders Collective] indian84:
All stock..
[Android Builders Collective] Aayushya:
Hi again [MENTION=2033478]Yank555[/MENTION],

So I went ahead, took the challenge and tried to make a CAF version of YAOSP.

Everything went pretty fine, well, almost.

I get an error at frameworks/opt/telephony, and I can't find a fix for it. I'd really appreciate help from you guys.

Here's the error: http://pastebin.com/HvV48tEL

Here's the GitHub Organization I made for the purpose.

https://github.com/YAOSP-CAF/

frameworks_opt_telephony: https://github.com/YAOSP-CAF/frameworks_opt_telephony

Any help will be highly appreciated!
[Android Builders Collective] Bongofriend:
Maybe this class is missing?
[Android Builders Collective] Aayushya:
Woah, you're right, I don't know how I missed that! :silly:

Thanks a lot, building again to see if its working now.
[Android Builders Collective] dankoman:
why not just call it YCAF instead of YAOSP-CAF? ;):D
[Android Builders Collective] Aayushya:
Hmm, :confused:

Didn't really give it a thought, YAOSP-CAF seems wrong lol, but you know, people will know its the CAF version of YAOSP just by looking at the name :P
[Android Builders Collective] dankoman:
lol good point
[Android Builders Collective] Aayushya:
New error popped up now :c

http://hastebin.com/ramoxazene.m

Help will be really appreciated!
[Android Builders Collective] Yank555:
Sorry ... was watching tv :angel:

Never seen that codebit, nothing I ever remember playing with ?? Maybe some merge issue ?

Saw you posting a link to github a few posts back, I'll try to have a look, but not really sure I'll be able to nail the issue...

JP.

Edit : Well I forgot how different CAF telephony is compared to AOSP ... what is the base you used before adding YAOSP stuff ?
[Android Builders Collective] Aayushya:
Thanks a lot, I hope we can all contribute to get a CAF version up and running soon! :D
[Android Builders Collective] Yank555:
YAOSP-MM Changelog v1.43

One more small update :

OMS/Substratum support

Security : Show negociated charger max current on lockscreen (in mA/h)

Mobile Networks - toggle to show/hide data connection in signal icon when roaming (instead of "R")

Angler / Bullhead kernel : updated hotplugging to v2.1

Note about angler hotplugging ... I've given msm_hotplug a major overhaul (as very well documented in this thread ;) ), big core handling is totally changed compared to what it was, simplified a few things, so far was stable for me, but 2.1 is about 1 day old, so might be too soon to tell for sure.

Note about OMS/Substratum & layers ... beginning with 1.43, YAOSP will be OMS/Substratum only, we need to move on ;)

Sources, changelog and download links as usual : https://github.com/YAOSP/manifest#changelog

Note : Angler, Shamu, Hammerhead, Flounder an Flo are up, Bullhead by Victor to follow.﻿

---------- Post added at 22:03 ---------- Previous post was at 21:52 ----------

If I see it right, you are trying to compile the CAF base you'd like to use ?

JP.
[Android Builders Collective] modernbummer:
Thanks, JP. Been using YAOSP (Shamu) exclusively since the SuperSU controversy. I appreciate your work.
[Android Builders Collective] Aayushya:
I'm trying to add in the CAF bits to YAOSP, so that we folks can get to use your work as well. :)

EDIT: BTW, I guess it WAS a mismerge, I'll fix it!
[Android Builders Collective] Yank555:
You'd better go the other way ... find a 'naked' CAF base and add YAOSP changes on top.

JP.
[Android Builders Collective] VictorLapin:
Yeah, just bootlooped my bullhead during the test run of the updated kernel, so it will be some time...
[Android Builders Collective] Ofthecats:
I'm also unable to set these values, and 160 is above the max for the relevant setting according to your git.

I use exkm and ninja kernel 3.4rc2 which has msm_hotplug merged