yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Yank555:
Just a sidenote about YAOSP repos, now that I think of it, I sometimes fix derps rather in the initial commit, instead of making multiple micro-fix commits (I just did in the "pimp multiwindow" commit, removed a badly placed blank space), which means that I'll force-push my local repo over that github repo.

A simple repo sync will fail in that case afaik, so a force-sync will be needed whenever you resync.

I'll also always rebase on an AOSP base change (like when march security update will drop anytime soon).

So there will be a new branch (manifest will be updated, of course) and all the commits will be put back on top. I will always try to suqash the fixing followup commits in the base commit to keep it more or less 1 commit = 1 feature as much as I can.

Just to let know for those using YAOSP repos ;)

JP.

---------- Post added at 04:38 PM ---------- Previous post was at 04:34 PM ----------

I'd say, clean install from CD is likely the best option.

If your hardware can manage, my build box is a virtual machine, makes it easier to handle (no risk of losin data ... only a tad less performing), and also a no-fuss to move to the next hardware whenever you change it, just move the few VM files and you're up again ;)

JP.
[Android Builders Collective] ezio84:
Mmm no, I noticed that when the remote tree is force pushed, repo sync automatically handles it without the --force-sync flag.
[Android Builders Collective] Yank555:
Aha, that's good to know ... thing is I never repo sync my repos LOL, so I was afraid it would make a mess unless force-sync was used ;)

JP.
[Android Builders Collective] VictorLapin:
I always do repo sync --force-sync
[Android Builders Collective] ezio84:
;D

I'm too lazy to write all those letters :D
[Android Builders Collective] VictorLapin:
It's my build VM, so all I do there is repo sync and build. Tapping up arrow a couple of times is not so hard ;)
[Android Builders Collective] ezio84:
There's also the Ctrl+R trick in the terminal, Griffin) another Griffin's awesome hint :D
[Android Builders Collective] kantjer:
Ctrl+R FTW
[Android Builders Collective] Mikulec:
Noob question, whats the difference between simple repo sync and force sync?
[Android Builders Collective] Yank555:
It will force your local repo to match the remote repo, no matter what, at worst dropping local changes, without sync would fail.

JP.
[Android Builders Collective] indian84:
Hey guys,

Any one knows status of Slim6 development? I came from gerrit and saw Josue has been pushing a lot of commits, both open and merged. But it's primarily him and few other like Griffin and a couple more devs.

Would love to hear something positive about our beloved Slim..
[Android Builders Collective] sanguinesaintly:
** deleted **
[Android Builders Collective] robertm2011:
Ditto for the N6, there are other good ROMs out there that are being built with Slim features, though.
[Android Builders Collective] adm1jtg:
been extremely happy with yaosp from yank555 it posted in here, very slimlike feel
[Android Builders Collective] :
Thank you for these. Running perfect on Sprint 6p! I'll be following close. Love this thread. ?
[Android Builders Collective] dankoman:
what is this "slim" you speak of :confused: ?
[Android Builders Collective] Garrykd:
Not what, who...

[YOUTUBE]HBuk1HXcz1k[/YOUTUBE]

:p:p
[Android Builders Collective] indian84:
I see what you did there. :highfive:
[Android Builders Collective] theesotericone:
That is a question that has been asked a lot lately. lol Hope all you guys are doing well.:cool:
[Android Builders Collective] DroidIt!:
The whole "what happened to slim?" thing was talked about a while ago. There was some talk and if you look at my posts from 8 or so months ago in this thread you can get a few more answers. Normally I'd give a link, but in very low internet area at the moment...and I hope everybodies been good as well. School's been keeping me extremely busy, but I'm still flashing YAOSP. ;)
[Android Builders Collective] Yank555:
As in any ROM, yes unless someone maintains it. Personally, I don't know who nor if, been way too long ago I turned my back on Samsung / i9300 development.

I don't want to be rude or anything,

really

not my thing, so forgive me if I do sound rude here, but I have a hard time understanding the logic put on display here, again, tbh.

Do you actually really expect anything happening from

you

stating in here that

you

are done ? I mean, what exactly do you expect from this doing to whomever is part of the team (tears, nervous breakdown... ?), other than maybe getting an "overly defensive attitude" from them ? Which I could actually still consider being a nice answer, given the circumstances, honestly.

One way to see this, instead of b*tching, could be like just being thankful for what's been given to you (for free) so far, allowing you to use your device far beyond its OEM's support, and maybe be sad if it's not going on anymore.

