yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] chykal:
Here is an attempt at capturing a logcat. I cleared data and cache on Bluetooth Share and rebooted. Paired the phone and tried to connect. it failed and I took the logcat. Hope this helps.
[Android Builders Collective] Deadsayer:
So I'm trying Ezio's July 4th build. I just flashed it so we'll see what happens tomorrow but it seems to be running fine for now. A couple of things, though.

When I actually have a picture of some sort assigned to one of my contacts rather than the default bit coloured letter that Android assigns, the pictures are all messed up. They don't look right in the Contacts list. Also, is there a way to turn on a close all button in the recents panel?
[Android Builders Collective] gladi8r:
Reset the DPI under settings / display.
[Android Builders Collective] Yank555:
Well reverting that breaks BT on shamu for some car stereo (at least) :(

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.

---------- Post added at 07:31 AM ---------- Previous post was at 07:25 AM ----------

Nothing BT in it.

You'd need to start catching the logcat before trying to first connect, so the log runs when it disconnects.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] diddly3000:
Hey guys. Has anyone got a build which is stock but has just rro? Want to keep it close to stock as possible. Thanks.
[Android Builders Collective] ezio84:
As said in the installation instructions, set again your preferred dpi value, it will fix the messed up pictures.

To close all recentes, just do a pinch-in gesture in the recents panel ;D

Unfortunately it doesn't show anything useful, you should start to grab it during the connection and stop it after the connection fail.
[Android Builders Collective] :
Which device?
[Android Builders Collective] diddly3000:
N5 sorry
[Android Builders Collective] :
Ah shame. Could have done one for shamu in literally 30 minutes.
[Android Builders Collective] diddly3000:
Much difference in n5 and n6 performance wise? Didn't seem like much of an upgrade so skipped it. Price dropping all the time now tho ?
[Android Builders Collective] Yank555:
Honestly, if the N5 had a bigger and amoled display (5.5 - 5.7) and stereo frontfacing speakers, I'd have stuck with it.

The N5 performs extremely well and I even almost get the same battery life as with the N6, with the same usage pattern (no gaming, mainly browsing, tapatalking, g+, chat...).

But I love the display (size and type, black is black on amoled) and the speaker construction (stereo & frontfacing, huge improvement).

Also the camera is an improvement.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] :
Pretty much the same feelings. I'd been hoping for a nexus or GPE phone around 5,7-6 inches for a long time. Still it took me almost half a year to sell my N5 for the Shamu I'm now holding.

Edit: [MENTION=2033478]Yank555[/MENTION] if I use your kernel with my own build will it inject that setting-file-thingie that comes with your rom?
[Android Builders Collective] :
New build up!

Changelog and download link can be found in my post here.

Didn't add that script by [MENTION=2033478]Yank555[/MENTION] yet. Haven't made up my mind incase people want to use other kernels with my builds.
[Android Builders Collective] razrlover:
N5 with 5.2 " or 5.3 coming in a couple of months:)
[Android Builders Collective] Yank555:
Just to be precise, since it's been a topic coming up here and there ;)

It might be an issue only if the kernel flashed does

not

bring its owm ramfs.

The reason is that I added an own service to init.rc which runs my config script on boot complete, this will be kept with kernels using anykernel flash method (does not bring a ramfs of its own), so those settings will still be applied.

As an example, if you flash lean for instance, the config script won't matter, as lean brings its own ramfs.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] PunkUnity:
Anyone know what's up with the audio on M8? Some users are having low volume issues with everything except in call volume.
[Android Builders Collective] :
Ah right, thanks for the clarification. I'll look into adding it for the next build then :) I really do like it because that way with your kernel it's just "flash and forget" because I like how it behaves and don't really need any kernel modification app either.

I hope you don't mind me asking further instructions :) Haven't done any scripts/patches like that in my builds before. Do I create a new file into the shamu device repo or add those lines to the device.mk? And how about the location in the device repo to add the file itself or will that patch generate the file upon building?
[Android Builders Collective] physwizz:
I improved my battery life greatly by changing the sync frequency on my exchange accounts from automatic(push) to never.
[Android Builders Collective] Yank555:
You just add the config script file in the device repo (root folder), and then add these lines in device.mk so it gets copied into the build (I left the lines above and below so you find the spot I added it to :

PRODUCT_COPY_FILES += \
device/motorola/shamu/spn-conf.xml:system/etc/spn-conf.xml

[B][COLOR="Red"]# Add kernel config
PRODUCT_COPY_FILES += \
device/motorola/shamu/init.yank555.lu.kernel.sh:system/etc/init.yank555.lu.kernel.sh[/COLOR][/B]

PRODUCT_TAGS += dalvik.gc.type-precise

Be sure to give the script file 755 filerights ;)

