yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] docck:
Main thread means official SlimRoms topic (there is link to it in OP)
[Android Builders Collective] inffy:
Anyone here build Shamu/Nexus 6 builds here?

Do you have a problem with the mobile/cellural connection. I don't get access to my carrier at all. This happens with the Official Alpha build and with my own builds. Only way to get a connection to the carrier is to run stock rom.
[Android Builders Collective] Yank555:
YAOSP-MM v1.42_OMS

All devices are up for download, links updated in the announcement post.

JP.
[Android Builders Collective] Stevica Smederevac:
Italian, drinking cappuccino and lurking ;)
[Android Builders Collective] Jax Teller:
KrexusMod_mm-160829

Download for Angler: https://www.androidfilehost.com/?fid=24694152805483592

Download for Bullhead: https://www.androidfilehost.com/?fid=24591000424960989

Download for Hammerhead: https://www.androidfilehost.com/?fid=24591000424960990

Download for Flo: https://www.androidfilehost.com/?fid=24591000424960991

Changelog:

====================

08-29-2016

====================

* frameworks/base/

4b35094c QS: Add Substratum Shortcut Tile

0e661e2 OMS: Themes should be dynamically theming the power menu

dbfd872 AudioService: Allow system effect sounds to be themed

8bb3caf Allow on-demand window refreshes using "om refresh"

====================

08-28-2016

====================

====================

08-27-2016

====================

====================

08-26-2016

====================

====================

08-25-2016

====================

====================

08-24-2016

====================

====================

08-23-2016

====================

* packages/apps/masquerade/

78490af Merge remote-tracking branch 'nicholaschum/master'

fc81a8b Add appropriate license for our use-case

Main differences against the official Krexus build:

OMS Compatible

Added masquerade app

Removed some stuff that don't have a point existing on an unofficial rom

Hammerhead and Flo are built on dr1.6 branch

Removed layers backup script from Hammerhead and Flo cause Substratum handles that now

Default lcd density is lower for all devices. Angler (480), Bullhead (380), Hammerhead (380), Flo (280).

Installation and kernel:

- Get the latest bootloader, radio and vendor if needed from 6.x factory images.

- If you come from another rom do a factory reset and wipe system/caches. If you come from the previous build, a dirty flash should be enough.

- After flashing the rom zip in twrp, flash latest opengapps and SuperSU if you want root, then reboot and enjoy.

- Recommended kernels: ElementalX for all, blu_spark for Hammerhead
[Android Builders Collective] limjh16:
Well idk for your device but for me I had to have a change in blobs from nameless to haxynox
[Android Builders Collective] angelcalibur:
Thx limjh16 !

It's for GT-i9505, so nearly the same like yours.

Where did you change in blobs from nameless to haxynox ? :confused:

The only one issu i solved to build was in external/sepolicy, for the gatekeaper file (needed to add a # before the neverallow).
[Android Builders Collective] limjh16:
lol just realised that haxynox is for my phone only (its pure AOSP for exynos)

but try using permissive SElinux since you changed something from sepolicy, idk im just asking u to trial and error at this point lol
[Android Builders Collective] ezio84:
Can't say no about that statement :D
[Android Builders Collective] Phrodini:
Came back with those Popeye /quagmire arms
[Android Builders Collective] Garrykd:
A-gah-gah-gah-gah-gah-gah :laugh:... Giggidy:p
[Android Builders Collective] killer618:
Do you use your own Kernel in all these Builds? Idk which one to flash, slim or yaosp. hmmmmm:confused: :angel:
[Android Builders Collective] VictorLapin:
YAOSP has more features ROM wise atm. Kernels are pretty much the same (well, almost :)) if we talk about corresponding Slim and YAOSP builds. YAOSP kernels can have some experimental features that haven't been pushed to Slim yet, or won't be pushed at all.
[Android Builders Collective] indian84:
Well guys, I have done something that I cannot be proud of. I bricked my 6P. Heheheheh. From YAOSP, I flashed N DP5 and sideloaded the Nougat Final Build OTA. Used it for a couple of days, and wanted to return to YAOSP. So Followed the standard procedure.

TWRP and Root. Phone booted fine. Downloaded the ROM, GApps and MCT20F Vendor image on my phone.

Did all the required wipes and flashed Vendor, ROM and GApps. Tried rebooting to YAOSP and Bootloops Galore. The phone is stuck on alternating between Google logo and bootloader unlocked warning. Tried all the possible fixes. Flashing MCT20F Factory image, flashing N DF5 factory image. And all the possible things I could find in troubleshooting thread.

