yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] Hopper8:
Yup the battery saving network mode will take a little while to switch back to 3g after the screen has been off. If you're in a strong signal area it's faster than if you're in a poor signal area. But you can always just leave 3g enabled if the switching time bothers you :)

Edit: [MENTION=1228651]fusionjack[/MENTION] I just saw in your bacon thread that you posted a build with Bluetooth fixes and the reboot fix. It appears this is on your github... So if I build this morning I shouldn't need to revert the reverted commit? :p

Sent from my Nexu5
[Nexus 5 Android Development] fusionjack:
[MENTION=4851213]Hopper8[/MENTION]: another bunch of bluetooth updates. i also updated hammerhead kernel with some bluetooth updates.

i need to sleep now, see you tomorrow.

---------- Post added at 12:06 AM ---------- Previous post was at 12:04 AM ----------

i didn't include the fix which causes soft-reboot in the kk4.4 branch. so hammerhead is not effected, only kk4.4-caf branch is effected.

so basically, you don't need to revert anything...unless you have reverted it on your local repo.
[Nexus 5 Android Development] Hopper8:
Thanks mate, I'll build straight from your git with no revert then. I didn't revert anything yet. Sleep well ;)

Sent from my Nexu5
[Nexus 5 Android Development] hellsgod:
Do you recommend to include these bluetooth fixes in the kernel for compatibility reasons? I'm asking because I'm using my own kernel with SlimSaber and I haven't included these patches yet.

hells
[Nexus 5 Android Development] Hopper8:
:eek: hellsgod on my ROM thread? Nice to have you here :D

Fusionjack won't reply till morning now sorry. But, if you use a Moto 360 / android wear, or connect Bluetooth to your car, does it pair consistently and without dropping in and out, and have all functionality (specifically, able to display sms on the car screen)? If it does all of that properly, that's what we're trying to troubleshoot. But neither fusionjack or I have a Bluetooth smart watch or a Bluetooth enabled car so it's difficult to test.

Sent from my Nexu5
[Nexus 5 Android Development] bobby janow:
It's specific in that it needs to be able to read sms and display it on screen. Without that bt works fine.
[Nexus 5 Android Development] Tylog:
Hehe [MENTION=4851213]Hopper8[/MENTION] Hell is everywhere [emoji91]

Tapatalk Team SlimRoms
[Nexus 5 Android Development] fusionjack:
those bt fixes on kernel side look good to me for fixing memory leak and for preventing crashes, except this one: https://github.com/SlimSaber/kernel_lge_hammerhead/commit/b9029d9e821d5d88c25e3a8f04f461c240be2926

...but since it has been signed-off by some 'professional-look' devs :p, i cherry-picked it anyway.
[Nexus 5 Android Development] bobby janow:
Not difficult for me.:angel:
[Nexus 5 Android Development] hellsgod:
Wow, it seems my name is more popular than I previously thought :D Yeah I'm using your build since a week or so now. I was using the build from Minux before, but after I tried yours, I stayed on it :) Unfortunately I don't have any bluetooth device to test it.

Alright, then I have one more for you to test :p https://github.com/hellsgod/hells-Core-N5/commit/434610db33eaa96f26038593a72c8ce64f8138cd myfluxi is hunting those bluetooth problems quite a while now...

hells
[Nexus 5 Android Development] hooliganx:
[MENTION=647113]hellsgod[/MENTION]

you're a great guy.

and many people here in xda loves your work, patience, dedication and friendly words (almost all the time) [emoji6][emoji106]

n5sk8.0.robbie09.17artgapps292

codeblue.r376rd1.16v4atwrp2.7.1.0

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

doubts about Slim? click here:

http://slimroms.net/index.php/faqandmanual
[Nexus 5 Android Development] Konsumhaus:
Yes, your name is Great [emoji6]

And your work will make it even greater.

You've tried out the same Roms like me[emoji106]

