yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] csolanol:
This is what we overlay about hardware keys:

<!-- Hardware keys present on the device, stored as a bit field.
This integer should equal the sum of the corresponding value for each
of the following keys present:
1 - Home
2 - Back
4 - Menu
8 - Assistant (search)
16 - App switch
32 - Camera
64 - Volume rocker
For example, a device with Home, Back and Menu keys would set this
config to 7. -->
<integer name="config_deviceHardwareKeys">71</integer>

<!-- Control the behavior when the user long presses the home button.
0 - Nothing
1 - Menu key
2 - Recent apps view in SystemUI
3 - Launch assist intent
4 - Voice Search
5 - In-app Search
This needs to match the constants in
policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
-->
<integer name="config_longPressOnHomeBehavior">3</integer>

<!-- Control the behavior when the user double-taps the home button.
0 - Nothing
1 - Menu
2 - Recent apps view in SystemUI
3 - Launch assist intent
4 - Voice Search
5 - In-app Search
This needs to match the constants in
policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
-->
<integer name="config_doubleTapOnHomeBehavior">0</integer>
[Android Builders Collective] Yank555:
That needs to be overlaid in device repo, but never changed in fwb.

But that shouldn't have impact on backlight...

JP.
[Android Builders Collective] Bongofriend:
[MENTION=2511007]csolanol[/MENTION] Same on bacon, but disabling ambient display solved the issue for me
[Android Builders Collective] angelcalibur:
your right [MENTION=2033478]Yank555[/MENTION] i didn't read the report by csolanol. the link i gave are to make device with hardware key be able to use them, and this light issu are certainly in kernel like you said before...

[MENTION=2511007]csolanol[/MENTION] try to look at this...:fingers-crossed:
[Android Builders Collective] Yank555:
Ambient display could certainly mess with h/w keys backlight as it's a semi-awake state...

Maybe worth investigating in that direction, too.

JP.
[Android Builders Collective] angelcalibur:
Hi!

you can try for slimrom, or try with CM. look at g4 thread to see if you can find one of this rom for g4.

You can look at AOSP too...
[Android Builders Collective] csolanol:
Yup!, ambient display is the culprit. Will have to look into it deeply or disable it lol.
[Android Builders Collective] likonvampire:
[MENTION=2033478]Yank555[/MENTION] are you planning to implement the network indicator change as per the MCC I.e 4g/LTE in the status bar ?
[Android Builders Collective] NeBouse:
That's precisely where my "problem" is lol

I don't want CM, not a fan of it.

There is an AOSP and a Slim6 rom available for my device, but the first is discontinued (dev has switched to IOS), and the second is unofficial and seems not to be updated anymore. (and both of them have sources not very "clear" if I could say).

So basically I'd like to build any Slim6 rom, to be sure my environment is ok, and then I'll try to bring up LG G4 "officially".

Thx.
[Android Builders Collective] angelcalibur:
Re bonjour! :p

I've looked at LG G4 thread : http://xdaforums.com/g4/development/rom-29-04-2016-slim-6-t3369066

You have the link for the device tree, the vendor etc...

so can use it for your own local manifest file. his device tree are from cm, and muppet is uptodate so don't worry about this!

If it's hard for you to make the local manifest, you can ask the dev that make the unofficial slim release. maybee he will be ok to share is local manifest file. It's open source, so he have to share it! :p
[Android Builders Collective] NeBouse:
Thx, I'll try to get in touch with him, hopefully he'll be more cooperative than the AOSP one, he didn't even answer when I asked him politely if he could share his manifest...
[Android Builders Collective] angelcalibur:
:mad::mad::mad:

always this issu with sepolicy when building my rom...

Someone can help me?

Here is the error :

http://pastebin.com/8eEsr6zV
[Android Builders Collective] Yank555:
You mean to show lte instead of 4g ? Been checked in the Slim base code.

So eventually yes, but as I said, purely cosmetic.

JP.
[Android Builders Collective] likonvampire:
Correct purely cosmetic , just a request but not absolutely necessary
[Android Builders Collective] Mikulec:
So does Slim_Yaosp have the same features as original YAOSP?
[Android Builders Collective] kantjer:
<bool name="config_show4GForLTE">false</bool> will probably do the trick for most unless for an overlay sets ik back to true for a specific mcc

https://gitlab.com/SaberMod/pa-andr...mmit/65a90d0709db61455ac593b53602c34d8e69f2fd
[Android Builders Collective] Yank555:
Unfortunately not in this case, that's in already, and telephony doesn't seem to care :silly:

Yup.

JP.
[Android Builders Collective] kantjer:
According to the Slim Git the default is set to 4G