Turns out, I am not the only one with this issue.

So now I have to drive up to Huawei service center and get the phone fixed.

Sorry for the long one. Will be back on YAOSP tonight hopefully.
[Android Builders Collective] kantjer:
Damn, sorry to hear that.

That's the main reason I haven't tried N yet, too many horror stories.
[Android Builders Collective] mslatter:
Most of the major issues I've read about have been going "back" to MM. Not indicating that's been the cause 100%, but something doesn't like reverting. The more I read, the more I'm quite happy on N... I can't afford having an offline device right now =( Glad you've got a relatively painless fix ?
[Android Builders Collective] indian84:
I believe if Google can release Nougat Factory Images, a lot of the problems will be solved..

---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------

Well my phone is not fixed yet. After being on phone with Huawei rep for almost an hour, he suggested me to go to the service center. The problem is amplified by me not having proof of purchase handy.. Again, I am to blame.
[Android Builders Collective] ezio84:
Did you try the various fastboot erase commands before flashing M factory images?
[Android Builders Collective] indian84:
I did.

fastboot erase system

vendor

cache

boot

Did not work. Anyways, I have given up. Will take the phone to Huawei and let them do it for me..
[Android Builders Collective] ezio84:
Very weird. I agree, N factory images would be handy...
[Android Builders Collective] indian84:
Yup. I think they will release it along with September security patches. We will need vendor image to flash custom ROMs as it is. So let's hope it comes soon..
[Android Builders Collective] Ofthecats:
Format user data?
[Android Builders Collective] Yank555:
You're the second I know firsthand who had exactly that problem doing exactly what you did.

An let me guess, you still can boot twrp ?

I wonder if it's not maybe some firmwares that have been updated which don't get downgraded and cause the kernel to panic. I suppose it's not giving you a change at gettings a log ?

Maybe check if you can see the last kernel dmesg (/sys/fs/pstore/console-ramoops) if you boot into twrp using adb on twrp.

JP.
[Android Builders Collective] indian84:
Yup. Did that too. Nothing worked.

---------- Post added at 12:58 PM ---------- Previous post was at 12:20 PM ----------

I flashed MTC20F. All stock including recovery. Then I flashes twrp and was able to boot in to twrp.

Thanks for the suggestion, but I will try and take it to Huawei and have it retrieved. Shlube leaving office in an hour. And if they decided not to help me, it will try your suggestion

:svetius:
[Android Builders Collective] Randomsmack:
Have you tried skipsoft toolkit, it worked for me to flash to stock m and reroot, follow the trouble shooting guide in toolkit.
[Android Builders Collective] Yank555:
Have you seen this ?

http://xdaforums.com/showpost.php?p=66944195&postcount=8

JP.

Edit : might be something written to that same partition that keeps the oemunlock status, that would never be touched by twrp not factory images. And that revert image might just revert that data ... wild guessing here, but could make sense.
[Android Builders Collective] indian84:
Yup tried every possible things. I guess it's the vendor partition that's jacked.

---------- Post added at 04:52 PM ---------- Previous post was at 04:52 PM ----------

I will try it later when I'm home.
[Android Builders Collective] galakanokis:
I downgraded from NP5 to YAOSP the other day and while flashing in TWRP my phone made all kinds of weird noises, I thought it was a goner. It made sounds like a radio picking up just static, it would also let out the odd squeal every now and then. It flashed and booted but I'm a little nervous to flash something again. Anyone ever experience something like this before?
[Android Builders Collective] jayjay1234:
Have you Factory Reset with Stock Recovery already?
[Android Builders Collective] ccie.muyiwa@gmail.com:
Good day.

I have the Huawei mt2-c00 phone. Please kindly make a custom ROM for it, based on MM. THANK YOU.

I have searched for an updated ROM without success. I am currently using stock (Rooted) Android 4.4.2 on it.

Looking forward to a great ROM. Thanks.
[Android Builders Collective] indian84:
Yup. Have an appointment at Huawei service tomorrow.
[Android Builders Collective] kantjer:
Watch over there shoulder, you can be an unbrick consultant [emoji1]

Sent from my Nexus 6P
[Android Builders Collective] Yank555:
Keep us posted ;) I have a friend with the exact same problem who'd be quite happy if he doesn't have to rma his, as it's bought from amazon...

JP.
[Android Builders Collective] JaylanPHNX:
This thread is about learning to build for yourself. There are many useful tutorials in the OP section. You cannot just ask that someone build a ROM for some oddball phone they do not have.

