yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] aow1980:
Thanks to [MENTION=992878]hooliganx[/MENTION] for letting me know in call proximity was broken.

Fixed it and new build uploaded.

Flash and enjoy

Download
[Android Builders Collective] efan3719:
my builds are taking their sweet time with uploading but once they are done... Based on 8.8 with LSW, Status Bar Network Speed, Auto Proximity Speaker, and Notification Ticker. I'm no longer including TRLS as it was abandoned til after Lollipop is out. Links are in my sig, or post 8.
[Android Builders Collective] hooliganx:
glad to help. [emoji4]

tested and work good!

really helpful this feature.

thanks [MENTION=3087740]Jubakuba[/MENTION] for develop it. [emoji6][emoji106]

thanks [MENTION=5497766]aow1980[/MENTION] for put it in your Rom.

n5sk8.8.aow10.26artgapps327

codeblue.r450rd2.21v4atwrp2.8.0.1

------------------------------------------------------------------------

doubts about Slim? click here:

http://slimroms.net/index.php/faqandmanual
[Android Builders Collective] coolek33:
Marc, will you pick this feature in the future? Seems very handy with the way I'm calling.
[Android Builders Collective] hooliganx:
"this feature in the future... "

[emoji4] nice!

n5sk8.8.aow10.26artgapps327

codeblue.r450rd2.21v4atwrp2.8.0.1

------------------------------------------------------------------------

doubts about Slim? click here:

http://slimroms.net/index.php/faqandmanual
[Android Builders Collective] indian84:
Thank You kind sir. So apart from changes mentioned on your blog, this is just SlimLP Build with Layesr??
[Android Builders Collective] Minux31:
Yes, nothing else ;)

---------- Post added at 03:53 PM ---------- Previous post was at 03:04 PM ----------

Revert this commit seems to permit build for d855 : https://review.slimroms.org/#/c/10906/

BTW I don't know why ...
[Android Builders Collective] mslatter:
Thanks Minux31! I'll have to look up what command to use for reverting it as I'm still a little wet behind the ears =) Going to the Bengals game tonight (shooting for 9 - 0), so will have to try it tomorrow. Thanks for the help!
[Android Builders Collective] Minux31:
Simple : if you're base on source rep, cd system/core then git revert I61644633db6b54fa230683615de9724f7fabf6fb (this is the change-ID you can find on the commit page) ;)
[Android Builders Collective] DroidIt!:
Pshhh, that IS simple....EVERYBODY knows to revert 15qrpt87345952 :)
[Android Builders Collective] mslatter:
Haha, simple to type out (or copy/paste) but how you know to do that is beyond me. I assume you look at the change, identify the location to be in and just type the revert command, identifying the change ID. It sounds simple now, but wouldn't have been able to figure that out very easily =)

That noted, I tried it and I get a "fatal: bad revision". Specifically:

android@lollipop:~/building/slim/system/core$ git revert I61644633db6b54fa230683615de9724f7fabf6fb

fatal: bad revision 'I61644633db6b54fa230683615de9724f7fabf6fb'

I thought maybe your ID might be missing a character or something, so I copy/pasted straight from the gerrit change... but no go. If I do a git status there:

android@lollipop:~/building/slim/system/core$ git status

HEAD detached at 63bcce0

nothing to commit, working directory clean
[Android Builders Collective] Minux31:
[MENTION=2982186]mslatter[/MENTION] : Simple if you know, that's clear :D

For the bad revision, have you forked the original project on your Github ? If so, change-id is not the same as initial project change-id, so you've got to find the good one on your github ...
[Android Builders Collective] mslatter:
Hey [MENTION=2638401]Minux31[/MENTION],

You keep giving me way too much credit lol .... negative, I've not forked anything. I just repo sync with Slim's github to my local machine. Any cherry picks I do are local but just running the command locally. To be honest....I got the builds working locally and have just left 'working' alone. Maybe there is a better way with pushing it up to my github account, but I haven't done that. Just a simple repo sync to my local machine, cherry picks, and then build commands.

On the attempt this morning, I repo synced to get all the latest and greatest. When that finished successfully, ran your revert command. Had that succeeded, I'd have then run my repopick commands for my cherry picks, and then make clean and make commands.
[Android Builders Collective] Minux31:
[MENTION=2982186]mslatter[/MENTION] : Great if it worked after synced your local sources :)

