yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Yank555:
Hi,

I've reviewd my battery icon / text code, and I was able to simplify it one more bit :

If anyone is willing to help test all is still working fine, would be much appreciated ;)

Patchset pushed : https://gerrit.slimroms.net/24334

Thanx, JP.
[Android Builders Collective] efan3719:
well i've tried different USB ports, ones on the front and the back, and i get the same thing. I'm going to try a different distro to see if anything will work and go from their. i wanna get to building.
[Android Builders Collective] Nucleonic:
Just built my latest yesterday. I'll be checking it out later in the week! Keep up the good work!!

What the heck. I'll go and build one now!!
[Android Builders Collective] inffy:
Cherry-picked, will be on my todays build

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

Btw, is there anyone who is building with lp5.0 and with a device that requires the lp5.0-caf branches?

How is the best way to handle two different bramches? Just do a two different folders and then repo init another with lp5.0 branch and another one with lp5.0-caf branch?

And how are you handling the upkeep, as some of the needed stuff is only available as lp5.0 branch.

Also is there a easy way to change to timestamp that comes to the zip name? I think it is UTC based now but I would like to have it UTC+2, is that configurable somewhere like vendor/slim/config/common.mk?
[Android Builders Collective] vampire36:
[MENTION=1277872]dankoman[/MENTION] : So if I understand correct...for a N4 if I select use significant motion sensor...then using this sensor the ambient display should work even in case of pickup :)
[Android Builders Collective] aoaleman:
[MENTION=251020]inffy[/MENTION], thank you so much for your shamu hoppyslim. This might be the first ROM that v4a works right out of the box. Thank you!
[Android Builders Collective] letmedanz:
i want to know too..i tried creating a lp5.0-caf branch, copied from lp5.0 with all my commits, but it wouldn't work.

spoke to [MENTION=4911350]RobbieL811[/MENTION] who said that you'll probably need to work on caf branch separately, adding all your commits separately

haven't had time and space on the drive to try it though, but that would work cos you are doing it all new..
[Android Builders Collective] vergilbt:
Big thanks to [MENTION=251020]inffy[/MENTION]

Love your last rro-build. Everything is working great...

Best cherry is v4a [emoji106]
[Android Builders Collective] RobbieL811:
Yeah. It's DEFINITELY best to keep 2 different directories. One for caf and one for aosp. No doubt!!!
[Android Builders Collective] angelcalibur:
thx for your help!

now, i have to learn, understand and try! :p
[Android Builders Collective] RobbieL811:
Just gotta do it man. The more you play w/ source, the more you'll get used to it.
[Android Builders Collective] inffy:
New hoppy is uploaded

CHANGELOG hoppySLIM v1.5:

Download: REMOVED as it bootloops

EDIT :Gapps packages also updated https://www.androidfilehost.com/?w=files&flid=25595
[Android Builders Collective] mgear356:
Bro I checked the MD5 and flashed gapps. Seems like it loops at animated screen and never enters.

Able to check?
[Android Builders Collective] inffy:
hmm strange...will check
[Android Builders Collective] PerfectSlayer:
For builders who picked network activity on status bar (@inffy ?) , I'm coding a new view to display network as a meter (like signal and battery).

I'm still testing it but it looks good =)

No more text with crazy jumping size > vector drawables instead (so layout do not seems to recompute at each change), more battery friendly (multiple handler task fixed), etc..

I also plan to add network output monitor if I find how to add it nicely to the meter display ^^'

I could share commits or post screens if you want to have a quick look ;)

Envoyé de mon Nexus 6 en utilisant Tapatalk
[Android Builders Collective] inffy:
Sounds awesome!

---------- Post added at 10:59 ---------- Previous post was at 10:45 ----------

Seems it won't boot. Removed the file
[Android Builders Collective] mj084:
Hello guys:)

Sorry for the stupid question:

I'm building SlimLP Mod with ezio84's sources, all fine (big thx to slimteam and all others here)!!!!

Now I want wo build with archi optimizations like hopper8 ;)

So what I have to do?:)
[Android Builders Collective] fraz14:
If you could share the commits it's would be perfekt.:good:
[Android Builders Collective] pkelly517:
I'll make a point of it when I get home.

Something happened to my FB repo which wouldn't allow me to build with your cherry pick. rm -rf was just the ticket to get me building again. Now it's time to pick again.
[Android Builders Collective] NovaSlim:
In case you guys have been living under a rock