From my Tab Pro 8.4
[Android Builders Collective] indian84:
Yup. Will let you know how it goes.
[Android Builders Collective] c3v1t:
A good Espresso is much better than a cappuccino... and much healthier for stomach and shape... :p

And a good prosiutto sandwich? give a little boost to your breakfast!!! :laugh:
[Android Builders Collective] angelcalibur:
Hello guys!

i have the same issu again...

i've made a logcat, anyone can help me to solve this ?

I've tryed to use another commit in ART, but it doesn't solved the issu.

here is the logcat : https://www.dropbox.com/s/tgpi8se9qn3za5d/logcat slim6 stable1.txt?dl=0
[Android Builders Collective] Yank555:
What exctly are you compiling ? Link to source ?

JP.
[Android Builders Collective] angelcalibur:
Salut JP! ;)

i build slim rom, with official source.

just mae changed for our unified S4 device (not supported by slim) and for TC.

here is my git :

https://github.com/angelcalibur/platform_manifest
[Android Builders Collective] csolanol:
Hi [MENTION=2033478]Yank555[/MENTION], i have a suggestion/petition :cowboy:

As slim6 got 1.0 stable version and android N is out and all efforts will go to N development a new SlimYAOSP mix would be really nice :angel:

What do you think?
[Android Builders Collective] Yank555:
Uhh ... ouch ... that will now be pretty messy lol ;)

As part of the things are already implemented in Slim, and behind the scences there's a whole lot of changes, so that would be hugely time-consuming :(

And ... well ... you know ... time is hard to find :angel:

JP.
[Android Builders Collective] ccie.muyiwa@gmail.com:
Thanks. That is my first lesson.

I want to learn. Keep you posted.
[Android Builders Collective] Ofthecats:
I don't know what you did on YAOSP, but it gave me the best SOT I've ever had...
[Android Builders Collective] Yank555:
Hmm ... well no idea, nothing major that would explain that, likely you have a good setup and apps seem to have behaved fine :D

JP.
[Android Builders Collective] Randomsmack:
https://goo.gl/photos/op6h3ZkHMSU7VaBc6
[Android Builders Collective] indian84:
Thanks. Just saw the post in the same thread. Will try and get it IP in a few hours.
[Android Builders Collective] angelcalibur:
Android 7 released (AOSP) for S4 device : :D

Screenshots:

Click on the screenshots to get full size:

​

rom can be dl here :

http://xdaforums.com/galaxy-s4/i950...d-source-project-nrd90m-t3453084#post68484183
[Android Builders Collective] Yank555:
That did it for my german friend !! His device is alive again !!

JP.

EDIT : This to be precise this did :

https://goo.gl/photos/op6h3ZkHMSU7VaBc6
[Android Builders Collective] indian84:
Merci JP.

My phone is up and running too.
[Android Builders Collective] Yank555:
Great, very glad to hear :D

I had that crap on my Note 3 (n9005) back at the time, had forgotten about it, other that I NEVER restore EFS even if I had forgotten why ... now I remember LOL

JP.
[Android Builders Collective] indian84:
The first Nexus I ended up bricking. Hahahahaha. Lessons learned.
[Android Builders Collective] indian84:
So, it turns out that this will probably be first and last Nexus I would brick.

Nexus will be Pixel come October 4th.

http://www.androidpolice.com/2016/0...oogle-home-daydream-vr-viewer-on-october-4th/
[Android Builders Collective] VictorLapin:
"Brick the Pixel!" :D
[Android Builders Collective] limjh16:
We don't even have a fully stable slim mm yet lol

Congrats anyways!! Now we wait for slimN
[Android Builders Collective] dankoman:
not to toot my own horn, but i totally called that one :p

---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------

like 6 months ago... though i'm sure my render is way off
[Android Builders Collective] VictorLapin:
[MENTION=1277872]dankoman[/MENTION] Daniel "The Nostradamus" Koman :D
[Android Builders Collective] angelcalibur:
Yes, and i always have my issu with booting the slim stable build...

After optimising app, i saw the the launching app, and i go back to the boot annimation...

don't understand what happen.
[Android Builders Collective] indian84:
Hmmm...
[Android Builders Collective] dankoman:
just playing around this morning :p

would be cool to have this logo branded on the back of the new pixels, but i'm not holding my breath...
[Android Builders Collective] indian84:
I believe they will have only G logo. But that Pixel art look's dope.
[Android Builders Collective] amphi66:
Now if only our FITs could communicate better than just Bluetooth Pandora w/ the new Pixel!
[Android Builders Collective] VictorLapin:
Just thought, someone like dbrand could make a case...
[Android Builders Collective] indian84:
[MENTION=2033478]Yank555[/MENTION]. Thanks JP.