Anyway, if you want to work with your own github and not have to cherry-pick everytime you repo sync, give a look at this excellent post from [MENTION=2095315]ezio84[/MENTION] : http://xdaforums.com/showpost.php?p=55178446&postcount=77

It contain all usefull commands to maintain a personnal github with our modifications beside official slim one and keep all up to date ;)
[Android Builders Collective] djole014:
Just ignore this
[Android Builders Collective] Garrykd:
Aaaaagggghhh......It's been two days, I can't ignore it any more!!!:eek::eek::p:p

...btw, best first post ever!
[Android Builders Collective] mslatter:
LG G3 D850 update.

First, big thanks to [MENTION=6794010]Coldwindofnowhere[/MENTION] and [MENTION=2638401]Minux31[/MENTION] for their help in getting past the vector issue. Reverting the commit ID verse the change ID worked! Thanks very much!

Changelog = all merges since last build: https://review.slimroms.eu/#/q/status:merged

PLUS

## Cherrypicks for SlimROM features ##

# RRO Fixes

# KIO - Call Log Phone Tint

# Keep quiet when volume keys are used to wake up device

# Advanced reboot - soft reboot option

# Slim Recent App Sidebar

# Slim Global Menu

# Settings: Add lockscreen rotation as an optional rotation setting

# Fix QS panel showing on secure lockscreen

# RRO2 Layers: show an "Interface-Themes configuration" entry if exists

# Prevent accidental wake-up to OFF by default

Also, removed the following (install app to replace):

FMRadio / HTMLViewer / wallpapers / Camera2 / Calendar

1. Full Wipe (am told dirty flash works)

2. Flash Rom

