yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Yank555:
They're still in Slim, the last one needs to stay in (it's a revert-revert). If it's reverted (so goes back in), it breaks shamu bt audio streaming to certain car stereos, which I just managed to fix recently.

I made a testbuild with just the 3 first (smaller ones) in, and it works fine on shamu like that.

I'll try to give the other 3 a closer look.

Could you test a build with the same commits for HH ? I'd spin it for you, let me know.

The thing, though, about those commits is, all these commits are in a purely BT repo, so they are all BT related. If you can get the same reboot on wired headsets, that must just be a sideeffect.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] ifwillems:
OK, I can test it. Let me know which one I need to test. Will then year test with BT and without BT active.

---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------

[MENTION=2640853]Garrykd[/MENTION] , does your latest version have the 4 commits for streaming audio ? Or did you keep those out for HH?
[Android Builders Collective] peikojose:
Hey [MENTION=2033478]Yank555[/MENTION] I was testing your build, smooth and clean... Latest Xposed version works fine... CV [MENTION=2095315]ezio84[/MENTION] Only thing I miss is ticker...
[Android Builders Collective] mslatter:
Bump - surely there is something out there? :)
[Android Builders Collective] raycaster3:
Wrong thread. Sorry fellas.
[Android Builders Collective] ezio84:
If you mean Statusbar notification ticker, it's already in my build [emoji14]

There's not a generic way to set something to a default value.

Check my github commits list, there are some "enable/disable xxx feature by default" commits.
[Android Builders Collective] Yank555:
It's been merged on July 3rd, so will be in my next build ;)

JP.

---------- Post added at 10:39 AM ---------- Previous post was at 10:37 AM ----------

Thanx ! It's compiling, I'll post a DL Link as soon as it's done and uploaded ;)

JP.

---------- Post added at 11:14 AM ---------- Previous post was at 10:39 AM ----------

Here it is : https://www.androidfilehost.com/?fid=24052804347769104

It does have the 3 first commits, the on I did leave out is this one : https://review.slimroms.eu/#/c/5103/

This way shamu works perfectly fine as before, if I add it, it breaks BT audio streaming to certain car stereos.

JP.
[Android Builders Collective] ifwillems:
I tried your special download, and I can't get it to crash anymore. I tried streaming audio without Bluetooth and also with Bluetooth.

Does this mean that the official unofficial version from [MENTION=4911350]RobbieL811[/MENTION] should also with with hammerhead?

Thanks for building this version!
[Android Builders Collective] RobbieL811:
Should also what?
[Android Builders Collective] ifwillems:
I meant to ask if your build has the same commits for streaming data and Bluetooth as [MENTION=2033478]Yank555[/MENTION], as his version now works for hammerhead.

I can test your version, but thought to ask first.
[Android Builders Collective] peikojose:
Yep sorry.. I didn't explained myself.

---------- Post added at 08:18 AM ---------- Previous post was at 08:17 AM ----------

Sources have been updated in this new build??
[Android Builders Collective] RobbieL811:
I'm not exactly sure what commits yank is using?
[Android Builders Collective] Yank555:
Revert these :

https://review.slimroms.eu/#/c/5106/

https://review.slimroms.eu/#/c/5105/

https://review.slimroms.eu/#/c/5104/

We should submit reverts for those 3 to gerrit (or fix the root cause of the issue).

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] ifwillems:
Yep. I just finished testing [MENTION=4911350]RobbieL811[/MENTION] latest ROM. It crashes after listening to streaming audio over Bluetooth after 5-10 min. [MENTION=2033478]Yank555[/MENTION] your latest test ROM you built for me, does not crash any longer.

Thanks guys, for all the hard work!

-----------

Unfortunately, I cheered too early. [MENTION=2033478]Yank555[/MENTION] your ROM still craps out after playing streaming audio over Bluetooth. It just took a bit longer: 14 min this time. Sorry.
[Android Builders Collective] ezio84:
As an additional report, yesterday I was running with my new BT headset and a test build with all 4 bluedroid commits reverted (so also this one https://review.slimroms.eu/#/c/5103/ ) and no audio streaming problems.

Ps: new build incoming :D
[Android Builders Collective] Mikulec:
when when when when when when when when when when when when?????
[Android Builders Collective] VictorLapin:
No ETA, remember? :D
[Android Builders Collective] Yank555:
Unfortunately, that is not a solution, it may solve bt streaming reboot issue for HH but it breaks (though not reboot, but constant reconnects) on shamu (at least).

We really need to get behind this HH reboot issue.

Shamu runs perfectly find with all 4 in, so it can't 'only' be those four, it merely seems to trigger the base HH issue, I'm afraid.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] ezio84:
Slim mod 5.1.1.build.0.6-20150705 :D

