yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] :
Thanks! Yours doesn't look bad either :) I've done builds before but this is the first one that has a window and stuff that is used for a purpose and not just something that I can game with. Doing your own build isn't only cool to learn but also gives you the best bang for buck that you can do. 5 years from now all you'll need is a Kaby Lake upgrade (if even that and just because your current mobo will support the socket), a new GPU and maybe RAM though I suspect 16 gigs will still be passable then. Intel isn't making any major advances in the processor front power wise so the only advances in the near future are better power management and more cores just for the sake of more cores. Considering gaming barely touches 4 cores atm and maybe 4 + 4ht with DX12 I think our 6700K's will be good for quite a while.

Yea you got a good one. I ended on the other end of the lottery. My chip has extremely different temperatures between the cores and even this HR-02 Macho Rev B is having a hard time keeping it cool. I'm still well within passable temps but I lowered my OC to 4.6 because it would go to almost 80 at Aida64 and higher with Intel Burn Test. The Corsair that's on it's way will probably help but I don't expect more than 5 - 7 degree during load so I'll probably keep the clocks at 4.6. Stability hasn't been a problem, just temperatures. I kept it stable at 4,7 but wasn't happy with how hot it went during gaming. I don't really fantasize about delidding my chip though that would probably bring it down a good 20 degree so I might toy with that idea once Intel's guarantee period is over after 3 years.

Sounds good, I'm doing my build environment soon-ish so I'll get to test then. I'm a bit surprised about the amount of RAM used though... considering that most gaming build guides tell you to put in 8 gigs "because more is unnecessary", then why is Xcom 2 giving me these readings (MSI Afterburner) during playing :D GPU temps are fine, CPU temps are fine but holy hell that game eats almost 4 gigs of vram and over 8 gigs of ram :D
[Android Builders Collective] theesotericone:
[MENTION=2770867]akselic[/MENTION]

Is that readout part of your keyboard? That's rad. I just use the onscreen nvidia reading during gaming. To be honest though I still game more on my PS4 than on my comp.

What linux distro are you running on it? I ended up on Mint 17.3 cinnamon. I tested just about every distro under the sun and it's the one that was the easiest to set up. Plus it is a really nice GUI with no KDE stuff. I like KDE as far as the GUI goes but I much prefer gnome apps to KDE apps. My mobo has a Creative Labs audio chip on the board and their linux support sucks. Mint picked it up well enough to actually have sound coming out of the audio port without me having to add a whole bunch of stuff to make it work.
[Android Builders Collective] :
Hehe yes. I'm still using my good old Logitech G15 which has its own mini display and MSI Afterburner still supports it after 8 years. Can't beat that! I'm waiting for a very specific mechanical keyboard to arrive to Finland (because I need the Nordic layout) and after that this dinosaur will be left to its hunting grounds as a backup keyboard.

Same here. When I was still running an AMD GPU (don't do it, just don't do it if you use Linux) Mint was one of the few that I could actually get working in a sensible timeframe. So that's what I stuck with. Plus I've used Mint before so it's not new to me. I find it very nice. In fact good enough that if it wasn't for games I'd replace W10 with it completely.
[Android Builders Collective] limjh16:
Boy nice build! Dat phanteks evolv tho

I'm going to be building a computer for my friend soon but he's unwilling to run linux due to "stability issues" since "windows is more stable" *ahem* but well its for my friend.
[Android Builders Collective] tuemdeluxe:
Running your YAOSP build since the beginning, immediately had an 11 days uptime without any slowdown, lag or issue. Definitely a rock stable build and it's running great with EX kernel (battery optimized interactive governor).

Battery lasts an average work day easily, normally I get between 3,5 and 5 hours SOT (on hammerhead I used to get 2-2,5 hours). If you're usage pattern includes long screen-on periods with medium brightness you can even get 6-6,5 hours.

Keep up the great work this build is amazing! :)
[Android Builders Collective] DroidIt!:
I've always wanted to build my own PC but always been a little afraid to cause what if I order all the stuffs, I slap it together and then I can't get the damn thing to work. :) I am pretty techy and grabbed a book on how to build your own, how to find out what mobo's work with what chip architectures, how to find drivers and all that good stuff, but always been a little apprehensive about taking the plunge. I hate my desktop, it just kind of sits there with a REALLY nice unused monitor but way underpowered. Lol, so that's why I have 4 win laptops and two macbooks. If you didn't know much about building your own PC and had never done it before, how hard is it in your opinion to do it from scratch?
[Android Builders Collective] Yank555:
Not very. You could do it with a friend who has done it already as a first time learning experience ;)