3. Flash Gapps (I used Slim's gapps from their XDA thread: http://tinyurl.com/pncj8jk )

4. Flash SuperSu (optional but with out it my apps didn't restore properly with Titanium and not realizing it, a few days later I backed up empty apps over my loaded ones - live and learn)

NOTE! I named the file wrong in my haste to go to bed - it was built tonight 11/19/2015 - not 11/2 as it's named. I'd rename it but the last time I did that, the replication broke across the hosting sites and some folks couldn't get it.

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

Huge thanks to the following for making all this possible:

The ENTIRE Slim Team - for a great ROM and constant updates

arcardinal - Device maintainer

X-san - commits help / time saving script!
[Android Builders Collective] amphi66:
In previous Android reincarnations I would sensitize the volume rocker to more & smaller steps modifying build.prop by adding entries:

ro.config.vc_call_vol_steps=30 & ro.config.vc_music_vol_steps=30

This doesn't seem to work with Marshmallow, probably as things are relocated. Does anyone have revised code?

Thanks

Edit: I changed the existing "call" setting from 6 to 30 and added the "music" line, but don't see a change.

Edit 2: Wrong ROM, sorry (although I would.like a solution)
[Android Builders Collective] Fastrite:
Carrying on a long tradition of OT posts [emoji33] , what do you guys reckon to this?

http://xdaforums.com/showthread.php?t=3214967

#WhiteUiMustDie
[Android Builders Collective] hb17:
I don't know if anybody has seen this commit but it's worth looking at.<br />

<br />

https://github.com/PureNexus/androi...mmit/d502eb337d26692f33b7fd0f0f168081e89375bf<br />

<br />
[Android Builders Collective] Yank555:
Pushed it to gerrit for easy picking a few hours ago : https://review.slimroms.org/#/c/12013/

JP.
[Android Builders Collective] diegocr:
New device on the family, amazon fire 5th gen (ford)

http://xdaforums.com/amazon-fire/orig-development/rom-slimlp-5-1-1-amazon-fire-2015-ford-t3256053
[Android Builders Collective] DroidIt!:
Just curious, was that a tough nut to crack? My first tablet was the 2012 fire HD and there was a lot of hoops to jump through just to get a custom ROM on. I did like the hardware, but all the complexity really pushed me to the N7.
[Android Builders Collective] csolanol:
Yeah it was. Not too hard to root since bootloader allows to boot with a temp image, but it remains locked and had to hack netd service to change selinux status and be able to boot the rom from the stock boot image.

This device has a ****ty display and we have had to fight a bit to build twrp for it.

It's a first build btw, bluetooth doesn't work and some small issues still to be sorted out.
[Android Builders Collective] DroidIt!:
Oh really? I loved the display on my kfhd. I would actually think about getting another but yeah, still sounds complicated and I still like my N7 enough I've still not been convinced to part with it yet. I have been seeing on Amazon recently though the N9 32 GB for only about $350 now. Now that is really tempting.
[Android Builders Collective] csolanol:
That's another league. We are talking about the cheap 50 bucks tablet from amazon.
[Android Builders Collective] likonvampire:
When are getting the new slimmallow on angler ?? [emoji16]
[Android Builders Collective] NovaSlim:
It will be ready when it is ready, you should know better than asking for ETA.

In the mean time get by with Xposed+GravityBox+Layers on a Rooted Angler Rom :p
[Android Builders Collective] likonvampire:
Not asking for an ETA sir , just wanted to know if it's being worked on. I do check the gerrit from time to time ..[emoji16]

Sorry not a Xposed fan , thanks I prefer my ROM with layers only.

Cheers [emoji482]

---------- Post added at 10:47 PM ---------- Previous post was at 10:38 PM ----------

Oh [MENTION=5281524]NovaSlim[/MENTION] i have a question for you , I see you are a pocket cast user. Does V4A work for you on SoundCloud with Android M if you use V4A ? It does work with pocket cast app..
[Android Builders Collective] NovaSlim:
One doesn't simply start a question with When then come back and proclaim he didn't ask for an ETA.

It will be worked on whenever SlimDevs with Angler(there are at least one, scroll back a couple pages and you will see, or search) feels like doing it. :p Seeing that SliM 6.0 test builds have been running on N5s since a couple weeks ago(search), shouldn't be too long of a wait.

If you don't like Xposed, that's your opinion. That does mean you have stay on stock M without custom Rom features or try another custom Rom for Angler. For me it is a nice fill-in until the time SliM for Angler is ready.
[Android Builders Collective] Yank555:
Well ... my 6p is "due" to be delivered today or tomorrow, but given Amazon hasn't shipped it yet, I don't quite see how that would be possible :(

Also, the device went from "available on 23rd" to "usually shipped in 1-3 months" a few days ago, I ordered mine on 9th, the day it went on preorder ...

So it's sit and wait I guess :(

JP.
[Android Builders Collective] Mikulec:
How many GB did you order? 32?
[Android Builders Collective] Yank555:
128 ... as 64 on my shamu are a bit short ;)

JP.
[Android Builders Collective] Mikulec:
Amazon has them? :eek:
[Android Builders Collective] Yank555:
In France they do, or rather did :

Only I still see a delivery for today or tomorrow and nothing sent yet, so I am doubtful :(

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Android Builders Collective] Fastrite:
I understand Google store (Europe) has them in stock now. [MENTION=5281524]NovaSlim[/MENTION] , what DPI are you using? I haven't changed mine from stock yet...

#WhiteUiMustDie
[Android Builders Collective] Yank555:
Well Google seems to not know Luxembourg is IN Europe and a founding member of the EU :D

I am not allowed to buy hardware on Play : not available in your country

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Android Builders Collective] Mikulec:
Not only Luxemburg. :crying:
[Android Builders Collective] Fastrite:
That's a b****r.

You'd think that Google being 'fairly big' in the search business would have that one sussed.

EU: a single Europe wide trading community...

The word Muppets springs to mind.

I hope Amazon get it sorted for you soon then.

#WhiteUiMustDie
[Android Builders Collective] JaylanPHNX:
But individual nations within the EU still have their own regulatory schemes, don't they? That could be making things harder for El Goog in those countries.

It's baconnn!
[Android Builders Collective] NovaSlim:
6P? Using 460 and it is working pretty well.
[Android Builders Collective] Mikulec:
Still, there are companies like Amazon that dont have problem to send stuff to countries where they dont have "shops".
[Android Builders Collective] Yank555:
As long as you're not selling stuff like alcoholic beverages, meds, nuclear stuff (like for hospitals) ... there is no legal / regulatory reason not to, the EU has a base of free movement for people and goods, no inner borders.

Well, with what happened in Paris, that part isn't as clear now as it was 2 weeks ago...

JP.
[Android Builders Collective] DroidIt!:
Hey all, kind of an ot question. :) On 6.0 ROMs I've been trying, I was just wondering if anybody knows of a way of restoring app permission and service blocks in between clean installs. Now, there's plenty of different apps to block app permissions and services of individual apps and most work really well, like 3c and My Android Tools. But after a clean install I haven't found one that will restore those blocks. I tried a tibu restore of the blocking app + it's data to restore all my blocks but I haven't found one yet that successfully does that. I'm just trying to avoid needing to manually restore all app permission and service blocks between clean installs...hopefully that makes sense :)
[Android Builders Collective] Yank555:
Yes it does :D