JP.
[Android Builders Collective] ezio84:
Can you please test this build by Robbie?

http://xdaforums.com/showthread.php?p=61825897

It has Google blobs and it seams to fix some BT issues, maybe we have luck with your one too :D
[Android Builders Collective] mslatter:
D850 update.

RRO layers

Add alternate WebView provider package

SlimHeadsUp: Add a global 3-way switch

Flip to Mute Working! (enable in call settings)

Accidental Wake up OFF by default

Latest Kernel, G3 and D850 commits

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 07/09 gapps from their XDA thread: http://tinyurl.com/pncj8jk )

4. Flash SuperSu

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

MD5: d40e1dd913029e3b3b561044db4135e1

Changelog is all new merges since last build from this link:

https://review.slimroms.eu/#/q/status:merged

Huge thanks to the following for making all this possible:

Slim Team - for a great ROM

arcardinal - Slim device maintainer

ezio84 - RRO fixes (Layers rock)

X-san - commits help / time saving script!
[Android Builders Collective] chykal:
I just did and it worked flawlessly. Here is what I said in the official Slim thread.

I'm sorry but I was away from my vehicle all day and just now got a chance to test it and it worked flawlessly. I paired and made a call. Then shut off the car and restarted it and made a call. I then turned off Bluetooth on the phone, restarted it and made a call. A disconnect from either side of immediately reconnected from without issue.

This is the amazing teamwork I have some to expert from this team of competitor's. You guy's are extremely talented. Thank you all.
[Android Builders Collective] Yank555:
I've spun a HH build with Robbie's latest vendor repo (he used in his testbuild).

Would be cool if those of you running into these streaming reboot issues could give it a test and report back.

https://www.androidfilehost.com/?fid=24052804347773173 (didn't boot)

Please note I made this remotely and couldn't test it (my HH is at home), so this may just as well not even boot, so a nandroid would be a good idea ;)

JP.
[Android Builders Collective] 7sen:
Doesn't boot with me. Stuck with Google [emoji185]
[Android Builders Collective] bobby janow:
Change the kernel and it should boot.

edit: Right, nothing to do with kernel. I can't boot this on multirom.
[Android Builders Collective] velvel:
Robbie's build fixed it for me. I did not have a lots of reboot problem, but bluesleep wakelock was killing my battery.
[Android Builders Collective] Yank555:
Will test it myself, home now ... I found the zip size to be a little 'tiny', but well...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.

Edit : yep, indeed, blobs were missing, and Robbie even told me, guess I was too tired to think about that ;)

---------- Post added at 08:10 PM ---------- Previous post was at 07:58 PM ----------

Nothing to do with the kernel.

JP.

---------- Post added at 08:18 PM ---------- Previous post was at 08:10 PM ----------

HAMMERHEAD TEST-ROM WITH BT STREAMING FIX

OK, ROM fixed, just 1 word to change, but one that has a heavy consequence :D

Here is the DL link : https://www.androidfilehost.com/?fid=24052804347773395

Running the ROM for a couple of minutes now.

JP.
[Android Builders Collective] morfances:
Doesn't boot me too. Stuck with Google
[Android Builders Collective] Yank555:
The one above your post ?? Running fine here.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.

Edit : This one : https://www.androidfilehost.com/?fid=24052804347773395
[Android Builders Collective] morfances:
No this

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Android Builders Collective] cimdrap:
I'm experiencing a weird behaviour with ezio's and elementalx 4.02. It worked ok since today, but i got the display full of glitches (colorated pixels on the whole screen), so i dirty flashed the rom again and everything gone ok, but i tried to reinstall the kernel and i got same problem since the boot animation.
[Android Builders Collective] Yank555:
A little more info might help, I just dirtyflashed it over my previous build and it's running just fine...