JP.
[Android Builders Collective] DroidIt!:
Oh, and I saw there's a ti VR unit and I didn't read TOO much but it looked like there's going to be a second gen, more vr purpose built ti coming out that looked like it is going to have performance closer to the titan without the insane price. Might be worth a look. :)
[Android Builders Collective] mslatter:
Hey JP,

I assume you're referring to the sources right? Or have you built slim6 for these devices?

Cheers.
[Android Builders Collective] Phazmos:
Oh man you should do it. Besides a mass cost savings, it really is pretty easy. Just follow the instructions - if you can do that, you're more than half way there.

Important notes;

Make sure the case well fit everything, especially the cooler. More room is better in a case. Easier to work on, better for cooling, and any upgrades.

Be real careful with the cpu. Don't touch any pins. It should be zif - zero insertion force - if it doesn't just drop right in, remove it and check alignment and the lock.

Phillips head is all ya need, just don't drop any screws. Get one behind the mb and you could be in for some grief.

The mb will come with all drivers needed to get everything working. And they are usually very well marked with what plugs in where.

Don't rush it, take your time. This is definitely one of those things that's well worth doing right the first time.

Research your components well. This should have been the first thing I mentioned!

I remember you from a while back - slim threads if I recall, I think you can handle it easily.
[Android Builders Collective] pkelly517:
Tom's Hardware has a section for building your own box, based on pricehttp://www.tomshardware.com/t/build-your-own/.

It's a good place to start. 2-3 years ago I built the $1000 box (twice) when my Linux mb died. It worked quite well, so I updated my Windows box with an improved video card.

I've since added ssd for the build directory. Build times are about 25 minutes now after a clobber.
[Android Builders Collective] theesotericone:
Bring two friends with you Droid!t and you'll be fine. Those two friends are Google and Youtube. I'd never built a comp before. Granted, I'd teardown and repaired a bunch of electronics so I have a pretty good working knowledge, but I've never actually put one together. So I spent a few days researching what I wanted and watching videos of the build process. By the time the components arrived I was pretty sure I had at least a 75% chance of it booting.

Give yourself plenty of time to build when the components do get there. I gave myself 2 days. It only took a few hours but it was nice not feeling like I had to get it done. I'm a pretty self-assured guy in my daily life, but I'll be honest, firing that thing up for the first time was nerve-wracking. Once you see it post though it's a huge sigh of relief and you can pat yourself on the back for a job well done.
[Android Builders Collective] Yank555:
Both, done the bringup and pushed flashable zips ;)

Have a look at my afh, there's a Slim6/Bringup 6.0.1 folder for all devices with ROMs inside, except for flounder of course.

JP.
[Android Builders Collective] indian84:
Hey JP, is Slim6 still bare bones? Or some features are added??
[Android Builders Collective] indian84:
OK. Will wait for the quick tiles and slim navbar to be added. :good:
[Android Builders Collective] mslatter:
Fantastic, cheers JP! :good:
[Android Builders Collective] dharmabm:
I am drooling over you guys' homebuilds! Just catching up on things after moving halfway around the world and haven't flashed anything in almost a month on either phone. Time to get updating!
[Android Builders Collective] a g bell:
Hola [MENTION=636871]ezio[/MENTION] please can you add dark mode if possible to your next hh build if you needs me to find the commits let me know if you can do this l won't link the song?
[Android Builders Collective] adm1jtg:
[MENTION=2033478]Yank555[/MENTION] just completely reloaded yaosp110 as was having what i feel was corrupted data partition issues and re-tested google dialer, it loaded and worked on wifi calling just fine. To refresh your memory, just in case, this was a question you asked about earlier in trying to get slim6 working if google dialer worked with wifi calling properly on latest yasop.
[Android Builders Collective] SteveMurphy:
You know, you could just use a layers theme and achieve what you want instantly with the build you're currently on. Magpie, Evolve etc all have the ability to emulate the 'dark mode'.

The dark switch isn't really implemented well at all by Google; a theme is the better route, as it has the option to theme multiple apps, whereas the switch only affects system settings.
[Android Builders Collective] Yank555:
Thanx, good info ;)