Keep me informed, that's the one reason I always go dirty as long as I can :cowboy:

JP.
[Android Builders Collective] VictorLapin:
Disable Service has backup/restore feature. You only need to grant it root first
[Android Builders Collective] DroidIt!:
Yeah! Hey [MENTION=2033478]Yank555[/MENTION] this one https://play.google.com/store/apps/details?id=cn.wq.myandroidtoolspro did work! I just looked at it and before my clean install I hit the backup button in the app. Then I did my clean install, reinstalled my android tools and hit restore. It gave me a message in the app that restore failed, but I just looked at it again and all individual app permission and service blocks are in place. I'll have to look into it a bit more but MyAndroidTools does work. :)
[Android Builders Collective] Yank555:
Crap ... Amazon reviewed the delivery date for my Angler, now it's dec. 10th or 11th :(

JP.
[Android Builders Collective] otisman:
Nice its going to be nice running your work again! Much alohas Jp
[Android Builders Collective] likonvampire:
Maybe it's all tied in [emoji4] , we have a high chance of getting a nice Slim Christmas present
[Android Builders Collective] VictorLapin:
Best Slim Christmas present for me would be a free time to return to Slim :rolleyes:
[Android Builders Collective] Yank555:
Yep indeed, I know what you mean last few weeks have been intense, no (or not much) juice left in the evening :(

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Android Builders Collective] Garrykd:
Hey guys :)

Happy thanksgiving to the americans out there....hope you are stuffed with turkey:D

Here's my latest Slim6 hammerhead build. There are at least a few things added so I thought I'd share:)

Included in the build is the latest merged Slim6 with:

root access -flash supersu 2.52- (thanks [MENTION=2033478]Yank555[/MENTION] )

power/reboot menu

slim recents ( working but non configurable atm)

and a few other things.

I'm still working on getting the settings for slim recents working as well as a few other things, it's a bit above my pay grade :eek::D

Info: http://xdaforums.com/showpost.php?p=55121772&postcount=5

Download: https://s.basketbuild.com/devs/garrykd/Builds/
[Android Builders Collective] NovaSlim:
Thanks, wish I kept my N5 so I could test it. Patiently waiting for it on my Flo/Angler.
[Android Builders Collective] Phazmos:
And to all good Canadians - and a few relatives