And when YOU are here I can't be wrong[emoji2] [emoji2] [emoji2]
[Nexus 5 Android Development] infatality:
LOL.. i didnt know that slimsaber is on N5 till now!! Gonna flash it.. Misses it since i left my S2!!
[Nexus 5 Android Development] Hopper8:
Hey mate good to see you here :) I remember you saying that you got a N5 not long ago actually :D

Sent from my Nexu5
[Nexus 5 Android Development] ezio84:
Hi guys!

Just to add some info about BT issues: a friend has a BT car stereo so we did a try with his Nexus5 and a galaxy tab.

Both devices sometimes can't pair with the stereo, sometimes can't send the playing audio (tried a lot of music players) while there are no issues with the call audio.

This happens when we install viper4android. Uninstalling it solves the problem.

Ps: tried with the stock Slim rom.
[Nexus 5 Android Development] Hopper8:
Thanks for the info mate! Interesting, I wouldn't have thought of this. [MENTION=2659927]bobby janow[/MENTION] do you use viper4android? If so, could you test without it?

Sent from my Nexu5
[Nexus 5 Android Development] fusionjack:
information regarding gapps 282:

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

Sent from my One A0001
[Nexus 5 Android Development] bobby janow:
Sure I can do that. I'll have to flash your 9/24 build again. But I never had a problem at all until then. Music was never an issue, it was only sms or ObexMap that kept disconnecting me. If I don't allow it access to my sms all is perfect. I'll flash later today.
[Nexus 5 Android Development] Hopper8:
Hold on before flashing 09/24. I'm about to build again ;) But thanks mate, appreciate it! :highfive:

Thanks for this, link added to OP. I meant to do it previously when I first saw that post :eek:
[Nexus 5 Android Development] bobby janow:
OK I'll wait. Long hike today so perhaps this afternoon.
[Nexus 5 Android Development] Hopper8:
Time for a new build! :D This will keep us going while we wait for the new weekly :p

SlimSaber-hammerhead-4.4.4-20140927.zip

Changes:

-More bluetooth updates & fixes. This includes some fixes for bluetooth & cars.

- Updates & corrections to APNs for various countries and carriers

- Fixes regarding memory & app clearing

- Kernel: some updates & bluetooth fixes

See the full changelog for details.. again, it's pretty big :p Have fun!

[MENTION=2659927]bobby janow[/MENTION], please use this one to test with & without viper4android? Thanks! No rush as always :)
[Nexus 5 Android Development] Flamehell:
Tnx mate!!!!Best rom out there!!!!!:D
[Nexus 5 Android Development] bobby janow:
Thank you sir. I'll do that and get a log if it still errors out.
[Nexus 5 Android Development] :
Can you integrate justarchis optimizations?
[Nexus 5 Android Development] Hopper8:
My pleasure, and thank you for helping figure this out :D

I've posted several times in the thread already.... this is already built with the vast majority of the changes that JustArchi's commit makes. These were implemented in SlimSaber well before JustArchi made his commit. There are some also additional flags & optimisations not included in his commit that we have.

Additionally, there's literally hundreds of fixes (memory leak fixes, performance optimisations, more) which have been picked by fusionjack for the ROM.

Summary: We're way ahead of just having JustArchi's commit. So no need to pick it :p
[Nexus 5 Android Development] andrewwright:
Seems like a good rom here ;)

Nice community too :)

Downloading
[Nexus 5 Android Development] Flamehell:
Best that you can find my friend....both :D
[Nexus 5 Android Development] Tylog:
SLim stands for Super Lovely important Mega super duper rom and com xD
[Nexus 5 Android Development] Konsumhaus:
[emoji106] [emoji3]
[Nexus 5 Android Development] Phazmos:
Way ot, but just had a really weird thing happen.

Made a post in the slim thread, now xda says it can't find the thread and I get a search box.

Notice any trouble? I'm missing at already!