JP.
[Android Builders Collective] ezio84:
Lol, maybe i got crazy but honestly i'm missing that song! :D

The dark mode is a little crappy afaik, dark layers like Domination does the job in a better way:

and they also provide themeable gapps.
[Android Builders Collective] indian84:
Textile OS theme is also pretty sweet. You have option to chose light, dark and a mix of both. You can choose accent colours too. Red, Mango, teal, Ocean and tow other colours I can't remember now.
[Android Builders Collective] ezio84:
Nice too!!
[Android Builders Collective] a g bell:
Fine? https://youtu.be/uJKfxtYAt0s

Yeah l am using a minty layer already ? but l think l am getting issues with layers menu button takes like 5 secs sometime to exit apps unless its ROM related?just thought having dark option in dev settings would a easy clean add

But anyway https://youtu.be/uJKfxtYAt0s
[Android Builders Collective] indian84:
I have not come across issues with layers affecting performance. Can you check with some other theme?
[Android Builders Collective] a g bell:
Yeah its strange one only happens now and again mostly with YouTube exit will try without layers for few days and see
[Android Builders Collective] indian84:
Quick tip...

Uninstall YouTube overlay and see if that helps. Beauty of layers, you can uninstall specific overlay. :)
[Android Builders Collective] a g bell:
Yeah its not that l don't what it is will clean install got a strange log

https://drive.google.com/file/d/0ByRlwtAJ0pz0dno2b191ZDhvRms/view?usp=drivesdk
[Android Builders Collective] limjh16:
Un-Beauty of layers: Sometimes menu and text box text cant be seen. At least for me on slimLP.
[Android Builders Collective] indian84:
That's because SlimLP did not have full layers commits added. We were lucky to get some themes working properly on SlimLP because of native commits in LP.
[Android Builders Collective] limjh16:
Oh that explains. Well, moving on to marshmallow now. Hoping slimMM has all the commits!
[Android Builders Collective] indian84:
What device? I have been running YAOSP and Garry's PN Mod on my 6P. I can confirm everything works as it should..
[Android Builders Collective] limjh16:
Haven't built yet haha... Hoping it'll work.

Check my sig, I'm on i9305 aka galaxy s3
[Android Builders Collective] indian84:
LOL.. OK. All the best with that..
[Android Builders Collective] DroidIt!:
Lol, a LOT of posts since I posted. Ended up going to an art museum with the wife and spending the day out. :) Yeap, done pretty much all researches and stuff, just haven't taken the plunge but been thinking about it for quite awhile. I've always kind of wished there's a way you could build with laptops the same way you can do desktops. I like the mobility but taking a look at the gaming laptops you might as well have a tower sitting on your lap. :p I'm working on getting a new job with my dad right now. Don't know if y'all remember but I was a train engineer as in driving passenger trains and I want something more technical and PC oriented and that's what I'm going after. Well, that job is nothing but travel. So now I'll need to decide if I wanna do a tower or a REALLY nice laptop. I just dropped about $3,000 for a MacBook Pro with the dedicated AMD r9 graphics card and that does pretty good with Steam games but there's a LOT of titles missing. If I'm going to be on the road all the time I might trade in the MacBook for a Win laptop with the beefiest dedicated GPU in it I can find, something that can handle xcom 2 and witcher 3 and such no problems. I do like the force touch pad on the MacBook, that actually is really nice, but the gaming isn't really there. Lol, well I'll have to make a choice. I send in my resume tomorrow and we'll see how goes. If I get the job it'll pretty much be exactly the position I want. I'd be my own boss and be kind of a globe trotter and I LOVE travelling. :angel: Sorry for the long post...lol, I guess either way I'll come back here when I find out if I have the job or not and if you guys don't mind I'll either pick your brains for a tower or laptop you guys think I should look at. Thanks for the responses guys and hope all are having a good weekend. ;)
[Android Builders Collective] indian84:
Train Engineer? That sounds interesting.. All the best for getting the job dude..
[Android Builders Collective] ezio84:
Mmm. there are a lot of weird errors i've never seen :silly:

Thanks for the song :D
[Android Builders Collective] a g bell:
No worries?
[Android Builders Collective] Yank555:
Ok, so here we are on the Slim6 front ;)

Flounder not yet on Slim's github, if you want to play with it, check my github : device, kernel and vendor are there.

JP.