Download: https://www.androidfilehost.com/?w=profile&uid=23578570567714195

(links at right)

Changelog:

- Source sync: Slim, AOSP, CM AudioFx/Terminal

- Heads up:

* Add a global 3-way switch (disabled - per-app - forced)

* Snooze button view and layout improvements

Navbar and Pie:

* PieController: prevent NPE in resizeIcon

* SystemUI: fix navbar icon too big when using custom icon

- Layers: calls log phone tint

- Layers app updated to 4.1 (sorry, in the previous build i put the 4.0 version by mistake)

- Improvements for rocker key music controls:

* Fix not being able to adjust volume when music control is on

* Disable screen off volume/music control when wake key is enabled

* Map long press of mute to keycode play_pause

- Fix navbar hiding slowly during full screen setup activities (SetupWizard)

- CM custom DPI improvements

- Keyguard: fix misaligned ripple for pin-entry backspace button

- Massive APN fix and update

- Fix missed call notifications not shown after you call someone

- Frameworks improvements

- Reverted "Turn off "Mobile data" and "Data roaming" by default" (As being discussed on the slim gerrit, this commit has a drawback: the user can't run the setup wizard when clean flashing without a wifi connection. Not good.)

- Maybe something else i don't remember :P

Installation and kernels - IMPORTANT:

- Ensure you have latest bootloader and radio from 5.1.x factory images.

- If you come from another rom do a factory reset and wipe system/caches. If you come from the previous build, wipe system/caches. In both cases, set again your dpi value in the "Display" settings menu.

- After flashing the rom zip in twrp, flash latest slim gapps (zero or mini), then reboot and enjoy.

- Recommended kernels: stock Slim

Tips about some features:

- If you want to use a navbar buttons layer, disable buttons colorization in navbar settings to avoi small icons

- Adding Slim Actions to Nova Gestures let you set some useful and handy gestures for the home screen

- Slim Pie can be also a good apps launcher

- you can set DPI in Display settings

- with the new Privacy guard, you can disable the automatic start of a specific app

- if you press Volume rocker down till it set the Vibration mode, press it again to enable the new Silent mode (no ringtones and audio notifications)

- if you want to use the No Interruptions mode but still want Alarms, go in the Audio and Notifications settings, then Interruptions, then enable Allow Alarms

- if you expand the volume panel, it will remember your choice also after a reboot

- in the navbar customization settings you can set the buttons glow color if the default white is too bright for you.

Build additional features compared to stock Slim (Please read it before asking where to find a setting):

PS: this list also contains links to all commits if you want to cherry-pick them:

https://github.com/ezio84/scripts/blob/lp5.1/My_mods-commits_and_tips/Commits-list-with-links.txt

PS: if you have problems, call A-team or clean flash.
[Android Builders Collective] Garrykd:
My latest build has the 4 bluedroid commits reverted.

I'm assuming that the 4 bluedroid commits have been merged into cm12.1 (they have - thats where they came from). If [MENTION=4267479]ifwillems[/MENTION] could possibly try a recent version of cm to see if he has the issue with it or not, that might tell us we are missing a commit or 2 somewhere in slim source

Edit: maybe something here?: http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_external_bluetooth_bluedroid

maybe we need this http://review.cyanogenmod.org/#/c/99486/ instead of this http://review.cyanogenmod.org/#/c/98804/ ???? (Edit: maybe not, that's for cm 12)

Thanks cm :rolleyes:

Edit again: we don't have this commit in slim http://review.cyanogenmod.org/#/c/99570/ maybe I'll build with that included
[Android Builders Collective] ifwillems:
Ouch, you now make me test a CM ROM? ;)

[MENTION=2640853]Garrykd[/MENTION] , [MENTION=2033478]Yank555[/MENTION] , [MENTION=2095315]ezio84[/MENTION] , [MENTION=4911350]RobbieL811[/MENTION] , I installed the latest CM ROM for HH. Then started streaming audio with a Bluetooth headset. After 45 min, it was still working without problems. There currently is no Slim 5.1.1 ROM, that I know of, that doesn't do a soft reboot within the 20 min mark.