Never mind - it's back - never had that happen - weird
[Nexus 5 Android Development] Tylog:
Happens from time to time. Had this sometimes too, it's random and happens with different threads :)

Tapatalk Team SlimRoms
[Nexus 5 Android Development] bobby janow:
Re: Bluetooth. I'm sorry but it did not work. I did a full wipe and installed your 9/27 build and then slim gapps. Logged in with my google account and nothing else. Connected to BT in the car with access to my SMS and it bombed out immediately. Connect and reconnect every few seconds. I got a log of the errors and will attach that here on an edit. Restoring my nandy now. I'm sorry.
[Nexus 5 Android Development] Hopper8:
Hi mate! Awesome to see you with an N5 :D enjoy your stay!

Thanks for testing and the log, I appreciate your time. So to check, that was with no viper4android installed? But thanks for the feedback, I'll look at your log soon. [MENTION=1228651]fusionjack[/MENTION] might like to see it too :)

Sent from my Nexu5
[Nexus 5 Android Development] jwhyte:
Just an fyi I've run v4a with every build of slimsaber currently on 9/18 with 0 Bluetooth issues paired with uconnect system.
[Nexus 5 Android Development] Hopper8:
This gets weirder and weirder :p Thanks for the feedback :) is it possible to update to the latest build & test, most of the Bluetooth updates were introduced from 0922 and further. No rush :)

Sent from my Nexu5
[Nexus 5 Android Development] jwhyte:
I had the same issues on the two newest builds with the continuous disconnect - reconnect. I haven't had time to flash the latest. Should be able to flash it and log tomorrow morning. I haven't had message access protocol working in several ROMs lately so i won't comment on that.
[Nexus 5 Android Development] bobby janow:
It was with nothing at all installed other than gapps. I know you two will figure it out.

---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------

Yes, you are correct. 9/18 was perfect.

---------- Post added at 05:38 PM ---------- Previous post was at 05:35 PM ----------

Same boat my friend. MAP is not working on the latest build, other roms cm based (although aosp) and anything past 9/22 here. I believe there was a 9/22 build if I recall correctly and then the 9/24 one broke it. I'll be a monkey's uncle if Uconnect works for you on this one. (monkey suit out)

Now that being said, Robbie's latest build works with MAP.
[Nexus 5 Android Development] jwhyte:
Alright, first off clean flash 9/27 build slim beta gapps and supersu. Downloaded catlog and spotify only. Phone connected, streamed music and phone calls with no issue. However I spent twenty min toggling Bluetooth on off rebooting etc. No issues aside from a ton of a2dp errors and absolutely no option to connect map. I tried voice commands and checked through settings and notifications but no option for map. I flashed v4a activated rebooted still no issue but also still no option to activate map. I'll give it another go tomorrow and see if I can get map activated and confirm or deny FC's. This is with a 2012 ram uconnect CD system not the touch screen version.
[Nexus 5 Android Development] bobby janow:
Nice work. I am finding the same with touchscreen. It's the MAP that is doing it for sure. Try it without MAP and all is good. So what has changed between 9/22 and 9/24 here and why does Robbie's work?
[Nexus 5 Android Development] fusionjack:
i assume the old build doesn't have cm bluetooth changes and still using slim bluetooth.

official slim only changed their bt to cm one for caf devices. hammerhead is not caf.

those cm bt fixes are all good ones. that's why i also use them on non-caf devices like cm.

did you try to unpair and pair it again? many users have solved their bt issues with this one.

Sent from my One A0001

---------- Post added at 01:06 AM ---------- Previous post was at 01:03 AM ----------

it is still the same error that i mentioned some days ago. you need a special build with a commit that causes soft-reboot on long pressing power menu.

Sent from my One A0001
[Nexus 5 Android Development] bobby janow:
I'll take it. I have a widget now for reboot. Missing my hopper build!