<bool name="config_show4GForLTE">true</bool>

If you set that to "false" the default will be LTE, unless an overlay sets it back to "true" again
[Android Builders Collective] Yank555:
Unfortunately this is the case, it's overlaid in vendor_slim ;)

https://github.com/SlimRoms/vendor_...e/packages/SystemUI/res/values/config.xml#L26

JP.
[Android Builders Collective] kantjer:
OK, in that case I shut up :o
[Android Builders Collective] Smallsmx3:
So I'm curious, why the switch to CAF? I was always against it because of CM. Not that I'm against what they do. It was because I was a CM user until they decided to go CAF which was right around the Nexus 4 days. Everything was really buggy and always broken. You would think CAF would provide a better experience as the code is developed for the SOC. Anyone have any insight on CAF?
[Android Builders Collective] DroidIt!:
:) Well, if it's stable, good battery, little fuss for Mr Yank and such, I say stick with it. I've never been too deep with building and such so I'm sure there's other reasons. Lol, think I was living under a rock too. :) Never saw it mentioned either.
[Android Builders Collective] DroidIt!:
BTW, I'd rather be hanging out with you guys...always homework. :)
[Android Builders Collective] Yank555:
Well looking at this from a purely Nexus point of view, I'd say there's no reason to go CAF ... welll there is, but it's a mixed emotions kind of trip. Mind you, AOSP also uses partially CAF stuff, but it's "older" more tested, so stabler, but logically also less cutting edge. CAF, would be the total opposite, more cutting edge.

So if cutting edge is what you prefer, CAF may be interesting. If stability is key, and a little less internal technical optimisation is in order, AOSP is the better choice.

So there's no good or bad choice in general, it's more of a personal preference thing.

Now if you look at this from a non-Nexus point of view ... there's a huge difference.

AOSP will likely not work easily, if at all, when CAF will be the way to go, esp. if your device is QC based.

And now looking at this from a ROM dev team point of view ... CAF allows to cover Nexus and non-Nexus with mostly the same code.

Keeping an AOSP base for Nexus and CAF base for non-Nexus requires a lot more maintaining work, and additional effort to keep both branches consistent featurewise. Which is why if the team aims at not only Nexus devices, CAF is the prefered choice here.

Hope that explains a bit the pro's and con's of CAF vs. AOSP ;)