I hope this helps. So CM does not have the issue, it seems.
[Android Builders Collective] RobbieL811:
It's probably something in the device files or blobs. BT streaming is working just fine on Bacon. Seems to be a HH problem.
[Android Builders Collective] :
Sigh I really should have known better...

Got myself a new AMD graphics card for gaming (on Windows) and totally totally forgot how crap it is to get anything AMD related working on Linux unless it's 5+ years old. Spent a better half of the last week installing, purging and trying different versions of the proprietary and Linux built-in AMD drivers. And been installing different versions of Linux too to see if it makes any difference.

Think I finally got the proprietary drivers to work after going to Mint 17.2 (didn't work on 17.1) at least for now. I really should just have settled with something Nvidia. At least their proprietary drivers work even if they aren't open minded about open source.

Anyway this is why there's been a bit of a break from my builds. I'll catch up sometime soon once I have time from work and have set up my build environment again.
[Android Builders Collective] acultr:
ezio84!

do you use some kind of layers, if yes then which one?

thanks
[Android Builders Collective] Yank555:
Aboslutely agree, same goes for shamu, all just fine, I'd have searched for the cause either in the device tree or indeed the vendor repo...

And reverting those, or better reverting the 4th (the one I left out) breaks BT streaming on shamu for certain audio hardware, so that one definately needs to stay in.

The problem here is that these 4 commits impact all devices (bluedroid repo is generic), and only HH has an issue, so the solution can't really be in that bluedroid repo imho.

JP.
[Android Builders Collective] ezio84:
http://xdaforums.com/showpost.php?p=61588399&postcount=6363 :D
[Android Builders Collective] Garrykd:
Well, tilting at windmills is the best I can do with my abilities :D

Not sure what might be the root cause, as I am on hammerhead and could not reproduce the issue. Streaming works fine for me without anything reverted. But it also works fine with the reverts.

I suspected it might be kernel related (as I don't use the stock slim kernel) but I believe [MENTION=2033478]Yank555[/MENTION]'s build includes his custom kernel and the issue for [MENTION=4267479]ifwillems[/MENTION] was still present on that build.

Either way, the issue is present in slim source. I only build for hh and mako so I'm going to continue to revert this and call it fixed :angel:

I have a new build up that only reverts the one commit (https://review.slimroms.eu/#/c/5103/) to see if it is just that.

https://s.basketbuild.com/filedl/de....1.beta.0.1-UNOFFICIAL-20150705-1926.TEST.zip
[Android Builders Collective] ifwillems:
[MENTION=2640853]Garrykd[/MENTION] and [MENTION=2033478]Yank555[/MENTION], I am not sure if anyone else with a HH has the streaming audio issues. So perhaps it is on my end. Although I did clean installs of your ROMs, I am willing to go one step further and first bring my HH back to factory settings, incl. unroot and locked. If you think that is worth a try let me know; and also which ROM I should test it with.

In the mean time I am back on Twisted 5.0.2 from [MENTION=2888538]letmedanz[/MENTION].
[Android Builders Collective] RobbieL811:
Actually JP, I've been sitting here listening to music for the past 30 minutes via bluetooth from my hammerhead without error. Seems that it's working just fine on my latest hammerhead build. Are you sure you weren't missing some other BT commits from Gerrit???
[Android Builders Collective] ifwillems:
Robbie, which ROM are you using? Let me install that one from a spanking clean HH device.
[Android Builders Collective] RobbieL811:
Below is the build that I am using on HH. I've been streaming BT music for probably near to an hour. Not one single problem.

Slim-hammerhead-5.1.1.alpha.0.5-UNOFFICIAL-20150704-1839
[Android Builders Collective] ifwillems:
I installed your ROM after wiping Dalvik, system and cache, coming from Garykd's ROM. My phone did a soft reboot after 20min of streaming audio via Bluetooth.

Should I do a different wipe, or install method?
[Android Builders Collective] RobbieL811:
Lol. Idk. I listened to music for an hour this morning. No problems. Can you induce the reboot and get a logcat of the reboot happening?
[Android Builders Collective] ifwillems:
See posts 6416 and 6417.
[Android Builders Collective] Yank555:
I am basing my assumptions on the feedback hear, I haven't tested this on my end, as silly as it sounds I wouldn't know on what to test it.

For now I will keep all in as they work fine on shamu, that I have clear feedback.

JP.

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

---------- Post added at 05:43 PM ---------- Previous post was at 05:42 PM ----------

BT commits from gerrit ? I just have what's in the repos for BT ... what'd I need ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] RobbieL811:
Why do I need to see those posts? I know what I'm talking about. I'm not having any BT problems. I'm basically telling you to prove to me that you are having problems. Also, if a problem exists, I would then have a log to go off if as I can't reproduce ANY Bluetooth issues. My BT is working tip top.
[Android Builders Collective] ifwillems:
6416 has the logcat in it.
[Android Builders Collective] RobbieL811:
Ok. I'm on mobile right now. Kinda hard to navigate.
[Android Builders Collective] theesotericone:
I'm not able to reproduce this on the HH either. I'm on one of my own builds but have not touched any BT stuff. Went out climbing yesterday and decided to bring my BT speakers instead of my wired earbuds specifically to test this issue. I played music over BT for well over five hours without a single skip or reboot. I am using EX as my kernel though.
[Android Builders Collective] ifwillems:
So is there a different way for me to do a clean flash? I wiped Dalvik, System, Cache. Should I wipe more? Or go back first to factory condition (unroot, lock)?

The fact that my phone is encrypted can't have anything to do with this issue, right?
[Android Builders Collective] theesotericone:
You're doing a form of dirty flashing that way. To do a true clean flash you need to wipe data. So wipe system, data, caches. Then set your phone back up and try again. If the issue still persists for you get an app like Catlog and start the log before you play music. It has an option to record the log to your sd card as a .txt file. When the reboot happens upload that log.

Encryption shouldn't have anything to do with what's occurring. My bet is some older data that's not playing nice.
[Android Builders Collective] efan3719:
The only Bluetooth related issue I had was with my pebble losing connection every once and while but on E's last few builds I've had not had that issue at all. Bluetooth streaming audio has worked just fine the few times I've used it.
[Android Builders Collective] Yank555:
BTW, if BT screws up someone and not for another, keep in mind that there are always 2 devices involved,both of which will negociate on how exactly the communication will go about.

The issue on shamu only happens with a very few BT devices, but it happens.

So to validate, we needs someone who can reproduce the issue reliably to actually test this...

JP.
[Android Builders Collective] Mikulec:
That is what I initially thought, what if the problem is not in the rom/mobile but in the bluetooth streaming device? So far I have seen only [MENTION=4267479]ifwillems[/MENTION] having the bluetooth streaming problems. Or have I missed someone else?
[Android Builders Collective] Minux31:
Hi everyone,

After a long time, I'm trying to come back in this wonderfull builders collective, by building Slim form my new LG G3 european version (d855)

I've initilize my building env correctly I think (Arch linux 64, Openjdk 1.7.0_79, python 2.7.10, and make 3.82)

I've repo sync lp5.1 branch of slimlp, added d855 spécific device, kernel and proprietary repo in .repo/local_manifests/slim_manifest.xmll :

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="SlimRoms/device_lge_d855" path="device/lge/d855" remote="github" revision="lp5.1" />
<project name="SlimRoms/device_lge_g3-common" path="device/lge/g3-common" remote="github" revision="lp5.1" />
<project name="SlimRoms/kernel_lge_g3" path="kernel/lge/g3" remote="github" revision="lp5.1" />
<project name="TheLoonyBin/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="lp5.1" />
</manifest>

After repo sync, lunch for d855 and make bacon, I'm facing this error :

Traceback (most recent call last):
File "../../tools/json_schema_compiler/compiler.py", line 196, in <module>
opts.impl_dir, include_rules)
File "../../tools/json_schema_compiler/compiler.py", line 54, in GenerateSchema
api_def = schema_loader.LoadSchema(schema)
File "/media/DataSSD/Android/slim/external/chromium_org/tools/json_schema_compiler/schema_loader.py", line 87, in LoadSchema
api_defs = idl_schema.Load(schema_path)
File "/media/DataSSD/Android/slim/external/chromium_org/tools/json_schema_compiler/idl_schema.py", line 466, in Load
idl = idl_parser.IDLParser().ParseData(contents, filename)
File "/media/DataSSD/Android/slim/external/chromium_org/tools/json_schema_compiler/../../ppapi/generators/idl_parser.py", line 906, in __init__
IDLLexer.__init__(self)
File "/media/DataSSD/Android/slim/external/chromium_org/tools/json_schema_compiler/../../ppapi/generators/idl_lexer.py", line 215, in __init__
self.lexobj = lex.lex(object=self, lextab=None, optimize=0)
File "/usr/lib/python2.7/site-packages/ply/lex.py", line 893, in lex
if '.' not in lextab:
TypeError: argument of type 'NoneType' is not iterable
make-3.82: *** [/media/DataSSD/Android/slim/out/target/product/d855/obj/GYP/shared_intermediates/ui/accessibility/ax_enums.cc] Error 1

Any idea ?

Thanks in advance :good:
[Android Builders Collective] Garrykd:
Here's my perspective... The problem [MENTION=4267479]ifwillems[/MENTION] is having is real and reproducible for him but nobody else has been able to reproduce it.. It started right after the bluedroid commits were merged on the 22nd of june and goes away if they are reverted (probably just the one commit). It doesn't happen with cm (where it all came from) so there is something that is different between slim and cm somewhere.

Also, it might be as you said and the specific bluetooth device is having issues. However, the fact that the problem started after those commits were merged and it doesn't happen on cm confuses me :confused:

What head unit do you have in your car [MENTION=4267479]ifwillems[/MENTION]?
[Android Builders Collective] ifwillems:
I can reproduce it with my car stereo as well as with my Bluetooth headset.

Based on an earlier comment, I am going to do a more thorough wipe off my device, then reinstall completely from scratch. Will keep you posted.
[Android Builders Collective] Yank555:
Well that is not exactly what I mean ;)