Edit: Why does the Robbie build work? I have no problems on long pressing and no issues with MAP. (Sunday night so be kind.. craft beer here in Colorado) Basically, what did the new BT commits give us that make it worth it to forgo the MAP functionality?
[Nexus 5 Android Development] jwhyte:
I'm giving 9/27 another shot I was unable to get even the option to enable map when I flashed it yesterday. My wife will have her 2014 uconnect touch screen system back Tuesday so I'll try hers then and give mine another shot tomorrow.
[Nexus 5 Android Development] xda890:
About bluetooth, every improvements to the terrible BT stack from Google is worth it.. But there is one feature in the stock ROM that is missing in AOSP ROMs and that is track information over BT, e.g. to be shown on my car stereo... Any chance in getting this in this ROM?

I also had HTC One (M8) for awhile (back to my Nexus 5 now... :) ) and they also had support for contact pictures over BT to be shown on my car stereo, also nice feature to have... :)

When the BT protocol supports all these nice features, why can't Google implement them......
[Nexus 5 Android Development] fusionjack:
ok, i think you have mixed up some information into one. here are some summary:

hammerhead IS NOT caf device

originally, slimroms only has aosp bt changes, then slimroms is using cm bluetooth, but ONLY for caf devices

slimsaber hammerhead HAS the cm bluetooth changes

based on your logcat, the fix of your bt issue should be the one which causes soft-reboot

this fix is nowhere to be found in slimroms or slimsaber. the fix needs to be added to github.

Robbie's build is mostly based on slimroms non-caf device which doesn't have cm bluetooth changes

with so many good cm bt changes, it is hardly that those changes make bt worse. cm could have problem with the map at the beginning and slimroms may not, but since we are using cm bt changes, we have it now.

so now, i need to you to test latest 3-4 builds and let me know, which build has a working MAP for you and which one is not.

please do a clean install for testing.
[Nexus 5 Android Development] bobby janow:
Very good explanation, thank you. So any aosp rom or device that incorporates the newer features of CAF, specifically the BT changes, will break the MAP function, as it currently stands. So at this point if I want to use MAP then I will need to use a rom that does not incorporate those changes or wait for a rom that will give me the power button issue. Correct me if I'm wrong.

As for now I'm running Robbie's build which still has the aosp BT stack. All works fine. Hopper's build was fine until 9/24. I've been on a clean install streak these days so there is nothing dirty about the flashes. I tried the build posted here 9/27 but the issue remains. I did not try to pair BT without MAP on that build. Every build before 9/24 worked fine. I clean flashed and dirty flashed for about a month now and it always worked. Liquid rom did not, so I'll assume they had the CAF changes in BT a long time ago. I'm going to flash the 9/27 build again now to see if BT connects without MAP, which I assume it will. I would flash a build with the power button reboot issue if it were available until the whole thing get sorted out if ever.

If you want any logs from the 9/27 build I can get them for you in about 30 minutes. Let me know which ones please. I can get all kinds of logging levels but the error only ones seem more concise and to the point. Thanks for your efforts here. Although a little frustrating it's kind of fun testing and such.
[Nexus 5 Android Development] Hopper8:
Yep I think you're at the right conclusion regarding which roms will have functioning MAP. Also note that official slim has not had significant Bluetooth updates for some time now.

Your testing is much appreciated, especially as neither fusionjack or I can test MAP :( if it's easier for you, flash the ROM to multirom (it's how I test things from other builds :p ) it saves a bit of hassle. But many thanks for your persistence :)

Regarding the power button /reboot fix, I highly doubt it'll be included apart from a possible test build. No point breaking something quite core to the ROM which will affect a lot of users. I hope this last paragraph doesn't sound arrogant or harsh, apologies if it does. That's not my intention :)