But in no way can you display being angry, angry suggests entitlement, which you do not have, never had nor will ever get.

This is what's driving many devs far far far away from these forums (and the likes).

Just saying ...

JP.
[Android Builders Collective] DroidIt!:
Well, ultimately it's up to each of us what we run on our phones. I've said this before to the question "is slim dead?"...no I don't think so. Is it different than before? Well, yes. It's just different is all. Instead of having one main guy at the helm it's more of a community build. In some ways that's better than having just one guy at the top, particularly in this case because there's so many good guys who help build and they fill in and contribute to bug fixes and features when they get the time. So, instead of waiting for one guy to get home from work, things can still happen while the others are out. As far as Samsung support, most dev's won't support a phone they don't own. There's just no way to test or make it a reliable product before it's published. So, some devices have likely dropped off, but that's the nature of things as guys get different devices and move on. I'd wager most guys can't keep a phone just for devving purposes. I know when I get a new phone I sell the old just because I have no use for it. Well, that's my perspective on the whole deal from being pretty well in touch with the team back in the early N5 days and knowing all the guys that are basically in the lead now. These guys in the builder thread are a great group of guys and they support what devices they can with the time they have. They do the best they can I believe and I don't think they'd ever do otherwise. :)
[Android Builders Collective] sanguinesaintly:
deleted
[Android Builders Collective] Mikulec:
[MENTION=2033478]Yank555[/MENTION] , how do you do commits in YAOSP? Do you make commits only before making a build or do you make them as you have time. The reason why I am asking is, if I make YASOP build, will it have any changes or will it be just the build you posted last?
[Android Builders Collective] adm1jtg:
Man of us share the "sadness" but phone support as stated above is really based on an active dev having the phone and wanting to improve it. I was lucky enough to work with the slim dev who had a nexus s (very old even at that time) and we extended its life a good year or so. That said I really don't think slim team is being secretive or has some hidden agenda, my personal opinion is now it has been so long since they have been an active unit and since that "mishap" they simply are not a cohesive unit any longer. Organization and management of resources seem to be lacking and while there is still some work being done its bits and pieces and on an as time permits basis for all involved. Without the unity of a managed system and a dedicated team it will be very hard to ever recover the old slimroms as we know it.

I had been on slimroms since i ported with permission the original slimics for the vibrant. It was a one man show back then and it has been a long great ride. But many have moved on as happens with all great rom teams and rather then be upset or angry I have also moved on. Slimroms has shown us one unique style or rom that is powerful yet light and well thought out. Other roms are now stepping up to fill that void. If you look at roms like yaosp, pure nexus, aospip and dirty unicorns (there are many more i haven't listed) there really is not a feature or style missing. Its not slimroms but it doesn't need to be.

If I am right or wrong about slimroms the simple fact is they are not releasing roms atm and may never again. You can keep waiting in hopes that may change or start trying to find alternatives that suit your needs. For all intents and purposes slimroms is at least for the moment primarily inactive, that could change tomorrow or never. As I have said above I see absolutely nothing lacking in the above mentioned roms thus see no reason to wait on slimroms for a rom that may never come. Most of the devs i knew and respected on that team have moved on and this slimroms is not the same team it was in the kk days anyway.

*** Insert personal plug for YAOSP here*** as thats currently my fav of all the roms I have played with, not even looking at other roms now
[Android Builders Collective] sanguinesaintly:
I agree with you completely. Honest, refreshing and to the point. It is indeed time to move on and embrace the future rather than dwelling on the past. Thanks for your insight. :)
[Android Builders Collective] DroidIt!:
:) I'ma just gonna keep coming here for one of the [MENTION=2033478]Yank555[/MENTION], [MENTION=2095315]ezio84[/MENTION], [MENTION=2640853]Garrykd[/MENTION], [MENTION=5790246]VictorLapin[/MENTION] or any of the other guy's builds and be as happy as I ever was before. IMO their's are just as good as any of the Slim builds ever were...just my opinion ;)
[Android Builders Collective] sanguinesaintly:
Agreed - that was never in question - now I just need a new phone :)
[Android Builders Collective] Yank555:
I usually push stuff as I go, but might repush it as I continue working on it, so it might not be 'good to go', bugs not excluded ;)

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.97
[Android Builders Collective] Ofthecats:
Pay no mind to the unappreciative Buddy