I mean the device will negociate sth specific which triggers the bug in HH, so the bug is in HH's code, but if you use a different device it will negociate different set of stuff, and that might just circumwent the problem.

JP.

---------- Post added at 09:51 PM ---------- Previous post was at 09:18 PM ----------

ROM Update SlimLP beta 0.1

It was time for a repo sync, done today about 3h ago, the changelog in my op is updated, everything that hasn't been merged yet is back in the build (I rebase on repo sync, cleaner and easier for me), plus this :

- in-call vibreation for call waiting

- long press volume skips music track

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

JP.

PS: shamu & hammerhead are up on both servers, flo compiling, flounder to compile.
[Android Builders Collective] Garrykd:
Ahhhh, right, I get you. So, what we have now is this:

And we need to find this:

:p:p
[Android Builders Collective] Yank555:
Exactly, ain't it fun :D

JP.
[Android Builders Collective] Mikulec:
If it is as big as on the picture compared to the picture of the heystack, it shouldnt be a problem, right?
[Android Builders Collective] pkelly517:
Big ol' magnet. Okay, lots of them. Conveyor belt.

Rare earth to start, and then a huge electromagnet at the end.

Easy.
[Android Builders Collective] Garrykd:
Pffft, engineers :rolleyes:

The needle is made of aluminum :angel:

:p:p
[Android Builders Collective] pkelly517:
Fine.

Hammermill with flexible moving rotating parts. All the straw gets sifted out. The non-flexible items get stuck in the input.

Think of a weed whacker for search. Maybe a few stages at 90 degrees. Bam! Non-flexible needle found.

Software bugs are hard.
[Android Builders Collective] Garrykd:
http://www.amazon.com/Darice-12-Piece-Flexible-Beading-Needles/dp/B00DD4D5WK
[Android Builders Collective] pkelly517:
I may be defeated, but there still is this.

Your silly little needle may not be caught in my trap, but it's not popular enough to be an issue.

Give me an hour or so to come up with a solution. :)
[Android Builders Collective] mslatter:
I'm not a professional at all, but since nobody has answered yet, let me throw this out there for you. I build for the D850, and here's what I did. Added the proprietary lines to .repo/manifests/default.xml file (NOT the slim manifest - not sure if it makes a difference or not.)

Then I ran ". build/envsetup.sh" to set the environment variables.

Then Breakfast [enter]

Select your device [enter]

This 'should' pull your other required locations.

I then go look at my slim_manifest.xml and ensure I have the correct paths to the following:

For me, it pulls lp5.0 - and I just change them to lp5.1 after I confirmed 5.1 existed.

Then I use "lunch" and select the same device and [enter]

Then for kicks, I repo sync again, start adding my cherry picks e.t.c.

Then I :

breakfast

lunch

make clean

make otapackage -j8

And if all works well, after a couple of hours, I have a clean build in ~building directory/out/target/product/d850

There are probably a couple of unnecessary steps in there, but as I read and read and read, and tried and tried and tried, this worked for me.....

Hope that gets it to build for you - good luck.
[Android Builders Collective] theesotericone:
You guys need to think further outside the box. The answer is simple:

Burn the haystack. Then you'll find your aluminum needle pretty easily.
[Android Builders Collective] Garrykd:
That gives me an hour to research more types of needles :D

You just melted both the aluminum and the flexible needles :( we needed those!

:p:p