Sent from my Nexu5
[Nexus 5 Android Development] bobby janow:
No offense taken at all. I understand that if it does happen it will be a test build. I never did get into the multi rom thing, maybe it's time? haha. So I just flashed your 9/27 build with 292 full Slim gapps. BT connected but it's still downloading my phonebook. I tried it with MAP, I'm a glutton for punishment, and it didn't work as I saw on Saturday. It will not download my phonebook. Going to restore my nandroid now and get you the log later. Looks like the 9/24 build for later.

Edit.. 9/27 version Bt doesn't work at all in the car, map or not.

Edit2: 9/22 version works fine other than MAP.

Edit 3: wow I missed this rom.
[Nexus 5 Android Development] marf28101995:
[MENTION=4851213]Hopper8[/MENTION]

Can you add trls in the next update ?they look awesome [MENTION=1228651]fusionjack[/MENTION] have you checked it ?:)

Sent from my nexus 5 powered by Code_Blue + Android L
[Nexus 5 Android Development] Hopper8:
I've seen it, and yes it looks sweet :D waiting for it myself. But not yet finished by dankoman, as far as I can tell it doesn't have a settings page yet. Don't worry, when it's able to be added, it'll be added :D

Edit: it does have something to do with settings. Just waiting to see what happens with it, usually dankoman will give a bunch of us a go-ahead on a group hangout :)
[Nexus 5 Android Development] marf28101995:
Nice :D

Sent from my nexus 5 powered by Code_Blue + Android L
[Nexus 5 Android Development] pSyCh¤_O_O:
OMG!!!! I didnt know i would find this ROM here toooooo!!!! Crying of joy[emoji24] [emoji24] [emoji24] [emoji24] [emoji24] [emoji24] [emoji24]

Thank you brotheeeeer!!!

Guess whos coming to this thread next week?

Me![emoji56] [emoji39] [emoji39] [emoji39] [emoji39] [emoji39] [emoji39]

Cant wait!

Edit Look who i found here .hehehe

I see a lot of familiar faces[emoji122] [emoji122] [emoji122] [emoji123]

[MENTION=2511909]gippy2[/MENTION] is here too?
[Nexus 5 Android Development] gippy2:
Hey man...great to have you onboard ....[emoji106] [emoji106] [emoji106] [emoji4]
[Nexus 5 Android Development] pSyCh¤_O_O:
Yeees!!! Cant wait bro....good to see you ;)
[Nexus 5 Android Development] infatality:
Was about to tell you this thread exists.. Lol
[Nexus 5 Android Development] fusionjack:
i might late to the party, what it is? :p
[Nexus 5 Android Development] gippy2:
Was so pleased when Hopper8 brought fusionjacks slimsaber to the N5..... And now you boys are joining in.....its going to be even better than before.... This is a well friendly thread and such a wonderful ROM.. We all have [MENTION=1228651]fusionjack[/MENTION] to thank...and of course [MENTION=4851213]Hopper8[/MENTION]....Happy days you will love it.... [emoji4] [emoji106]
[Nexus 5 Android Development] marf28101995:
The real light slim haha like trds but with white colors

Sent from my nexus 5 powered by Code_Blue + Android L
[Nexus 5 Android Development] AA1973:
The real *light* slim ? ??
[Nexus 5 Android Development] pSyCh¤_O_O:
Hehehe...first thing i did was...android development...scroll down...BINGO! tears of joy.hahaha

Hello to everyone![emoji39] its nice to move home and find a home exactly like the one you left, but better, and be surprised to find out your buddys moved next door[emoji4] lol cool
[Nexus 5 Android Development] fusionjack:
i see, thanks.

btw, [MENTION=2952258]AA1973[/MENTION] nice to see you here :)

how is father chas doing? i'm not following his thread anymore...

sorry for OT :p
[Nexus 5 Android Development] AA1973:
I am fine, thanks [MENTION=1228651]fusionjack[/MENTION]. Nice to see you too. Chas is cooking Dirty Unicorns like there's no tomorrow ?