Did you clean/dirty flash (on top of which ROM) ? Cleared anything ? Flashed a kernel, mod ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] morfances:
Clean flash ,multirom

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Android Builders Collective] Yank555:
Could that be the issue ? That's the only diff with my setup, no multirom.

JP.
[Android Builders Collective] bobby janow:
It has to be multirom. I've never been able to flash your or Robbie's rom. I've tried a diff kernel and got it to boot one time a while ago hut it messed with the multirom boot sec injection or whatever it's called. Yet Ezio and other slim roms boot fine.
[Android Builders Collective] Yank555:
I never used/needed multirom, so never actually cared to look what needs to be done to make a ROM/kernel "compatible".

If it's no big deal (and has no ill sideeffects on normal use), I could add it ... not sure that would ever make it into Slim, though.

JP.
[Android Builders Collective] bobby janow:
Once you get hooked on multirom it would be very difficult to do without. With a solid "internal" rom there is no need for a nandroid ever again. I mean anything can happen so save your sdcard to computer once in a while, but no need to ever restore. And multiple areas for testing roms. But this is not a multirom thread so I'll stop. But I've always wanted to flash your builds so if you can figure it out...
[Android Builders Collective] 93foxgt:
Didn't mean to thumbs up this but oh well. You get a freebie today. I used multirom for a while and its nice if you like to flash different things. The problem that plagued me and made me uninstall it was the fact that 9 times out of ten the secondary ROM I would attempt to flash wouldn't boot. How are you clean flashing it? When you flash it do you flash multiple items before booting? I ask because I would have to flash the ROM, boot, then go back in and flash gapps, kernel, SuperSU afterwards and that always didn't work.
[Android Builders Collective] rpr69:
I had a very similar problem on Sunday with multirom, I could not get the secondary ROM to boot. I tried everything that was mentioned above, but what fixed it was going into TWRP -> multirom, pick the ROM, then run 'restorecon'. Booted up first time after that. Maybe try that.
[Android Builders Collective] bobby janow:
Lol, thanks. I really didn't want this to degrade into a multirom discussion but I'll answer quickly. I very rarely have run into a non boot, perhaps once in a hundred. I "add a rom" to internal, go back select the rom and flash gapps, and superSU if needed and then reboot. That's it. One boot not multiple. Let's head over here for further discussion. http://xdaforums.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
[Android Builders Collective] Garrykd:
Hi guys :D

New builds up. Includes updated blobs (thanks [MENTION=4911350]RobbieL811[/MENTION]:good:) We'll see how bluetooth streaming goes now :)

Pretty much stock slim, up to date as of today with the addition of layers and [MENTION=2095315]ezio84[/MENTION]'s missed call notification fix

https://s.basketbuild.com/devs/garrykd/Builds/
[Android Builders Collective] cimdrap:
Edit: i installed hellscore kernel and worked for a while...then i received a call (like it happened the first time) and got glitches again. this time i keep getting that issue even i reflash the ezio's rom without flashing other kernels. I think it's heat related. Now i shutoff the phone waiting for it cooling down and try again.

I leave a picture of my phone screen.

EDIT2: i confirm it boot up after cooling down...what could it be?
[Android Builders Collective] ezio84:
I've never had that issue (also these days with high temps here in Italy), but i think you should try with a stock slim or a stock aosp, just to be sure it's not rom related.
[Android Builders Collective] cimdrap:
i don't think it is hardware related because i can read normally the recovery and multirom options. The problem starts on boot animation. Could it be MPDecision related?
[Android Builders Collective] Yank555:
If anything then thermal-engine related, but not mpdecision.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] cimdrap:
so what should i do?
[Android Builders Collective] ralpheboyo:
https://youtu.be/dTpuIiVv7Yg

1+1 Ultra~LP~5.1.1
[Android Builders Collective] cimdrap:
LOL i'm not scared, but i can't use my phone cause of glitches when it happens
[Android Builders Collective] inffy:
Hi guys...long time no see...

Well back again on Android (finally!). Got myself Oneplus One for the time being (waiting for the OP2 and new Nexus phones). And as I don't have my buildserver anymore, I can't build my own builds for the time being

Is anyone building for bacon. Would like something pretty close to stock but some nice cherry picks. Haven't really followed this thread in a while so little bit lost at the moment :P
[Android Builders Collective] dankoman:
hiya builders! some stuff for you to play with: https://review.slimroms.eu/#/q/topic:dim_nav_buttons
[Android Builders Collective] Yank555:
Holy Moly ... and I have been settings my Navbar icons to translucent and grey all that time to not have them burn in into my amoled screen :D