Android 5.1 Confirmed
[Android Builders Collective] pkelly517:
vendor/slim/config/common.mk line 161.

It may take a separate line to do it. I'll putz around when I get home in front of my Linux box.
[Android Builders Collective] mgear356:
guys able to look into this for proximity bug for nexus 6? basically is if "check proximty before turning screen on" is checked, when there is a call and taking out phone from pocket, the screen will not light up

http://xdaforums.com/showpost.php?p=58601475&postcount=1781
[Android Builders Collective] Silentbob999:
I am surprised by that. They are branch remotely, why can they not be branch locally?

I am not building or anything but the way I will see it is working on an lp5 commit. Pushing it remote. Switch to caf branch. Cherry pick the same commit and resolve conflict. Pushing to slim caf branch.

It's just that you absolutely need to push your change to your own github (or any remote that you own) to be able to move commits from one branch to the other because when you switch branch the entire folder change.

At least this way you don't need double the size.

It just feel like it been made to be use like this.

Now I am saying that but it is without knowing the complexity of such a big project, I am far to understand how all the repo are link together.

---------- Post added at 07:46 AM ---------- Previous post was at 07:39 AM ----------

By the way, I am looking at this thread once in a while and I am very amaze by all the work you guys do. At the very beginning I did not predict that you would start to merge stuff on slim code. Congrats to all of you.
[Android Builders Collective] tysonwald:
it's like holding candy in front of a kid and then telling them they can't have it. keep up the good work and hopefully you figure out the bootloop issue so I can get my flash fix! LOL
[Android Builders Collective] dankoman:
mako doesn't use significant motion sensor to trigger doze at all. it uses the pick up gesture sensor. if you turn off the switch, it won't use any sensors to trigger doze at all (doze will only be triggered by notifications).
[Android Builders Collective] DroidIt!:
I wasn't going to say anything, but now I'm kind of offended. I like living under my rock [emoji14]
[Android Builders Collective] Skripka:
Hopefully 5.1 will have a Nexus6 graphics driver fix for battery drain. Franco said something about there being an easy-to-fix battery vampire lurking in the graphics system that needed a Google fix.

Funny just yesterday 5.0.3 was being talked about....now it is 5.1
[Android Builders Collective] :
Just finished a build with the new changes and it seems to work just fine. Went through all the settings and no problems at all. Thanks for the update :)
[Android Builders Collective] RobbieL811:
It doesn't work like you are saying. You will have issues. I mean, you can try if you want, but it's not gonna work. I'm on a server w/ 30 other SlimRom devs and NOT one of them does it this way. They all have seperate directories. B/c that's how you have to do it. Lol. One folder named SlimLP and one named SlimLP-caf and then you repo init respectively in those folders.
[Android Builders Collective] danarama:
Well if anyone is interested, turning off scrolling cache doesn't seem to make scrolling any smoother on Slim

https://github.com/one-love-420/and...453c9c62cc3fea416ea92dcd7af2d168c248b9#diff-0

I don't need it...
[Android Builders Collective] Grondinm:
yes save me from hunting for it
[Android Builders Collective] abhi03:
i am newbie and hence totally noob therefore dont know how to know github source of any feature.although i google for github source for force high end graphics feature but all i got the link of github of rom.
[Android Builders Collective] Mikulec:
[MENTION=2888538]letmedanz[/MENTION] - where did you get the Blur feature? Is it possible to cherry-pick it? Is it working with the Slim lockscreen wallpaper?
[Android Builders Collective] Garrykd:
I'm going to give it a shot...but I don't know what I'm doing, so I can't make any promises ;):D
[Android Builders Collective] soumoks:
Anything you put out, I'm ready to flash and knowing you I'm also obliged to include this sentence "please don't take any of the above words the wrong/dirty way" :D :D
[Android Builders Collective] ezio84:
Here's also the opendns script:

OpenDNS: https://www.androidfilehost.com/?fid=23622183712470987

You are lucky, here in Italy some providers are blocking Mega and other websites :silly:

LsW and see_through are both merged in letmedanz build but you can't use both features.

You can cherry-pick the commits from github.
[Android Builders Collective] Mikulec:
Yes I know euther u have LsW or Blur, I was currious if you can have both options in rom withou getting some errors. I cant seem to find the Blur commit.
[Android Builders Collective] ezio84:
Yes we have both, here are the commits you need:

https://github.com/ezio84/packages_apps_Settings/commit/462d927ddb33caa1583e53be288c4eac59760d22

https://github.com/ezio84/frameworks_base/commit/a7c616b8c29f2b4f6b119a4ea286912e67061281

https://github.com/ezio84/frameworks_base/commit/aae565f2c10e18ce3cb4a00e6bdf23a66da6e8f0

Keep in mind i adapted them to my build, the original ones in fusionjack's github had some lines for other features (omnirom lockscreen battery etc). If you don't have those additional features you should go fine with my commits.
[Android Builders Collective] mendozaram:
Hello [MENTION=2888538]letmedanz[/MENTION] im testing your build, looks pretty good but i cant find de Lockscreen wallpaper option? :p

Enviado desde mi Nexus 5
[Android Builders Collective] Mikulec:
Try: Settings/Interface/Lockscreen Wallpaper
[Android Builders Collective] mendozaram:
Nop, i found under settings-display-wallpaper-lockscreen , thx anyway

Enviado desde mi Nexus 5
[Android Builders Collective] vampire36:
The new look is awesome...Can you possible build for N4 :P

If not make a zip of those added stuff...look awesome switch and stuff...

Which is the font ?
[Android Builders Collective] letmedanz:
Will give it a go

---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
[Android Builders Collective] vampire36:
Thanx a lot will be waiting :)
[Android Builders Collective] letmedanz:
Twisted SLIM for Mako!

MAKO Version of Twisted Slim

DOWNLOAD

- https://www.androidfilehost.com/?fid=23622183712471295

Enjoy!

Note 1 - BootAnimation would still be stock, will update with next version

Note 2 - i don't have a Nexus 4, so i can't really test anything.. keep me posted

Link added to First Page Post

Features in first page post too
[Android Builders Collective] skidaway:
Thanks for making a build for mako. I have to complete some yard work before it rains, but I'm definitely going to give it an install later this evening. I'll report back after the install.
[Android Builders Collective] Garrykd:
First draft/proof of concept.....1080x1920....other resolutions to follow.....and I'll spice it up a bit too, at some point:

https://s.basketbuild.com/filedl/devs?dev=garrykd&dl=garrykd/Slim Builders Digests/bootanimation.zip

Copy new bootimage.zip to system/media (rename old bootimage.zip to bootimage.zip.bak)

Change permissions to rw-r-r

Reboot
[Android Builders Collective] srkmagnus:
error: "vendor/lge/hammerhead/device-vendor.mk" does not exist

Hello everyone!

I'm new to compiling Android from source and have been trying to build SlimLP for Hammerhead. However, after initiating the "lunch" then "Slim_hammerhead_userdebug: command I get the error listed below. If I can get some help or pointers as to how to solve it'll be greatly appreciated.

Information that may help: I am building from a portable hard drive and have my working file under ~/slimroms. Also, I've created a folder under .repo named "slim_manifests" and "slim_manifests.xml" file within that folder with the loonybin files provided via the helpful links within the 1st post.

I'm a bit lost as I'm new to building and don't know where to go from here. For what its also worth, I've copied and pasted/manually entered the Loonybin text into the xml file with the above error still occurring. Thanks in advance for any help or suggestions provided!
[Android Builders Collective] inffy:
After you have put the loonybin lines to your manifest file, have you done repo sync and checked that builddir/vendor/lge/ gets populated with the files? And you have put the branch as lp5.0?

Paste your manifest files here so we can have a look
[Android Builders Collective] RobbieL811:
Delete the slim_manifest stuff. That will get automatically generated when you run lunch. That's probably where you're running into trouble. What branch did you sync? Did you sync the CAF branch or the regular AOSP branch? When you run lunch, do it like this (After removing the slim_manifest stuff)

. build/envsetup.sh && lunch

Then a menu will appear w/ a bunch of devices and numbers. Find hammerhead in that list of devices and find the number beside it. Enter that number, then press enter. Then the next command will be to start the build. But before you start the build, go back and look into the .repo folder and you will see where the folder that I am talking about has been generated. Then place all the lines you need for your vendor files there. After that, you will need to do another repo sync. When repo sync is done, you will wanna run the above command again, and select the hammerhaed device number. Then run this.