JP.
[Android Builders Collective] Smallsmx3:
Learn something new every day. I had allot of general ideas what CAF was. But from a Nexus point of view CM is the only CAF rom I know of and any other Roms that are CAF are based on cm. Guess I'll ride this out. Slim was always great to me on other Nexus devices so I'd like to see how this pans out. And so far in an alpha state things sum to work well
[Android Builders Collective] DroidIt!:
Makes sense :) I figured it had probably been thouroughly talked about way back between the shadow team and Kufi and Juba and such. Makes a bit more sense now. So mostly AOSP based with bits here and there CAF. Aiai sir! :D
[Android Builders Collective] dankoman:
back then we were maintaining both caf and non-caf branches. slim team is a lot smaller now (it's still not the same without [MENTION=4790322]kufikugel[/MENTION] [MENTION=1015465]tortureduck[/MENTION] @jubakuba [MENTION=3609932]Nebucatnetzer[/MENTION] [MENTION=5047159]Tylog[/MENTION] [MENTION=4420265]pemell[/MENTION] and other members of yesteryear, but we still manage), it saves a lot of time cutting out one of the branches altogether.
[Android Builders Collective] Garrykd:
I think you have to say it 3 times.... [MENTION=3087740]Jubakuba[/MENTION] [MENTION=3087740]Jubakuba[/MENTION] [MENTION=3087740]Jubakuba[/MENTION] :p:p
[Android Builders Collective] dankoman:
not gonna work unless you're in front of the bathroom mirror, with the lights out, and are spinning around in circles as you're saying it
[Android Builders Collective] Garrykd:
I thought i was :confused::confused:

I'm certainly dizzy.

:p:p
[Android Builders Collective] limjh16:
Wait what happened to tylog I'm so late
[Android Builders Collective] Smallsmx3:
Not sure if anyone's tried the new N preview? Pretty damn sweet
[Android Builders Collective] JaylanPHNX:
I think, like a lot of people, be just moved on from the hobby.

From my SlimTab Pro 8.4
[Android Builders Collective] adm1jtg:
Lol you didn't mention tarak and rebelos and even me (skitz1967) your premier tester of crespo :D Luckily I think we still have gmillz and prjosh and you and dexter from the original team.
[Android Builders Collective] Ryther:
I'm a fan of Slim since S2 times (started my adventure in the Android world with the HTC Desire :D ) and never found a better ROM. My heart broke when slim almost "disappeared" during LP era, this fabulous team brought a lot in the Android scene! Thank you guys for all your hard work! I love you! :thumbup:

And that's why I'm so proud to announce that my first slim's MM build is ready for bullhead! SlimYAOSP for precision, thank you [MENTION=2033478]Yank555[/MENTION]! And thank you to all the slim team for all your efforts!

You will find all my builds here!

Not tested at all (I dare you to try it :p ), just finished the building, started the upload and now off to bed, my 4hrs of sleep before work awaits me :sly:

Let me know if it works!

EDIT: not working, I'm removing it, will give another try later!
[Android Builders Collective] Mikulec:
Spin clockwise or anticlockwise?

BTW, [MENTION=2033478]Yank555[/MENTION] - Slim is definitely snappier and more fluid than YAOSP (dont know why), but besides the missing Nexus audio I found another cosmetic bug. When the cellular signal is switching the signal icon is changing to the pre-Kitkat icon (5 or 4 stripes that shows the signal strenght).

One other thing I have noticed that the keyboard sound, eventhough its set at the same volume level (the default) is a lot louder (like 100 times louder) on Slim than on YAOSP.
[Android Builders Collective] dankoman:
"and other members of yesteryear" covers you, karan, tarak, arvind, hell even [MENTION=2722834]rirozizo[/MENTION] :p
[Android Builders Collective] Yank555:
Well it's CAF based, so likely more updated drivers ;)

I added the Nexus sounds, but those got overlaid by slim vendor's, which are the AOSP ones, unfortunately. A detail to be addressed ;)

Yep, that's a know thing, no biggie, but needs to be addressed as well, was already the case on LP in the beginning.

Didn't notice, but likely because I tend to disable all sounds pretty much as soon as I boot up a device for the first time :D

JP.
[Android Builders Collective] limjh16:
Whelps what happened to everyone in the slim team...... (I guess what yank and this thread is here for)
[Android Builders Collective] Bongofriend:
SlimYAOSP for bacon is here!

https://www.androidfilehost.com/?fid=24533103863141690
[Android Builders Collective] htb2050:
Is there any lost soul with DEB who might have created slim rom for his/her device?
[Android Builders Collective] gamal001:
what the features about kernel...
[Android Builders Collective] Bongofriend:
It uses sultanxdas stock caf kernel.
[Android Builders Collective] csolanol:
Hi all, someone with bullhead can confirm that whatever kernel you use, cores go offline. On this mi4c kernel all cores are online always while the screen is on.

Ty.
[Android Builders Collective] Ryther:
My cores are always online, I think you need to have an hotplug governor to automatically switch cores on and off
[Android Builders Collective] csolanol:
Yeah, ty, that was what I was asking for [emoji4]
[Android Builders Collective] Yank555:
And when you see 'hotplugging' you're likely just observing thermal throttling in action ;)

JP.
[Android Builders Collective] csolanol:
Well I was used to see cores offline in my hammerhead, so I got confused when all cores are online all the time in this device. It is really snappy with slimYAOSP but was curious about the idea of save some battery with hotplugging. You did and awesome work with slim+YAOSP, thanks again. Wish you enjoy your holidays [emoji1]
[Android Builders Collective] angelcalibur:
JP, where is your manisfet file for SlimYAOSP? :o
[Android Builders Collective] VictorLapin:
I'm tempted to try SlimYAOSP on bullhead but I'm lazy :p it may require another bringup and will certainly require a clean flash
[Android Builders Collective] NeBouse:
Well guys I think i'm gonna need help to create my manifest myself...

I've already asked 2 times to the dev who has ported Slim6 to LG G4 to share his manifest, but he always answers with useless infos...

He can't speak english (german) so either he doesn't understand what I want, or he just don't want to share it...

Where do I begin ? I know where to find vendor tree, kernel sources(CAF based I believe, it comes from CM) and device trees for my device.

Thx.

PS : I don't mind trying to build SlimYAOSP instead of Slim6 if possible.
[Android Builders Collective] rohit25:
missing "sRGB mode"

hey [MENTION=2033478]Yank555[/MENTION] ... thanks for the build.. just flashed over stock build and went into developer options to enable "sRGB mode" but the option is missing.. any reason or did I flash it wrong??

sharing a blurry screenshot as in office right now :P
[Android Builders Collective] diegocr:
I use this at local_manifest

https://github.com/reposte/reposte/blob/master/SlimYAOSP_manifest.xml

Enviado desde mi Mi-4c mediante Tapatalk
[Android Builders Collective] Yank555:
You flashed SlimYAOSP over YAOSP dirty ? Don't think that's a good idea tbh...

The option is available in YAOSP (AOSP based), but doesn't seem to be available in SlimYAOSP (CAF based).

General note - Important : SlimYAOSP is not an update of YAOSP, it's a totally different ROM base, but with the same added features !

JP.
[Android Builders Collective] rohit25:
I was previously running stock rom.. what I essentially did was from TWRP did advanced wipe(wiped everything except for internal storage) and then flashed slimYAOSP... have flashed it twice with no luck.... the sRGB option isnt showing up...
[Android Builders Collective] Ryther:
How do you manage device files?

And what commands do you issue to start a build?

My build missed slimLauncher and I cannot understand why :(
[Android Builders Collective] NeBouse:
Yep, wondering the same here.
[Android Builders Collective] jisoo:
Browsing around github, I happened upon this commit: power: Disable keyboard/button lights while dozing/dreaming.

Is this the droid you are looking for?
[Android Builders Collective] csolanol:
[MENTION=2033478]Yank555[/MENTION] opened a pull request in SlimYAOSP Settings project with spanish translations. Hope you can merge it.

Thanks.
[Android Builders Collective] ezio84:
[MENTION=2033478]Yank555[/MENTION] there's a little fix for the Swap volume buttons on rotation commit:

https://github.com/ezio84/purenexus_frameworks_base/commit/66e04499a196252efe6e0beb487b439a37e92372

Tested and working (thanks Krexus).
[Android Builders Collective] LukaszBobrek:
Man, you've made my day ;) are you going to maintain SlimYAOSP for bacon?
[Android Builders Collective] indian84:
I flashed N Beta released yesterday. Have to say, it's super smooth and I'm getting decent battery. My stats with Social Media, Messaging and a bit of YT. An hour of LTE browsing and rest on Wi-Fi.
[Android Builders Collective] Yank555:
What does need fixing exactly ?

JP.
[Android Builders Collective] Bongofriend:
I will try
[Android Builders Collective] Yank555:
Well that is good enough ;)

But as I said, Slim6, based on CAF, does not have that feature at all.

If you want that (AOSP) feature in your ROM with YAOSP features, just use YAOSP instead of SlimYAOSP ;)