/OT ?
[Nexus 5 Android Development] Hopper8:
Hey mate! Awesome to have you here :D I didn't know you were upgrading, but great choice of device, it's a beast :D looking forward to having you here :)

I hope this keeps going, soon we'll have half the S2 community here ;)

Sent from my Nexu5
[Nexus 5 Android Development] hooliganx:
I knew it! [emoji16]

this names isn't strange for me!

and suspect know someone from S2 days.

nice! [emoji122][emoji4]

n5sk8.0.robbie09.17artgapps292

codeblue.r414rd1.16v4atwrp2.7.1.0

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

doubts about Slim? click here:

http://slimroms.net/index.php/faqandmanual
[Nexus 5 Android Development] bobby janow:
So now Official Slim, Robbie, and Hopper builds are using the CAF BT "fixes". My car will not connect with BT at all now on any of these roms. I'm still running an older version but is there anything I can do other than go to Purity AOSP? If I have to I will, naturally, but other than that is there another option? Perhaps I need to learn how to build my own and keep the aosp BT stack? Color me not happy but I'm only one person.
[Nexus 5 Android Development] Hopper8:
The idea is to still get the CM BT stack to correctly pair with every device, well at least from a SlimSaber point of view :p It's probably a good thing that official slim is using the CAF BT fixes.... that way some other slim devs will be able to help debug.
[Nexus 5 Android Development] bobby janow:
I will test and log as needed. As for now I'm on 9/24 with a nandroid to beat the band.
[Nexus 5 Android Development] Hopper8:
Thanks, when there's something to test/log I'll let you know :good:
[Nexus 5 Android Development] Flamehell:
[MENTION=4851213]Hopper8[/MENTION] my friend,the new official weekly(8.2)is already included in our buil?Tnx mate!!!!!!:D
[Nexus 5 Android Development] amphi66:
The only BT problem I have with either official SK or Robbie 8.2 is SMS transfer/operation with my 2014 Tacoma. Calls are OK with both using BT. The SMS was also a no go on SK official 7.9, but OK when I briefly reverted to stock to use a clean base for 8.0.
[Nexus 5 Android Development] Hopper8:
Another person with a fancy car :cowboy: does BT work for you on these builds? If not, which parts does/doesn't?

@ Everyone else, sorry I'm having a bit less time for XDA lately due to studies. But don't worry, I'm still around :good:
[Nexus 5 Android Development] herpehancock:
On the most recent build (can't remember the last build BT seemed flawless, but it was) my BT shows it's connected long after I disconnect. A quick off/on toggle seems to fix it. A few other little issues here and there but nothing big enough to make me give up on this amazing rom :)
[Nexus 5 Android Development] Flamehell:
[MENTION=4851213]Hopper8[/MENTION] good luck for everything my friend ;)
[Nexus 5 Android Development] bobby janow:
Do you have UConnect on that Tacoma? I can connect to the phone for only calls once or twice. After that I get bluetooth FC and I have to unpair the phone in order to even use the radio properly. I believe the last time it worked flawlessly was the Robbie build before this one and the Hopper build before 9/24, maybe it was 9/17? Any rom with the CAF BT "fixes" will not work. I saw that Slim Bacon even merged them and I didn't bother to try it. I flashed PA yesterday and it works perfectly. I'm sure that Purity will also work since there are no CM patches.

This has been going on for some time now. These BT patches were merged a while ago and as such no rom was working that had them. Now all the Slim roms went that way and I took the highway. Haha, just kidding but hopefully all roms will not do this. PA tends to be more cutting edge than Purity so I can always go back to stock. I just don't think anyone cares enough about this which is understandable since it only affects a few of us. It's the beauty of having an N5, options galore. However, if any dev feels like tackling this issue I'm happy to test. Nandy, wipe, install, test, restore only takes about 15 minutes.

edit: Looks like the Tacoma has Entune radio which might have slightly different results.