PS: Don't get fooled, all are 6.0.1, on the first screenies the ".1" label commit was not in yet ;)
[Android Builders Collective] Natakranta:
[MENTION=2033478]Yank555[/MENTION], since you are here, I have 2 things regarding YASOP. I've just did a fresh clean flash on angler with open gapps and theme ready gapps and SuperSU 2.71.

I'm getting Gallery app FCs. Need log I guess. Domination theme layer maybe? But there is not a specific layer in the theme for the gallery app.

And talking about Domination, SuperSU icon in settings menu list is not themed. Calling [MENTION=4603975]daveyannihilation[/MENTION]

:)

And Dave, you probably know there's a new Hangouts, I'm getting update in Play.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] DroidIt!:
For a future post? A table at a resturaunt? Your personality is reserved? ;)
[Android Builders Collective] ezio84:
With ART you could notice a little improvement when scrolling the page in some apps, at least is what i see.

With the Google stock recents panel it was more evident, the glow effect on the recents button in the navbar was laggy when using Dalvik, no issues with ART instead.
[Android Builders Collective] danarama:
I've got a cherry-pick best practice question for you all.

This is how I cherry-picked a commit.

I sync'd the slim repo then lest say I cherry-picked a commit from somewhere else into frameworks_base

I also forked the repo and cloned it elsewhere locally.

Then, I copied the the slim sync'd local frasmeworks_base into my local frameworks_base clone, picked up the differences and commited them back to my fork

I then use that commit ID to cherry-pick those changes every time I update my local slim repo.

Thats fine, that will work forever.

BUT, what if I then want to add a new cherry-pick to frameworks_base? I've sync'd Slim a few times so if I copied my locally sync'd frameworks_base into my local clone, it will pick up the cherry-pick as a difference but it will also pick up all the slim changes so I can't commit it.

How would you avoid this?

My thought would be to sync the slim repo and add my existing cherry pick

Then, remove my existing fork and refork it to my git.

Then reclone with the updated fork

Copy the local sync to the local clone and re-commit the old cherry-pick

Then make the new cherry pick, copy again to my local clone and commit that too...

Would that make sense? I dont want to accidentally commit slim changes into my fork.
[Android Builders Collective] ezio84:
[MENTION=2872010]rootSU[/MENTION]: replying you in the next post (if not ninja'd by someone :P).

Uploaded test builds if you want to try the new incoming Slim features:

- Configurable recents panel background:

Settings are now under "Interface" instead of "Accessibility";

- Lockscreen wallpaper (still under development by the SlimTeam), its settings are under "Interface" instead of "Security" and atm you can't set your realtime home as lockscreen background:

Usage: the "X" is to disable the feature, if you want to enable it tap on "Pick" to select the image, if you want to add a blur effect open the Lockscreen wallpaper settings page again and tap "Blur".

The build has also all usual additional features you can see in the 6th post of this thread (i just removed the buggy soft reboot option).

If you find errors or bugs with the recents panel and the ls wallpaper function, please report them to help the Slimteam too :highfive:

Download for mako: https://www.androidfilehost.com/?w=files&flid=18313 (under the "Test builds" folder)

Download for hammeread: https://www.androidfilehost.com/?w=files&flid=18315 (under the "Test builds" folder)
[Android Builders Collective] danarama:
I suppose there's nothing to stop me cherry-picking directly into my clone once I tested the cherry-pick worked in my local sync...
[Android Builders Collective] danarama:
Wow. Thanks for this.

So just a quick question...

Lets say I have a few commits in my forked repos...

https://github.com/SUroot?tab=repositories

Whats the best way to get to the state you mention above? Just do a clean repo sync without any cherry-pick, then git push back to my forks? All my commits will stay in place?
[Android Builders Collective] ezio84:
No, merge the slim framework_base with these steps:

That way, all your commits will be still there, git will just add new updated slim merged commits you don't have on the fork ;)

---------- Post added at 05:02 PM ---------- Previous post was at 04:57 PM ----------

PS: but before that you have to change projects in your local manifest , then repo sync so all your commits will be on your disk too, then merge the slim projects, then push the merge on the fork.
[Android Builders Collective] danarama:
OK I'll do it that way. Thanks very much again!
[Android Builders Collective] ezio84:
To be more clear, in your situation you have to follow all the steps i wrote, skipping the cherrypicking part.

So, that is you have to do:

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

Some edits on the post, see now :P
[Android Builders Collective] danarama:
Yup. I've edited the manifests and just doing my initial repo sync. Then I'll add and merge. Many thanks.

Presumably I have to cd into framework/base to git add, as I would a git clone?
[Android Builders Collective] ezio84:
Yep, git add, commit, push, remote, fetch, merge, etc... in the main project folder (e.g. framework/base).
[Android Builders Collective] danarama:
Great. One last noob question.

What are your steps to build the next weekly?

So you do a full repo sync, then gid add the slim repos you replaced with your forks, check it builds then push it back?

Do you bash script any of this or do it manually?
[Android Builders Collective] ezio84:
I'll repo sync to keep all projects updated.

I'll merge new slim commits to my local forked projects:

git remote add slimroms https://github.com/SlimRoms/frameworks_base
git fetch slimroms
git checkout kk4.4
git merge slimroms/kk4.4

and

git remote add slimroms https://github.com/SlimRoms/packages_apps_Settings
git fetch slimroms
git checkout kk4.4
git merge slimroms/kk4.4

(git remote add XX YY is not needed each time, git saves the added remote).

If there will be nothing new to merge, git will say "Nothing to merge, already up to date". So no need to push something to my remote forks.

If there will be updated commits on the slim gerrit (like the commit that change the weekly build number, e.g. https://gerrit.slimroms.net/#/c/13063/), git will merge them.

Then:

git push https://github.com/ezio84/packages_apps_Settings kk4.4
git push https://github.com/ezio84/frameworks_base kk4.4

to push the merged commits on my remote forks too.

Then to the build process:

. build/envsetup.sh && lunch
make installclean
make bacon -j#

I do it manually just because i'm not good with linux scripts :D
[Android Builders Collective] letmedanz:
Assuming you are in a state that you are happy with-

a) your local clone folder has all the features & commits you need

b) your slim source is synced as well.