Amazing battery on 6P. Feels so good to be back home.

All stock on latest YAOSP.
[Android Builders Collective] Randomsmack:
https://goo.gl/photos/oXGBrGT5zKL72rg78

Yaosp with NinjaThan kernel, zooper widget
[Android Builders Collective] limjh16:
[MENTION=4570506]indian84[/MENTION]

was this ur problem?

http://xdaforums.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
[Android Builders Collective] Yank555:
Yes
[Android Builders Collective] VictorLapin:
I wish there was a similar wallpaper with just the YAOSP logo :p
[Android Builders Collective] Yank555:
So I've taught msm_hotplug to gently ask msm_thermal if it's ok to up a certain core, I've added hotplug back into my angler kernel.

If you want to help test that build, here's where to download it : https://www.androidfilehost.com/?fid=24591000424962478

On a sidenote, the issue was that msm_thermal would check temps and act upon that every 1000ms.

msm_hotplug would do that every 200ms, and since msm_thermal will generate high load when it's throttling, msm_hotplug would reup the cores.

So in essence msm_thermal's work would only be applied for 0.2s every 1s ... temp rasises ... once it reaches 66° msm_thermal will panic and shutdown the device.

So I guess I've pushed mine there 2-3 times when I was using msm_hotplug before (my first and only random reboots on angler so far).

Preliminary tests seem fine, has been stable for me.

Still working on msm_hotplug, as I don't like the way the big cores are handled ... stuff cooking ... but more about that later, first I need to test that :D

JP.
[Android Builders Collective] indian84:
Will report back tomorrow. Out for the night.
[Android Builders Collective] DroidIt!:
Me too :D
[Android Builders Collective] Yank555:
If after that you're interested to try the next step ... here's with what I just done coding (v2) : https://www.androidfilehost.com/?fid=24591000424962569

The technical details :

As it was before :

when little cores went up to 3, 2 big cores where put online (no questions asked)

when little cores went up to 4, 4 big cores where put online (no questions asked)

when little cores went down to 3, 2 big cores where put offline (no questions asked, so back to 2)

when little cores went down to 2, all big cores where put offline (no questions asked)

So in fact, if we would set minimum online cores to 1, that would only allow for 1, 2, 5 or 8 core mode.​

As it is now (v2) :

little cores go up and down based on load (as before)

As long as not all 4 little cores are online, big cores stay offline (no questions asked)

when we reach 4 little cores online, and their average load is above online_load_big (default 80%), one big core is added

from here on, when the average load of whatever big cores are online is above online_load_big, we add another big core (till all are up).

now, we keep them up, as long as their average load doesn't drop below offline_load_big (default 20%), and we remove one big core (till there are no more).

If little cores drop below 4 online, big cores count can only go down, but not up, so we let them finish what they're doing until they fall below offline_load_big till all are off.

So now, if we would set minimum online cores to 1, that would now allow for 1, 2, 3, 4, 5, 6, 7 or 8 core mode.​

This certainly will need some more finetuning, maybe changing things, too, I've just coded it and gave it a small test, so be gentle if it's not behaving perfectly :D

JP.
[Android Builders Collective] Randomsmack:
Have you messed with zooper? Play store, dl zooper widgets with fonts add ons to build font library then you can logo any Rom your running.... I just do that when I'm on a rom long enough, like YAOSP, PN Mod, beltz etc
[Android Builders Collective] indian84:
[MENTION=2033478]Yank555[/MENTION]

OK then, I will try V2. Frank, I never had any issues on your previous array adding hotplug. My usage is not very heavy. So probably I won't have issues on your builds.

Thanks for the hard work.
[Android Builders Collective] kantjer:
Completely OT [emoji6] , I switched from Zooper to KLWP recently, steep learning curve but so much more that can be done with it.

Sent from my Nexus 6P
[Android Builders Collective] Randomsmack:
Sounds good, I'll try KLWP this could be the challenge I'm looking for.
[Android Builders Collective] Natakranta:
Flashed. Running fine, so far so good. I'll report if anything strange happens.

Thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] limjh16:
I'm just too lazy to use KLWP since there's a lack of pre made widgets available as compared to Zooper and I have to make the widgets myself lol
[Android Builders Collective] JRJ442:
There's plenty if you look in the right places.
[Android Builders Collective] Yank555:
Spent this morning continuing on msm_hotplug, and did change a few more things, did some code cleanup and extended the sysfs interface ...

So I've decided, given the changes, to now call it msm_hotplug v2 :)