But damn, my timing sucks ... I'm just done repo syncing and compiling for all 4 devices :(

Will have to play with this tomorrow ;)

JP.

---------- Post added at 11:45 PM ---------- Previous post was at 11:44 PM ----------

Well, you could try using a kernel with configurable thermal control (like intellithermal), and set the thresholds lower to avoid going where it hurts.

JP.
[Android Builders Collective] theesotericone:
I've seen a lot of phones with bad flex ribbons that produce that screen you posted upthread. To eliminate that as a possibility flash stock and stay on it for a few days. If I was betting money I'd put it on flex ribbon or the connector.:cool:
[Android Builders Collective] JaylanPHNX:
[MENTION=3306843]kantjer[/MENTION] is posing his builds of SlimSaber with ak kernel built in.

From my SlimTab Pro 8.4
[Android Builders Collective] Mikulec:
[MENTION=2095315]ezio84[/MENTION] - any plans on a new build?
[Android Builders Collective] kantjer:
I stopped my AK kernel builds. I still like the kernel a lot but do not like Synapse/UKM to set the kernel.

We added some missing features like smartmax cpu governor and Westwood TCP congestion avoidance algorithm to the Slimsaber stock kernel.

So I'm back to stock SlimSaber now.
[Android Builders Collective] Minux31:
New LG G3 (D855 only) SlimLP personnal build : https://basketbuild.com/filedl/devs...5-5.1.1.beta.0.1-MinuxBuild-20150715-1137.zip

Changelog :

- Sync with latest SlimLP Sources (https://review.slimroms.eu/#/q/status:merged)

- Alarms and no interrupt zen mode

- Allow/Prevent notification light in Zen mode

Sources of my modifications : https://github.com/Minux31?tab=repositories
[Android Builders Collective] Yank555:
ROM Update SlimLP beta 0.1

Time for a repo sync again, not much new in the ROM, most of what got merged actually was already in my previous builds.

But late yesterday night (well for me it was night), [MENTION=1277872]dankoman[/MENTION] (little genius he is) made what was that obviously obvious that noone else ever thought of doing, welcome his SlimDim, Navbar button will dim after a given timeout, makes them feel like hardware keys, the best of both world (did I already mention that I really love that little feature !!) :D

As usual, ROM download links can be found in my OP in the Builders Collective, post 14.

JP.

PS: builds are up on both servers for all 4 devices (shamu, hammerhead, flounder and flo).

Edit :

Please set your custom dpi again so all app manage the new logic.
[Android Builders Collective] ezio84:
:D

Genius. Another little amazing feature. Thank you :victory:
[Android Builders Collective] ezio84:
I always think the most epic part/scene of the series is this one:

Their faces, lol :D
[Android Builders Collective] rfkw:
[MENTION=2095315]ezio84[/MENTION]

I'm on Nexus 5 running latest version of your ROM.

Just a minor bug..

I disabled Ambient Display (doze) options in Settings - Display.

I tried sending myself a message and the screen turns on by itself.

I then try covering the proximity sensor and send myself a message again. After 10 seconds, I uncover the sensor and the screen turns on again.

It seems to be stuck in enabled mode. Can't seem to disable Ambient Display.

Thanks!!
[Android Builders Collective] ezio84:
Which app are you using for messages? At default, if the screen is off and you get a new message notification (whatsapp Hangouts or Gmail for example) the screen doesn't turn on, also if the proximity sensor is uncovered.
[Android Builders Collective] rfkw:
I think you're suspecting a feature in the app which wakes screen. However, it's not a specific app which has this problem. Pushbullet, Whatsapp and others too. It seems to be a general problem...

Diving deeper into the problem, I'm using Glimpse Notification to wake my screen whenever a notification comes in. I have it set to check my proximity sensor for 8 seconds. So if proximity sensor is uncovered within 8 seconds, screen turns on.

The problem seems to be intermittent. Was okay and working fine last night. Today I noticed that when I flip over my phone (ie. uncover the sensor), the screen turns on even though the notifications arrived 30 minutes ago. Disabled Glimpse Notification and the problem still appears.

Cover sensor, send notification, wait >10 seconds, uncover sensor, screen still wakes.

Weird.....
[Android Builders Collective] ezio84:
Maybe that notifications app is not working well with the doze feature or has some other issues with the build, the app dev perhaps can five you some suggestions ;)
[Android Builders Collective] theesotericone:
It's never the an apps fault silly. It's always the ROM. lol