JP.
[Android Builders Collective] ezio84:
If you have the commit to swap volume buttons when rotating the device, if you open the three dots menu of an app and while the menu is showing you press the volume button, the app FC.
[Android Builders Collective] Yank555:
Just tested, on YAOSP angler, no FC ??

JP.
[Android Builders Collective] adm1jtg:
Hey arent you supposed to be on vacation oh wait your not in the US arent you supposed to be on holiday :D
[Android Builders Collective] indian84:
I guess he said he's leaving Saturday. But you should never trust developers. They will continue to work on vacation too. ;)
[Android Builders Collective] Natakranta:
[MENTION=2033478]Yank555[/MENTION], Gallery app FC when I try to edit picture.

Angler Slim_YAOSP. CatLog

Anybody using Shuttle+ player could confirm if it resumes the playback in exact position you paused? I'm listening to audio books, it's annoying when upon resume it is playing few or dozen minutes back from where I left it. I wander if it is because the file (new audio book) or Slim.

I'm restoring my YAOSP nandroid to check.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] DroidIt!:
How many times have I told you! STOP trying to take naked selfies and then trying to edit so you look 3 inches longer. It won't work! :p ....sorry, weird mood...carry on :silly:
[Android Builders Collective] abhibnl:
Hi [MENTION=7031867]Bongofriend[/MENTION]

Thanks for building this. Can you please point to your github to track the changes? Also, if possoble and if you have time, can you please post these builds in the "Slim Builder's Thread" in the bacon sub-forum? Here's the link:

Really excited for this and would love to see what changes or updations are you making, and what feature-set this rom has. Great work!
[Android Builders Collective] Natakranta:
Yeah, I know, I'd have to make it at least 4 inches longer for it to work.

[emoji16]

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] Bongofriend:
I just synced and will post the build here when its finished compiling.
[Android Builders Collective] rohit25:
hey [MENTION=2033478]Yank555[/MENTION] thanks for the reply.. but just to confirm if you plan to implement that feature in the SlimYAOSP as well.. as otherwise it be rendered useless for me... can stand the oversaturated colors of AMOLED.. did try tweaking with FrancoKernel as well but no luck..(like Google's more :P )

thanks again for the help though.. :)
[Android Builders Collective] Yank555:
In vacation mode lol The car is mostly ready to go, everthing's pack ... except for the stuff I will notice I forgot once I'm on the road :D