Wish you were here!
[Android Builders Collective] Garrykd:
And I wish I had an Angler to build with ;)
[Android Builders Collective] efan3719:
i wish i could build something for Angler. :(
[Android Builders Collective] indian84:
Is Slim6 build able for Bacon yet?
[Android Builders Collective] kantjer:
There are no Slim m6.0 device repo's for bacon, so no it isn't
[Android Builders Collective] indian84:
I guess because our beloved Robbie is busy with this life.
[Android Builders Collective] NovaSlim:
Looks like there is no Black Friday deal for Angler, Bullhead(N5X) is $80 off everywhere in the US though(Google Store/Amazon)

Volantis(N9) is $200+ off, $199 for 16GB and $279 for 32GB on Google store, most likely clearance sale to get ready for Pixel C soon.
[Android Builders Collective] efan3719:
just what my wallet doesnt need right now lol. though, i wonder if they will really push the pixel c as the replacement for the N9. doest really seem to be filling the same use case. seems like it's more of a competitor to the iPad Pro and the Surface, especially at the price point.
[Android Builders Collective] VictorLapin:
I'd like to have a Pixel C :) Looks just like the something I need
[Android Builders Collective] Garrykd:
Hot damn! A new commit on gerrit!

https://review.slimroms.org/#/c/12088/

...and a new commit means a new build :p:p

Slim density is back, thanks to the always vigilant [MENTION=1277872]dankoman[/MENTION] :highfive::D

Default density for hammerhead is now 400dpi but can be changed, without effecting play store, by changing persist.sys.lcd_density in the build.prop

Build is the same as yesterday with the addition of Dan's density commit

Info: http://xdaforums.com/show...72&postcount=5

Download: https://s.basketbuild.com/devs/garrykd/Builds/
[Android Builders Collective] dankoman:
Does it work? I didn't even test it yet lol
[Android Builders Collective] Garrykd:
Yup :D You're welcome:p
[Android Builders Collective] shaggyskunk:
Looks like someone built Slim Bacon 6.0

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

https://plus.google.com/+martincoulon/posts/H82XGNesocn

Sent From my SM-N910W8 Running SlimRemix V5.3
[Android Builders Collective] coolek33:
Yes, but it's without root and switch network causes FC.
[Android Builders Collective] shaggyskunk:
Yeah I don't have a Bacon device - I was merely pointing out that in fact - Someone has built MM For Bacon.... Maybe it's bacon and eggs - lol

Sent From my SM-N910W8 Running SlimRemix V5.3
[Android Builders Collective] mslatter:
Hey guys,

The G3 doesn't have a maintainer on the MM side yet, so I've just been watching what's going on on the other ROMS. I noticed when reviewing various githubs of other G3 MM ROM's that some folks are forking CM's G3 hardware stuff. Is that something we can do ourselves pretty easily? I gave a shot in the dark tonight and did this....

Deleted everything in my build folder, and a bunch of stuff in the hidden .repo directory (with out deleting all the project files in an attempt to save bandwidth).

Edited and ran:

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

Repo synced and all looked good.!

To default manifest, added the usual (albeit new confirmed branch of course)

<project name="TheLoonyBin/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="mm6.0" />
<project name="TheLoonyBin/proprietary_vendor_qcom" path="vendor/qcom" remote="github" revision="mm6.0" />
<project name="TheLoonyBin/proprietary_vendor_broadcom" path="vendor/broadcom" remote="github" revision="mm6.0" />

Then, thinking I was clever, rather than adding the Slim hardware code (since 6.0 doesn't exist yet) added to my local_manifest:

<project name="CyanogenMod/android_device_lge_d850" path="device/lge/d850" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_lge_g3-common" path="device/lge/g3-common" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_kernel_lge_g3" path="kernel/lge/g3" remote="github" revision="cm-13.0" />

Repo synced again and it completed with no errors!

Next up, Breakfast...but that fails immediately....

build/core/product_config.mk:234: *** Can not locate config makefile for product "slim_d850". Stop.
Device d850 not found. Attempting to retrieve device repository from SlimRoms Github (http://github.com/SlimRoms).
Found repository: device_lge_d850
Checking branch info
Calculated revision: mm6.0
Default revision: android-6.0.0_r5
Default revision android-6.0.0_r5 not found in device_lge_d850. Bailing.
Branches found:
lp5.0
lp5.1
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.

Is this even possible to do, or am I wasting my time (and yours =)?

Thanks in advance for any advice!
[Android Builders Collective] cyril279:
Great start [MENTION=2982186]mslatter[/MENTION] ! You definitely aren't wasting anyone's time .

Notes:

You are starting with CM device trees, which will need to be "slimified" before the build will begin.

Since you're using your own manifest to control things, we're going to skip breakfast, and use lunch.

slimify cm fork example "d850": https://github.com/SlimRoms/device_lge_d850/commit/c6531d15df7830be0bdb028ff7e8a38ad71fb109

slimify cm fork example "i777": https://github.com/cyril279/android...mmit/33605bf4f3b4c90040267ce0312ff48862a68927

slimify cm fork example "ghost": https://github.com/cyril279/android...mmit/178234b2ea6a808196a7b2c534a3cc0f9b9e1608

published manifest(s): https://github.com/cyril279/local_manifest#built-from-slimroms-source

In all examples you'll notice that the cm.mk becomes slim.mk and file references within the make files are changed to reference slim stuff (vendor mostly).

Within recently added slim devices, look for the "bringup" or "slimfy" commit for more examples of the changes made to get slim to build.

Once your builds actually begin, other errors will likely come along, and it will be important to scroll back a bit and find the error. The message is usually VERY helpful in explaining the mismatch/error. After that, search engine.

Best wishes building, long live SLIM!

-Cyril
[Android Builders Collective] shaggyskunk:
It's always Awesome to see support for Slim - Great post ?

Sent From My SM-N910W8 Running SlimRemix V5.3
[Android Builders Collective] mslatter:
Wow, cheers Cyril!

Great information and I can see I have another learning curve to go through =) Interesting stuff and I'll take a look tonight and hopefully get something started. I deleted EVERYTHING last night (thinking it may have been remnants of my 5.1.1 builds causing issues) and repo'd over night. Everything is fresh on my machine to start playing =)

Thanks SO much for the invaluable information - truly appreciate your time!!

Mark.