Remember this scene and the events that lead up to it? One of the best faces on TV.
[Android Builders Collective] rfkw:
alright. I've contacted the dev and we'll see how it goes.

Used to work fine on Cataclysm and Chroma. But those are different base and AOSP. Perhaps that app doesn't work well with Slim's base.
[Android Builders Collective] ezio84:
I'm still crying for that pizza :D

Slim is aosp based too, it's weird then. But I can't help you more on that [emoji14]
[Android Builders Collective] Mikulec:
Ok, since the last couple of pages here and in SlimLP official thread has been all about reboots while using BT streaming I gave it a try in my car stereo (****ty chinese radio:rolleyes:). I had to flash latest builf from [MENTION=2033478]Yank555[/MENTION] since I was not able to pair my car radio with Nexus 5 on latest build from [MENTION=2095315]ezio84[/MENTION] (probably issue with different kernel:angel:). And the result was that I had no reboots on a 45 minut drive. I didnt use Spotify but just a Google Play Music, so I personaly think that the reboots are not connected to bluetooth but to either Spotify or to streaming music from internet via bluetooth in general.

One thing to mention [MENTION=2033478]Yank555[/MENTION] - I had bootloop while dirtyflashing your build after ezio´s build, but after flashing different kernel (ElementalX) the rom booted up fine. And just to mention, you are missing lollipop system sounds (at least the system keyboard sound was the kitkat one).

Othern than that all seems fine. Thx.
[Android Builders Collective] DroidIt!:
Hiya [MENTION=2033478]Yank555[/MENTION], [MENTION=2095315]ezio84[/MENTION] et al [emoji16] Been missing a lot of builds I see. I'll flash this a bit later today and bug you if I see anything...though I doubt it, I have seen you guys have been madly working through issues while I've been gone :)
[Android Builders Collective] Yank555:
I keep the stock SlimLP sounds in my builds, I really try to be 100% Slim plus Gerrit stuff (OK, I admin, I have the network indicators and am porting NavRing from CM, but that's all) ;)

LP sounds I flash in my "Yankeefy" flashable zip, with all my stuff, like layers, gapps subset, removing system stuff I don't want etc ;)

I suppose the bootloop is due to ezio having some art stuff in his build (@ezio84 correct me if I'm talking nonsense :D) ?

JP.
[Android Builders Collective] ezio84:
Next build will have all Robbie's BT and audio/video stuff, those pairing issues should be fixed ;)

Welcome back to the party :D

Yes, I'm quite sure the bootloop on dirty flash is due to those art/core commits [emoji14]
[Android Builders Collective] Yank555:
Had some spare time... ;)

JP.
[Android Builders Collective] Failyx:
Please add an option to disable nav bar completely, this would be great ?

Gesendet von meinem Nexus 5 mit Tapatalk
[Android Builders Collective] Yank555:
Navbar ? That's been there for quite some time.

NavRings has a switch.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] ezio84:
It's already Christmas! :D :D

Thanks man!
[Android Builders Collective] Yank555:
ROM Update SlimLP beta 0.1

Two changes, pretty interesting if you ask me ;)

SlimDim has been updated and now does have an option to fade out the navbar keys !!

I've ported CM's NavRing Targets and added a global on/off switch (look in NavBar setting, down at the bottom).

Btw, NavRing is up on gerrit :

https://review.slimroms.eu/6555

https://review.slimroms.eu/6556

As usual, ROM download links can be found in my OP in the Builders Collective, post 14.

JP.

PS: shamu and hammerhead are up, flounder uploading on both servers and flo compiling.
[Android Builders Collective] PerfectSlayer:
Go in settings, navigation and toggle "enable navigation bar" off ;)
[Android Builders Collective] Minux31:
Hi all,

Just a little question : I want to apply RRO2.1 commits on my build, should I have to add abandonned commits of these list : https://review.slimroms.eu/#/q/branch:lp5.1+topic:rro2.1 ?

Or just open commits (that I wanted to do) ?

Just to be sure :)