Thanks for your contributions
[Android Builders Collective] adm1jtg:
March update is out does this mean a new yaosp is coming soon? [MENTION=2033478]Yank555[/MENTION]

:)
[Android Builders Collective] Mrcactuseater:
Number XDA rule is no ETA. I know you might just be curious, but it'll come when it comes

Tapatalk'd from my Twisted, Yank'd Nexus 5
[Android Builders Collective] adm1jtg:
I think yank555 knows i am just messing with him, His rom is so perfect for my needs I am bored to tears lol.
[Android Builders Collective] Yank555:
Just got up :D

Will start syncing sources in a few minutes, rebase tonight after work, dunno if I'll manage to get done in one go, but unless the new drop is a revolution, I should ;)

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.97

Edit : Sources are sync'ed (r17), rebase still ahead for tonight after work :)
[Android Builders Collective] dankoman:
what's taking so long?

ETA plz :angel:
[Android Builders Collective] Mikulec:
F*ck YAOSP, the development of that rom is dead. The sources are already up and he is not able to upload new build.

:p:D
[Android Builders Collective] Yank555:
I'm at it, I'm at it LOL

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.97
[Android Builders Collective] scoobyjenkins:
#patientlywaiting ?

Tapatalked that shiznit.
[Android Builders Collective] adm1jtg:
[MENTION=2033478]Yank555[/MENTION] can you add to your list of things to do eventually some call blocking?
[Android Builders Collective] Mikulec:
What about the Google phone app? That one should have the call blocking function.
[Android Builders Collective] adm1jtg:
I believe he is using the aosp dialer and in the naked rom there is no built in call blocking. Of course we could load something from playstore but would be way better to have it built in
[Android Builders Collective] Yank555:
Not sure yet, that call blocking is a pretty much an octopus in nature, needs bunch of changes a bit everywhere. Not saying no, but not on my roadmap for now. Added to the list, though ;)

JP.
[Android Builders Collective] adm1jtg:
ok not a huge deal as plenty of third party apps just thought it would fit with your redo of app opps. If its that big a deal your right leave it be. :)
[Android Builders Collective] Yank555:
Sources are up, angler zip about to upload
[Android Builders Collective] adm1jtg:
f5 f5 f5 f5 .... waits for shamu :)
[Android Builders Collective] Yank555:
Up next ;)

But takes ~45mins to compile...

JP.
[Android Builders Collective] Mikulec:
Anything new other than March security fixes?
[Android Builders Collective] Yank555:
- SlimActions: add torch
- BatteryLight: add separate color for fast charging
- Add native init.d support
- Rebase on AOSP 6.0.1_r17
- ad-blocking hosts file updated (2016-02-08)

Also, if you sync, it's a new branch, else you'll end up with 0.97b ;)

JP.
[Android Builders Collective] Mikulec:
good to know. thx.
[Android Builders Collective] adm1jtg:
Didn't even know we had ad blocking :D Guess I don't really need ad away anymore then.
[Android Builders Collective] adm1jtg:
Still hitting f5
[Android Builders Collective] Yank555:
Yep, sorry, got sleepy and went to bed (had to get up early today) ;)

Should be compiled, will upload shamu in a few minutes and start compiling flounder.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.97
[Android Builders Collective] Laggalot:
its been long, but im coming in here to say that fingerprint sensor for OP2 was finally made working on a CM13 ROM. Things are looking good now and Im really looking forward to more stable builds and maybe some Slimmallow goodness! :3
[Android Builders Collective] VictorLapin:
I suddenly realized we HAD it when I couldn't connect to Moscow underground Wi-Fi. "Looks like you are blocking the ads", it said... :D
[Android Builders Collective] dankoman:
sounds scary :D
[Android Builders Collective] indian84:
It's mother Russia. What do you expect??
[Android Builders Collective] DroidIt!:
Huh, init.d support is interesting...and hellooo [MENTION=2033478]Yank555[/MENTION] :) I might be mistaken but isn't most things run through su.d now? Just my curiosity was piqued when I saw that. What's the init.d support for?
[Android Builders Collective] ezio84:
PureNexus mod 6.0.1-20160309 :D

Download for Hammerhead: https://www.androidfilehost.com/?w=files&flid=50100

Changelog:

Update built-in supersu to System Mode 2.68beta version (for dirty flashers: remove supersu folders in both /data/app and /data/data before flashing)

Full rom italian translation

Removed feature/code: show purenexus icon in statusbar