mka bacon

And build will start.
[Android Builders Collective] inffy:
Been doing some testing after my todays build bootlooped.

I just did a completely stock built from Slim source. And still it gets stuck to slims bootanimation.

I can't think anything that could be the problem. My nandroid backup boots fine...
[Android Builders Collective] theesotericone:
It sounds like a good idea. I'll add my vote to you posting up some a screenie and the commit when you get some time.

The Slim team broke something?? Uneard of. lol

I did a build last night but won't be able to flash it until after work. About ten hours(hopefully) from now. I'll check then if mine boots if it hasn't been sorted.:cool:
[Android Builders Collective] Yank555:
I saw a tiny glitch, already fixed and testing, will push a patchset later tonight.

With battery percent next to icon (or text only), when you pull notifications down and battery level has changed since you last pulled notifications down, you'll see the old level at first and see as it's updated shortly after that while still pulling the notifications down.

Nothing bad, but well, not as it should be.

Fix is here if you want to add it asap but it's just a display glitch, so need to rush. Careful with cherrypicking, it's in my personal repo, I may have stuff in my base that is not in yours or vice-versa, the fix are the changes in these files : StatusBarHeaderView.java, PhoneStatusBar.java and KeyguardStatusBarView.java. The other two files are just comment updates.

JP.
[Android Builders Collective] inffy:
My build from yesterday works fine so your will probably work too
[Android Builders Collective] :
Ah I didn't even notice this until you mentioned it :P Not a big deal. I'll just wait for your gerrit push because I'm in the middle of a build anyway atm. Thanks!
[Android Builders Collective] srkmagnus:
Here is the loonybin info I copied and pasted into the slim_manifest.xml file (as noted in reply to RobbieL811's post below, I created the folder and .xml file myself)

And yes, I've done a repo sync after editing the slim_manifest.xml file and get no errors and see files within vendor/lge, just not the one listed within the error "device-vendor.mk". There is a file called "device.mk", however. The error only occurs after lunch then selecting the build for hammerhead...Thank you for the help - it's greatly appreciated and I've been learning a lot the past couple of days going through this thread.

I sync'd the regular AOSP branch. I won't be able to retry the build until tonight, but when I do, I will delete the slim_manifests folder and slim_manifest.xml file and follow your instructions. I will report back late tonight or early tomorrow - Thank you for taking the time to help.
[Android Builders Collective] :
Just to add to this before you give it another shot :)

1. Before doing the first repo sync did you initialize the repo with this line?

repo init -u git://github.com/SlimRoms/platform_manifest.git -b lp5.0

2. When you added the looneybin info, do you have the proper tags around it? As in this example:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheLoonyBin/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="lp5.0" />
<project name="TheLoonyBin/proprietary_vendor_qcom" path="vendor/qcom" remote="github" revision="lp5.0" />
<project name="TheLoonyBin/proprietary_vendor_broadcom" path="vendor/broadcom" remote="github" revision="lp5.0" />
</manifest>
[Android Builders Collective] Silentbob999:
I thrust you.

The complexity of an entire rom which contain many separate repo is probably way to complicated to move between branch with ease.

I still think that on github server those are branch, therefore they are in the same "folder". Git is a real beast.

But also don't understand how clone (repo sync) and init deal with multiple repo in the first place (never deal with manifest myself) .

You probably can repo sync the 2 branch together at the same time. But you need to be very careful and checkout from one branch to the other and always know where you are before changing stuff.

---------- Post added at 01:13 PM ---------- Previous post was at 01:05 PM ----------

You should always create a new branch for every modification/project you do anyway rights? That ways you separate everything and can deal with conflict before merging it back to the main branch... Getting two huge base branch should not change much thing in this matter no?

Again, no experience myself except with a project containing only 3 files lol... With small project like this playing with branch is pretty fun... With slim it’s probably scary lol
[Android Builders Collective] srkmagnus:
Yes to both.

repo init -u git://github.com/SlimRoms/platform_manifest.git -b lp5.0

was the first thing I did and everything went fine.