then for future builds, you would-

make sure you have a remote pointing to Slim repo in each of your cloned folders.

do a git pull, git fetch, git merge & git push

repeat the above in all your cloned folders.

go to slim tree & sync repo

then all sources everywhere will be up to date.

build
[Android Builders Collective] danarama:
Hmm. OK thanks.

Still a little confused though.

dan@dan-Latitude-E6410:~/android/slimkat$ cd build
dan@dan-Latitude-E6410:~/android/slimkat/build$ git remote add slimroms https://github.com/SlimRoms/android_build
dan@dan-Latitude-E6410:~/android/slimkat/build$ git fetch slimromsFrom https://github.com/SlimRoms/android_build
* [new branch] jb -> slimroms/jb
* [new branch] jb-exp -> slimroms/jb-exp
* [new branch] jb4.2 -> slimroms/jb4.2
* [new branch] jb4.3 -> slimroms/jb4.3
* [new branch] kk4.4 -> slimroms/kk4.4
* [new branch] kk4.4-sdk -> slimroms/kk4.4-sdk
* [new branch] lcdbackup -> slimroms/lcdbackup
dan@dan-Latitude-E6410:~/android/slimkat/build$ git checkout slimroms/kk4.4
Previous HEAD position was 3deffab... GCC Version 4.8
HEAD is now at a620892... Add ro.slim.model for OTA purposes
dan@dan-Latitude-E6410:~/android/slimkat/build$ git merge slimroms/kk4.4
Already up-to-date.
dan@dan-Latitude-E6410:~/android/slimkat/build$ git push https://github.com/SUroot/android_build slimroms/kk4.4
Username for 'https://github.com': SUroot
Password for 'https://SUroot@github.com':
Counting objects: 11, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 969 bytes | 0 bytes/s, done.
Total 8 (delta 6), reused 0 (delta 0)
To https://github.com/SUroot/android_build
* [new branch] slimroms/kk4.4 -> slimroms/kk4.4
dan@dan-Latitude-E6410:~/android/slimkat/build$

I've done that ^^ Which seems to suggest there were some changes to write back.

But then when I go to github, I see no difference and it says I'm 2 commits behind slimroms. Not sure what I did wrong...

https://github.com/SUroot/android_build
[Android Builders Collective] Jonnyredcorn:
You guys are going to make my head explode. I was reading hoping to learn something and I found myself dialing 911
[Android Builders Collective] letmedanz:
Sorry, saw this late..

Did you get it worked out? i don't have any problems here wither..

i did face this once before, it was a setting in Mova...

i think i had selected 'choose color' or something like that..