From PureNexus official source:

- Merge tag 'android-6.0.1_r17' Aosp March update

- hammerhead: update blobs for 6.0.1 (MMB29V)

- hammerhead kernel: Merge tag 'android-6.0.1_r0.24'

- Arm/arm64 webview to 49.0.2623.63 & x86 48.0.2564.106

- DocumentsUI: use proper provider client for cut

- Advanced caf AppOps (PureNexusSettings - Tool and info - AppOps )

- Custom ambient display settings (Settings - Display)

IMPORTANT for a dirty flash of this build over previous ones: remove supersu folders in both /data/app and /data/data before flashing

Installation, tips, info: check the 6th post of this thread: http://xdaforums.com/showpost.php?p=55121776&postcount=6

PS: if you have problems, call A-team or clean flash.
[Android Builders Collective] morfances:
[MENTION=2095315]ezio84[/MENTION] lock screen shortcuts have been added?
[Android Builders Collective] liquidreign:
I have got to say that I appreciate everything you have done. I cannot believe people think they are entitled to something just because they want it. If want something bad enough and there is no one to help I figure it out on my own. Anyway more than planned to write, but please know I for one really appreciate what you do, and I am sure I am not the only one.
[Android Builders Collective] MZO:
bacon staging/mm6.0
[Android Builders Collective] indian84:
It booted fine. But it's pretty Vanilla AOSP. Zero customisations whatsoever. But felt smooth.
[Android Builders Collective] MZO:
It is "slim" :'D
[Android Builders Collective] indian84:
Ultra Slim. :P
[Android Builders Collective] Yank555:
Just old school init.d support by an old guy liking old ways of doing things :D It's for running scripts on late boot for whoever wants, taken care of by init.xxx.rc directly ;)

Personally I don't use it, but I also have the luxury to change what I want directly in the ramfs to fit my wishes, which might not be everybody's :D

JP.
[Android Builders Collective] MZO:
What can you expect in 240MBs lol. I'll maybe try Sultan's size reduction method lolol it'll give me 180-190MBs zip
[Android Builders Collective] indian84:
Not complaining dude. Was just a feed back. Good news is the build boots fine and felt smooth.

You can always cherry pick commits and add necessary features. I'm sure, the users here will be able to help/ suggest.
[Android Builders Collective] MZO:
Yeah. I'm joking too :D dunno if I will cherry pick because people at bacon haven't tasted lots of pure aosp :D I'll let Slim sort it out if they wanna add more features. I ran out of space else I was doing another ROM too lol...

P.S. I sent you a PM. Please send me about phone info as screenshot so I can make a thread :)
[Android Builders Collective] ezio84:
Not yet, haven't had time to look at it. But i found a nice lockscreen shortcuts bar on [MENTION=3445747]XXMrHyde[/MENTION] Darkkat (really interesting rom with some cool and different features from common ones), maybe I'll try to pick it :D
[Android Builders Collective] DroidIt!:
Makes sense :) I get ya. I still do some things just out of habit, like when flashing just because that's how I've always done it. Do it some new-fangled way like these damn kids now days and I get all messed up. :p
[Android Builders Collective] JaylanPHNX:
Hypo-slim™

From my SlimTab Pro 8.4
[Android Builders Collective] Garrykd:
..... and as usual, an angler version here: https://s.basketbuild.com/devs/garrykd/Builds/

:)

.
[Android Builders Collective] adm1jtg:
Hypo-Slim for all you crack flashers.... Get your fix here.....
[Android Builders Collective] DroidIt!:
Man! I don't know how you do it [MENTION=2640853]Garrykd[/MENTION]. Your change logs must take you forever to write up! :D :p
[Android Builders Collective] Garrykd:
Thank you for noticing:silly:...though it is starting to take its toll on me.

I wasn't exaggerating here :p

I think next time I'll just do this:

^^>>

....still leaves a bit of room for improvement too ;)
[Android Builders Collective] adm1jtg:
Go back a few posts and you can see how yank555 gets its done in the animated gif he postred
[Android Builders Collective] Garrykd:
Indeed. I don't know what the animal labor laws are in Luxemburg but over here that kind of exploitation is illegal!

:p:p
[Android Builders Collective] VictorLapin:
YAOSP-MM v1.00 for hammerhead, finally compiled :D

https://www.androidfilehost.com/?fid=24438995911975233