YAOSP Angler with it can be downloaded here : https://www.androidfilehost.com/?fid=24591000424962790

Sources are up as well, I squashed commit msm_hotplug v2, so you need the following 3 commits in angler kernel to play with it :

Get rid of __cpuinit - squashed (jollaman999)

sched/cputime: Fix steal time accounting vs. CPU hotplug

soc: qcom: msm_hotplug v2

JP.
[Android Builders Collective] indian84:
I just downloaded previous build. :P

Now have to download again..

But you can always keep throwing builds at us. :P Much appreciated.
[Android Builders Collective] Yank555:
LOL

You can go ahead now, nuff for today, I'll be couch-surfing the rest of my sunday (or watching TV as normal folks would put it) :D

JP.
[Android Builders Collective] indian84:
Hehehe.. OK. Will download when I go home. Enjoy your Sunday.
[Android Builders Collective] JaylanPHNX:
And by couch surfing, you mean making YAOSP 7.0, right? Right?! (I'm just busting your ****) [emoji56]

From my Tab Pro 8.4

---------- Post added at 09:08 AM ---------- Previous post was at 09:05 AM ----------

Tagging [MENTION=6842057]nathanchance[/MENTION]

From my Tab Pro 8.4
[Android Builders Collective] Yank555:
LOL

As much as I couldn't get N sources soon enough, I've not felt inspired much to start playing with it, now I have them... maybe because we still have no official factory images for angler .... dunno ;)

This felt more important to me, as heat can be an issue on angler, and I wanted to mitigate it without affecting stability (link to msm_thermal) nor performance (my other changes).

JP.
[Android Builders Collective] limjh16:
*because

*heat

you're welcome.
[Android Builders Collective] indian84:
So if I understand correctly, source for Nougat is out. Which is needed for development. Even though factory images for 6P are not out yet, developers can still work on Nougat for 6P right?

But to flash cutom ROMs we need bug free TWRP and Nougat Vendor image.

Correct?
[Android Builders Collective] BakedTator:
Source is out, understock is now nougat, if you sideloaded the OTA for nougat you will have the vendor installed though you will still get that stupid error but it can be overlooked

If you flash nougat, make sure you are unencrypted and continue to use twrp 3.0.2-0 and all will be well
[Android Builders Collective] Yank555:
Well you can work on the ROM side.

For vendor (be it partition or the repo with whatever is not in vendor partition) we'd need a factory image, and there's no running N on 6P w/o vendor, not properly anyway.

TWRP, well either the -2 is a fix, but I can't find any changelog, or use -0 as that was working fine. Also I'd always backup EFS but never restore them anyway, so no issue there, any TWRP should do as long as you don't restore EFS.

JP.
[Android Builders Collective] BakedTator:
Someone has pulled the vendor out of the OTA. Or if you flash the OTA before flashing a custom aosp build, the vendor will be installed already.

Don't use any twrp other than 3.0.2-0...both 3.0.2-1 and 3.0.2-2 have bad bugs in them and are not to be used
[Android Builders Collective] Yank555:
I prefer to see factory images, personally ;)

Not that much in a hurry, M's running just fine with all I need for now...

JP.
[Android Builders Collective] BakedTator:
No worries, I was just giving some information on the matter. Would never rush a dev to build.
[Android Builders Collective] JaylanPHNX:
Is it just my memory, or is Google completely backwards this time in releasing source quickly and lagging behind on factory images? I don't know why I'm feeling super itchy to get nougat ROMs, I'm usually very patient about waiting until the features I like get included. I think maybe the fact that we're having to wait on Google before real work can get going is why it's bothering me.

I agree about getting thermal under control; it's the only complaint I've ever had about the 6p. It can get damn hot sometimes.

From my Tab Pro 8.4
[Android Builders Collective] kantjer:
I'm in no hurry to try N. Now testing Ninja Kernel on m with [MENTION=2033478]Yank555[/MENTION] hotplug. Running perfect

Sent from my Nexus 6P
[Android Builders Collective] JaylanPHNX:
Did you bring enough to share with the rest of the class?

From my Tab Pro 8.4
[Android Builders Collective] kantjer:
Lol, I'm not at home and can't upload. I'm now running a build with the previous msm hotplug commits. I will update to v2 asap. Nathan is also testing on his personal N build. I'm sure he will release a test soon

Sent from my Nexus 6P
[Android Builders Collective] nathanchance:
Yup, I'll add the commits from Yank and test today and if all goes well, I'll throw out a beta tonight.
[Android Builders Collective] harpin14789:
Would it be for Nexus 6 along with 6p or just the 6p?