Thank you again for helping out. As I said before, I'm new to this compiling from source thing and have found it an enjoyable learning experience, and the help I've received is much appreciated. Actually, it's because of this Community that I decided to setup my Mac to build from source (which was a whole other learning experience). I forgot who said it, but someone said something like, "if you can flash a ROM, you can build a ROM". I'll let you guys know how everything goes once I get home and can double check that the above TheLoonyBin info is properly inserted to the correct folder/xml file.
[Android Builders Collective] inffy:
BTW why are u using an external drive?
[Android Builders Collective] JaylanPHNX:
Well that's just rude.[emoji87]

From my SlimTab Pro 8.4
[Android Builders Collective] :
Haha I've been holding that in for a hour and happy someone else said it before me :D
[Android Builders Collective] NovaSlim:
That's nothing

Now this

Is what you call misinformed and rude, not to mention

a. Their solution to "stability and advancement" is the CM theme engine

b. rro layer was thrown under the bus in the same post.
[Android Builders Collective] Nucleonic:
Is this problem still occurring?

[MENTION=2033478]Yank555[/MENTION] this might be the problem I've been experiencing today.

To summarize, I've successfully built from source both clean and with the two Yank555 battery icon commits. I get the same problem as [MENTION=251020]inffy[/MENTION]. Boots up past the Google logo, and onto the SlimLp animation, and stays there swirling round and round. My nandroid backup also works.

There were a lot of ffmpeg merges yesterday. Might that be the culprit?
[Android Builders Collective] Skripka:
I saw that and debated linking it.

There's a ROM off my to try list.
[Android Builders Collective] inffy:
Still a problem.
[Android Builders Collective] :
Last time I had weird issues was when I hadn't updated my local forks before building. Have you checked that this is not the case? Also tagging [MENTION=251020]inffy[/MENTION] here

I've been flashing testbuilds all day and not one of them has failed to boot.
[Android Builders Collective] a g bell:
Is kufi still part of slim very hard to know what's happening these days
[Android Builders Collective] NovaSlim:
There is still constant references to him in the N5 thread, but last I heard he broke his N5 screen and is now looking for a new phone.
[Android Builders Collective] JaylanPHNX:
Wow. And we haven't lost our lead developer. We've simply misplaced him. It happens sometimes.

From my SlimTab Pro 8.4
[Android Builders Collective] Skripka:
Are Slim devs like car keys then? :)
[Android Builders Collective] inffy:
As said I synced a totally stock slim repo's to another folder and it still won't boot.

I can't think anything else than that the problem is in the slim source
[Android Builders Collective] :
Check the local tavern. In 95% of cases that's the best place to find a missing German.

---------- Post added at 10:36 PM ---------- Previous post was at 10:33 PM ----------

Ah right yes, sorry missed that part. I wonder if this is occurring only on Shamu builds.
[Android Builders Collective] srkmagnus:
I have plenty of space on my MacBook to do the builds. However, it would require that I partition a case-sensitive drive and I don't really want to start partitioning my laptop. Being that my wife also uses it for various uses and stores a lot of information on it, I figured going the external drive route would be best to keep my android projects separate and have free range as to how I much storage I want to have for compiling source.
[Android Builders Collective] inffy:
You don't have to partition anything. Just create a volume for Android stuff. I have written few guides here on XDA how to setup build environment on a OSX machine. For cm11
[Android Builders Collective] :
[MENTION=251020]inffy[/MENTION] and [MENTION=4453916]Nucleonic[/MENTION] and any other Shamu builders. Out of curiosity have you seen this commit merged early today (or yesterday depending on timezone). How about trying to revert it and build and/or format the file system to f2fs before flashing?
[Android Builders Collective] Silentbob999:
Please BOLD, definitely not that rude lol

(If it is please consider that I am not native English speaking ok lol)

Actually I was sincere in the fact that I trust and respect Robbie. He's answer is right because it’s the easiest way. I am just surprise. You can delete a folder and start over without issue, you can fallow every tutorial with eyes close without worry, no doubt. But I was in the idea that it is probably just 2 or 3 extra command to do the same with a branch and you just need to be cautious about what people are asking you to do knowing you run a bit differently. I can be totally wrong.

I know some have super computer and awesome bandwidth. Did anyone of you already test it? Is it fast to switch between 2 branch that big (don’t know if it’s really big diff between caf and non-caf, maybe some of you have LP and KK together.. is it fast to switch between both ?)
[Android Builders Collective] inffy:
Noticed that but that would be a really stupid if you would have to reset everything/wipe everything just to flash a rom.