Changelog: https://github.com/YAOSP/manifest#changelog
[Android Builders Collective] Mikulec:
I saw that google released another update, MHC19I, are the sources for that up? Flar2 (ElementalX) mentioned that this update has some performance tweaks.
[Android Builders Collective] Yank555:
Have a look here :

https://source.android.com/source/build-numbers.html#source-code-tags-and-builds

The MHC19x branch seems 5X specific ... I use r17 = latest 'multi-device' for the time being, for ROM and kernel that is.

Edit : Take that back, I is for 6P, J was for 5X.

Google isn't making sense anymore, J is higher than I but older !? But no ROM Source yet, as for kernel, there are 3 branches for angler, don't know anymore which is which tbh.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.97
[Android Builders Collective] Mikulec:
That is weird cause there is MHC19I build available for Angler. :eek:
[Android Builders Collective] Yank555:
Yep (hence my edit ;))...

But how can MHC19I be newer than MMB29V ? Breaks the versioning logic ;)

We'll have to wait for AOSP tp drop...

But damn, I can't keept 3-4 full sources for my 4 Nexus devices !? Need more HDD and time to maintain all this :D

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.97
[Android Builders Collective] Mikulec:
lol, now you feel my pain with that HDD trouble. I feel like Google is just laughing now, 2 new M builds and one Developer N preview.
[Android Builders Collective] kantjer:
latest MHC19I image looks to be interesting for Angler

http://tinyurl.com/hm9xefw
[Android Builders Collective] Yank555:
If only they'd say which kernel branch goes with which ROM branch ... anyway, we'll have to wait for a new ROM branch to drop before being able to use any of these "advanced" features. Not that I ever had to complain about 6p performance tbh ;)

JP.
[Android Builders Collective] Mikulec:
Man, those N developer preview features are really nice, especialy the multiwindow. I wish theres a way to bake them in.
[Android Builders Collective] Yank555:
Not until sources drop, of course.

Talking about source drops ... I really need a coffee or two, strong ones that is ... :silly:

If we have MHC19J as 6.0.1_r22 ... that means "I" actually already had dropped before ... and guess what, it has as 6.0.1_r21 ... feeling a little stupid this morning :p

OK, so then, let the syncing begin, yet once again ... twice in two days, that's gotta be a record ;)

JP.
[Android Builders Collective] Mikulec:
I guess we will not see the N sources so soon, thats why I will probably flash the N developer preview on my Nexus 9. I just hope there are no big bugs, otherwise my wife will kill me (she uses the Nex9 as a "entertainment system" while she is feeding our son :D).

I am starting the countdown for YAOSP_1.01, lol.:good:
[Android Builders Collective] Ofthecats:
I'd recommend not flashing the preview. It may be unstable
[Android Builders Collective] Yank555:
I flashed it on my shamu, felt pretty stable for the time I've spent with it, but of course, it's a preview version ;)

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r17 v1.00
[Android Builders Collective] dankoman:
google probably in cahoots with the likes of seagate, westerndigital, etc ;)
[Android Builders Collective] Ofthecats:
I don't know, I wouldn't want to flash a preview version on a shared device lol
[Android Builders Collective] adm1jtg:
might give it a try in multirom config
[Android Builders Collective] t0mas_:
[MENTION=2095315]ezio84[/MENTION]

hi!

i just flashed your latest rom with added app opps. thanks for that, i missed id from old rom :)

but, i found some bugs, so i thought i let you know.

first one is just cosmetic, tabs on top are not visible when you first open the app, once i swipe right they show up

the other is app opps crashing when trying to set permissions for certain apps. the ones i found dont work are viber and beautiful widgets. both warn about not being fully compatible when disabling permissions in native permissions manager, so i suppose it has something to do with that.

nontheless, still a great addition, thanks

oh, i can provide logcats later in the afternoon
[Android Builders Collective] Mikulec:
lol, you uncovered great conspiracy here :laugh:
[Android Builders Collective] ezio84:
---------- Post added at 06:33 PM ---------- Previous post was at 05:49 PM ----------

PS: i've restored the Change-DPI-flashable-zip download if you want to quickly change the dpi value into the build.prop from twrp, before booting the device after the rom flash:

https://www.androidfilehost.com/user/?w=settings-dev-files&flid=51778

Yes i noticed the tabs thing, i'll check it :D

About those apps, yes, if you can please make a bug report, though AppOp is a cm/caf tool and still under development (sometimes they have added new fixes).