This time it'll be hard if ut's more than answering a question ;)

Will be back right for Google's next security patch.

Won't get to look at this before I leave ... same was happening on YAOSP ... so I guess sth in the base is broken as I haven't made a single change to that package..,

If Slim (or CAF) won't, I don't think I'll invest the time.

Just use KCAL, it's available in angler, shamu and HH kernels that come with the ROM.

Again if you really need that, just use YAOSP ;)

JP.
[Android Builders Collective] indian84:
[MENTION=2033478]Yank555[/MENTION]

Have a good time. Family first. Cheers.
[Android Builders Collective] Yank555:
I just checked ... I don't have any changes in the file at all related to the swap volume buttons commit ?!

https://github.com/YAOSP/frameworks_base/commit/82f9a56a17ac482eb70166daccdf4c79435ec867

Probably why I don't have FCs either ... just wonder, what that code in "core/java/com/android/internal/policy/PhoneWindow.java" does that I'm lacking ?

JP.

EDIT: Just also tested on SlimYAOSP, no FC either.
[Android Builders Collective] adm1jtg:
Looks like its time for a diff compare :D

Btw answer your hangouts when you get a minute please
[Android Builders Collective] Yank555:
Well if no feature is missing and all works fine, no real need :p

Answered, even if maybe no big help ;)

JP.
[Android Builders Collective] csolanol:
SlimYAOSP for Xiaomi Mi 4c: https://www.androidfilehost.com/?fid=24533103863141902
[Android Builders Collective] ezio84:
Uh well, they seems different commits. Less code is always better, so don't care if the feature works well :D
[Android Builders Collective] abhibnl:
Thanks for continuing building. Was just wondering if you can post in the bacon sub-forum Slim Builders Collective thread. I'll follow this thread as well. :)
[Android Builders Collective] rirozizo:
only just saw this mention.

It sure as hell isn't the same without you guys either! i miss you boys :)
[Android Builders Collective] Yank555:
Off I am, time to leave for Tuscany !! ;)

Will have my phone on me, so may chime in from time to time. Will be back home on June 6th ;)

JP.
[Android Builders Collective] htb2050:
Hey guys! I am trying to build slim6 for Nexus 7 2013 deb. I have synced all the sources and also synced the repos for Nexus 7 from this https://github.com/zwliew?tab=repositories using local manifest.

Now what should my next step be and how do I use the files that I have downloaded from the above repo for a build?
[Android Builders Collective] angelcalibur:
Hello guys!

i want to sync slimYAOSP but i don't see any manifest file or readme with for exemple :

repo init -u git://github.com/slimYAOSP/manifest.git...

Someone can send me a link to make able to sync this ?

want to try to build it too!;)
[Android Builders Collective] Ryther:
Yank555 made no manifest, as stated by him some pages back. A lot of builder shared their github for SlimYAOSP, I have linked my manifest too, just take a look some posts back ;)
[Android Builders Collective] diegocr:
Use slimlp manifest

and a local_manifest like this
[Android Builders Collective] angelcalibur:
Thx guys, [MENTION=4375260]diegocr[/MENTION] and [MENTION=4575569]Ryther[/MENTION] i will look at this!
[Android Builders Collective] JaylanPHNX:
Have fun.

From my SlimTab Pro 8.4
[Android Builders Collective] NeBouse:
Plop.

I've synced SlimYAOSP sources and vendor, device trees and kernel from CyanogenMod github to my build machine.

This is what I get if I try to build :

root@slimbuild-0906:/home/b1jam1_ansel1/slimsource# lunch cm_h815-userdebug
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_h815". Stop.
Device h815 not found. Attempting to retrieve device repository from SlimRoms Github ([url]http://github.com/SlimRoms[/url]).
Repository for h815 not found in the SlimRoms Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/slim_manifest.xml
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_h815". Stop.
** Don't have a product spec for: 'cm_h815'
** Do you have the right repo manifest?

What's next please ?

I think it's a missing .mk file but I don't know what and where ^^

Thx.
[Android Builders Collective] Smallsmx3:
So what are the odds of getting slim to work with Android Pay? I don't really use it but I like having the option since our phones support it. Also, what are the chances that OK Google everywhere will be implemented?
[Android Builders Collective] VictorLapin:
AFAIK, OK Google everywhere is part of the gapps
[Android Builders Collective] Smallsmx3:
Not true at all, if that's the case then my Gapps are magically changing since i use the same gapps with every Rom and thus is the first one that I haven't had it. I'm sure gapps can play a part but isn't the whole story