yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] Hopper8:
Thanks for the feedback! Glad to hear you like it :) we already have stable build 8 merged in, the code has been online for some time now.

But, I do plan to release a new build by tonight, after my presentation is over :D

@ all above discussing skype etc, I find it hard to believe that it's a ROM problem after investigating further. Like it's been stated though, it's impossible to tell without logcats from now. However, as it's a 'side app' - not part of the core experience I'm not likely to look into it further unless a logcat is provided.
[Nexus 5 Android Development] bobby janow:
Thesis on what?
[Nexus 5 Android Development] Hopper8:
My engineering studies thesis. A lot of CFD and wind tunnel testing relating to cycling... that's about all I can say :)
[Nexus 5 Android Development] :
Good luck with the presentation :)
[Nexus 5 Android Development] DsturbD:
Good luck Hopper!!
[Nexus 5 Android Development] Hopper8:
Cheers guys, appreciate it! It went pretty well I think :)

I'm building now but there's no way I can stay awake for it to complete & upload. Don't worry, there'll be a fresh build with a MASSIVE changelog tomorrow morning :) apologies for the delay, but I'm dead tired :(

Sent from my Nexu5
[Nexus 5 Android Development] Royal King:
Umm, any idea what that is?
[Nexus 5 Android Development] Phazmos:
Looks like a screen shot
[Nexus 5 Android Development] gippy2:
Lol..this made me smile....[emoji1]
[Nexus 5 Android Development] Phazmos:
I just had to. Really though, what else could I say
[Nexus 5 Android Development] Phazmos:
Lol - mine is in the shop for a tune up
[Nexus 5 Android Development] gippy2:
Has it got a wake lock ...lol
[Nexus 5 Android Development] Phazmos:
Lololol!!
[Nexus 5 Android Development] Hopper8:
To tell what it is, you need to look at the partial wake locks, not kernel wake locks. I'm not sure what that's called in the app you're using. In betterbatterystats, you look at partial wake locks to see what the problem is. But, doing this tells you that it's an app causing the problem, not a ROM problem.

[MENTION=3276129]Phazmos[/MENTION], full marks for your reply [emoji23]

To everyone else, build is complete and will be uploaded soon! Don't spam f5, I'll announce it when it's finished uploading. But remember that my internet connection is quite slow at the moment :p

Sent from my Nexu5
[Nexus 5 Android Development] Phazmos:
Can't wait for the new build. Looks like a lot of updates to slim.
[Nexus 5 Android Development] DsturbD:
Must...resist... the...urge...to...press...F5..................
[Nexus 5 Android Development] tokoam:
Tell me about it I keep refreshing to see if there's a update.
[Nexus 5 Android Development] Hopper8:
25% uploaded, not long to wait :p
[Nexus 5 Android Development] Hopper8:
Right! Build is uploaded! :D Sorry for the delay. There are a massive number of changes in this build, many thanks fusionjack for your work! The summary I'm posting is very condensed... please look at the full changelog for details.

SlimSaber-hammerhead-4.4.4-20140922.zip

Changes:

- Huge, huge updates to bluetooth. Please test and report.

-'Accept all files' for bluetooth

-More bluetooth updates

-More bluetooth updates :D

-ANT+ support. This is so that heart rate monitors and supported devices are supported. Please test!

Make sure to look at the full changelog for all the details. It is huge! :eek:
[Nexus 5 Android Development] DsturbD:
downloading now!

question: if i did a repo sync this morning and did a build, would it be the same as this?
[Nexus 5 Android Development] Hopper8:
You'd actually have a couple extra patches :eek: I only just checked this minute, it seems FJ updated some stuff while I was building.
[Nexus 5 Android Development] DsturbD:
gotcha. my repo sync was about 10am eastern this morning so who knows LOL

i'll try both and see if i notice anything different
[Nexus 5 Android Development] Hopper8:
:good: I didn't know you built your own, nice work :highfive: to check, go to Slimsaber github and see the time stamp of the latest commits. Then compare that to when you synced :)
[Nexus 5 Android Development] DsturbD:
Cool deal. Yeah I used to be on a dev team, Infamous Development. We had our own source and built for a lot of devices. I did the Note 3 and S3. It was a combo of aosp, aokp, and cm. Our code maintainer had a bit of an ego problem so I left along with a couple of others. The dev team pretty much died after that. Anyways still like to do my own builds but don't really do anything with them. Sometimes you just can't improve perfection! [emoji6]
[Nexus 5 Android Development] Hopper8:
Ah right, sounds cool! Well not about the team break-up.... but hey. Still good to know how to have some fun with the source :) Feel free to fork repos/change things if you want! Else suggest what to change and we can have a look. But warning... my skills are in development too, fusionjack is the brains behind this outfit ;)
[Nexus 5 Android Development] bobby janow:
Yeah, yeah. How did the presentation go? ?
[Nexus 5 Android Development] Hopper8:
Thanks for asking, not bad I think! Presented quite well and my team mate did a fantastic job. We haven't got a grade for it yet, this will come at a later time. But nothing to worry about now is nice :)
[Nexus 5 Android Development] bobby janow:
Excellent! I'm a biker so I was interested in the wind tunnel stats. Another time though.

On a more pertinent issue for this thread.. Anyone get pocket mode to work?
[Nexus 5 Android Development] gippy2:
Not using it...but just tried and it works fine...you did check lockscreen notifications as well ?
[Nexus 5 Android Development] bobby janow:
Son of a gun. Thanks. ?
[Nexus 5 Android Development] Tylog:
Well done Hopper

Tapatalk Team SlimRoms
[Nexus 5 Android Development] Hopper8:
Thanks mate! Really appreciate it :) [emoji106]

Sent from my Nexu5
[Nexus 5 Android Development] TaRsY:
Latest rom is working great on my device. Thanks for the good work.

I can't find the automatic 2G/3G setting when screen on/off. Could anyone help me?
[Nexus 5 Android Development] Phazmos:
Mobile network settings
[Nexus 5 Android Development] TaRsY:
You mean this?
[Nexus 5 Android Development] Phazmos:
That's where it should be, but you don't have it.

On the latest? Clean flash?
[Nexus 5 Android Development] bobby janow:
Have there been changes to bt? My phone will now not pair with my car when using messages. Keeps connecting and disconnect. If I don't use messages it will work. I found this on a different rom some months ago but never this one.
[Nexus 5 Android Development] TaRsY:
Yes, clean flash, full wipe. Slim mini gapps for 8.0 no additional kernel. I have an other problem too. Headsup notifications not showing up. I've found the settings for it, but no on/off switch, now I only have the standard notifications. Before I used to use Mahdi with franco.
[Nexus 5 Android Development] Phazmos:
I don't use heads up, can't help there, but how do you clean flash?

Does it include making sure system is mounted before formatting it?
[Nexus 5 Android Development] gippy2:
Have you gone into settings/ apps..and ticked the box in whatever app you want to show as heads up?.......

I don't have an incar BT... I do have a jawbone and it stays connected whilst sending and receiving messages...Also a boom box for my music and that also stays connected when messages are sent and received.....If that's what you was asking about ......
[Nexus 5 Android Development] TaRsY:
Thanks! Ticked the box for the desired apps.
[Nexus 5 Android Development] bobby janow:
Re: BT. That's not what I'm talking about but thanks. In my car I can connect BT to the phone but in addition it will read my text messages, display them on screen and read them back to me while driving. It's called MAP I believe. When I pair my BT to the car it will ask if it can access my messages. If I say yes the function is enabled. However, on this build and on no other Hopper builds, if I do that the BT will keep connecting and disconnecting over and over again. The only way I can keep BT enabled on the phone is if I unpair it, re-pair it and deny access to messages. This happened on another rom about 2 months ago and I had to leave it due to this since I don't like to text while driving. There is something in the BT stack that has changed and I'll poke around at the changelog now to see if it's documented. I'm wondering if Slim in general has this issue or just this build. I guess the only way to tell is to flash stock Slim but I'm wondering if anyone can replicate. Obviously this is a specific issue for specific cars with this functionality.

Edit: OMG, I'm screwed. Well over (I can't count that high) BT changes and no way to tell which one messed this up for me. So it's either restore my nandy or try another Slim. Dang it. And for the record I got 0.2% drain overnight.
[Nexus 5 Android Development] gippy2:
I thought it might be that ....I'm sure I've heard of this problem not so long ago...but I don't use an in car BT so didn't take to much notice.. Sorry I can't help any further ....Perhaps have a look on slim bacon thread and see if it's mentioned there ..Hopefully somebody can clarify for you ....[emoji106]
[Nexus 5 Android Development] bobby janow:
Nothing there I can see. Are all the BT changes here coming from Slim Bacon too? I apologize, I don't know anything about github or how this stuff gets built, but I will say I appreciate it immensely.
[Nexus 5 Android Development] gippy2:
This was a huge update especially regarding BT.. Fusionjack compiles the ROM and slim bacon is his thread as he has a one plus one...I cant help with anything else but Hopper should be about soon as he is due to wake up lol.....
[Nexus 5 Android Development] Hopper8:
Yes there were massive updates with Bluetooth. People were finding that things such as android wear smartwatches wouldn't pair with the phone. So fusionjack went ballistic and gave us massive updates on Bluetooth. I've actually just noticed that there are a few more fixes on fusionjack's github regarding Bluetooth. I'll compile another build and could you test with this one? If not we will ask fusionjack :)

:eek: how do you know when I get up :D

Sent from my Nexu5
[Nexus 5 Android Development] bobby janow:
We all know when you get up. I will test for sure. So.. this is what I did today. Looked at Robbie's build didn't see BT changes. I don't usually do this and stay with it but I did a nandy of your current build. (working perfectly other than the BT issue btw) Then I flashed Robbie dirty over yours. BT issues are gone. So it's definitely the BT commits from what I can tell if I have a single clue as to what I'm talking about. A test build I will clean flash tomorrow morning as I just can't tonight. And now the Mrs. calls..
[Nexus 5 Android Development] Hopper8:
A new build is up! You guessed it.... more bluetooth updates & fixes :D

SlimSaber-hammerhead-4.4.4-20140924.zip

Changes:

-Fixes to bluetooth in frameworks_base, telephony, and bluetooth app. There are fixes regarding interface when tethering, calls, song updates, and more.

-system_core: memory corruption fix.

Please see the full changelog for details.

[MENTION=2659927]bobby janow[/MENTION] hopefully this will help your bluetooth issues. When you get the chance let me know :good:
[Nexus 5 Android Development] bobby janow:
Downloaded. We're in way different time zones. I'll flash by 8a mdt. Thanks so much. Let you know by 9a.
[Nexus 5 Android Development] Hopper8:
Thanks mate, no rush or stress :)

Sent from my Nexu5
[Nexus 5 Android Development] gippy2:
Sweet ...just on way home from work..3.20am...[emoji1] [emoji106] [emoji1]
[Nexus 5 Android Development] bobby janow:
BT still does not work with messaging. On the changelog from the 9/22 build there are multiple BT commits. I have not seen that in any other Slim build although admittedly I have no idea where to actually look. As I said yesterday, Robbie's build works fine but I've not tried original Slim Bacon. The rom I had this problem with a couple of months ago was Liquid. Purity and Purity plus did not have this issue.

Steps: Restored 9/22 build, unpaired BT Uconnect in car, flashed 9/24 build, updated binaries and all the other system things, re-paired car to phone. Initially it worked as it did originally. Turned off the car, back on and BT would not stay connected. System BT FC every 4 or 5 seconds. It restarts then crashes. I did the same thing with Robbie's build and this did not happen although I did get some other problems like reboots but probably due to the dirty flash. I was merely testing the BT and it did work.

I usually don't have problems like this that others don't have so I'm not versed in getting a logcat. I will gladly do that if it will help. I think there is a logcat app which I'll download now. Thanks for your efforts. The rom is flawless and I'm not wishing to try something else for a silly little thing like this even though it's a big one for me.

edit: If I knew what I was doing I'd be dangerous. Nonetheless, I am seeing a "Fatal Exception: BluetoothMapAcceptThread 0" each time it connects and reconnects. Map is the thing that allows messaging to be connected to the car BT. I know that because when it's connected successfully there is a wakelock called, ObexMapTransaction which I Googled and found references to the messaging.

Logcat attached..I think. A fascinating read and my SS number has been removed.
[Nexus 5 Android Development] fusionjack:
thanks for the report.

first, let's say there are two different kind of bluetooth code bases: aosp and cm

official slimkat build 8 and i also assume Robbie's build still based on it have aosp based code

slimsaber build (let's focus on the latest build) and current slimkat (which is not released yet) are now using cm based code

i remember reading similar symptom to your issue on some custom roms in bacon thread. i believe they are using cm code based for bluetooth stuff. so, my roughly guess: it looks like your issue is a cm bluetooth bug. at other side, based on user feedback on bacon thread, the cm bluetooth fixes some bluetooth issues that user had in the past on slimkat.

as you mentioned fc, it would be helpful if you could grab logcat. you can use bugreport feature in slimcenter and then attach the zip file here.

nevertheless, i'll keep hunting bluetooth fixes and keep my eyes open for any bluetooth related discussion. :)

edit: btw, if you want to test bluetooth, it'd be better to do a full wipe since it could be that the bt device registration from other roms or previous builds could cause issue.
[Nexus 5 Android Development] bobby janow:
Thank you so much! Yes, Liquid is CM based too, although aosp rom. I think you nailed it on that. I did attach a logcat above, next time I'll do the slim center one too. As for dirty/clean flashing, the 9/22 flash was a full clean flash. I usually dirty when the same rom updates but this time for some reason I felt like clean flashing. Hopper did say is was a major update and I had the time. As soon as there is a resolution I will clean flash another build. It's almost come down to how badly do I want messaging on the car BT since otherwise this rom is perfect. I mean 0.2% drop / hour with everything running at night. (well location reporting is off and I use device only..) But really, thanks again for looking into it.
[Nexus 5 Android Development] fusionjack:
i think i found the fix for the fc loop...however i'm not sure if the fix could cause other issue. let me test first shortly on bacon...
[Nexus 5 Android Development] bobby janow:
That would be great. I know there are others with the issue, albeit not too many at this point. As these UConnect BT devices become more prevalent in cars that read your messages aloud I think the issue might get a little more attention. I have a good nandroid and I'm willing to test it out if you don't find anything major that is wrong. Thanks for doing this.
[Nexus 5 Android Development] jwhyte:
I'm up for testing too but not until tomorrow. I have a 2012 uconnect system and up to and including the 22nd build I've had no recognition of incoming messages even though I have given it permission. Bluetooth Fc loop on the 24 th build as well. Map isn't a deal breaker for me but Bluetooth fcs are so in running the 22nd build.
[Nexus 5 Android Development] bobby janow:
So that makes 3 of us that I know of if you're not the guy in the slim bacon thread. lol. I would think there are probably more but that just don't want to deal with it and bypass the messages connect. One thing about not recognizing your messages, however. I know it does not do Hangouts messages. It will only recognize my phone number SMS messages which is kind of annoying. I wonder why that is? Probably a UConnect thing. Hangouts might be more like an email app or something. Think that might be the issue with your uconnect?
[Nexus 5 Android Development] fusionjack:
unfortunately, i'm currently cannot compile a test build for hammerhead and the fix is also not available on my github because i'm doing a maintenance build for i9100 to sort out issue that some users experienced.

nevertheless, perhaps [MENTION=4851213]Hopper8[/MENTION] could provide a build for you who want to try bluetooth fc loop on reading messages.

[MENTION=4851213]Hopper8[/MENTION]: there are some updates on my github. mainly a bunch of bt updates again and some fixes on frameworks/base for stability.

additionally, you can include a fix for the bluetooth fc loop that i mentioned above by doing this in frameworks/base: git revert 197e20f55e7f7647e3e58580765cda72484d17e1 (then press crtl-x, y and enter)

this change looks fine till now on bacon, but i can't test the fc loop.

[MENTION=2659927]bobby janow[/MENTION]: thanks for the logcat. it helps a lot :)
[Nexus 5 Android Development] bobby janow:
Thank you, no problem on waiting for either of you to build. A light at the end of the tunnel is enough. If it works I'm going to scour the threads to find those with the issue. It's actually a perfect storm to even notice it, a newer car with this functionality (special audio system) and a rooted android phone with the CM BT stack. When I mentioned it months ago it was largely ignored, understandably. But with Hopper's build changing from one to the next it became easier to troubleshoot. Can't thank both of you enough for looking into this. Oh, and I like those logcats! I got an app called Catlog and it scrolls in realtime with a capture to text in a simple click.
[Nexus 5 Android Development] jwhyte:
I had your same issue on validus. Great ROM but after submitting logcats for two different releases it was ignored. Love the atmosphere that [MENTION=4851213]Hopper8[/MENTION] and [MENTION=1228651]fusionjack[/MENTION] have created here!
[Nexus 5 Android Development] Hopper8:
Hi mate, thanks heaps for hopping in here :D [emoji106] I'll compile another test build with the latest fixes on your git and also revert that commit (don't worry, I've done that plenty of times before building SS :p )

To everyone else testing, especially [MENTION=2659927]bobby janow[/MENTION] thanks for the feedback :)

Sent from my Nexu5
[Nexus 5 Android Development] fusionjack:
as i thought, the bt fc loop fix is causing other issue. it causes soft-reboot when power button is pressed.

don't apply the fix (the git revert one) [MENTION=4851213]Hopper8[/MENTION]

Sent from my One A0001
[Nexus 5 Android Development] Hopper8:
:eek: oh I see. Well in that case don't worry, I'll leave things as they are for the time being :) thanks for the warning ;)

Sent from my Nexu5
[Nexus 5 Android Development] bobby janow:
So with my limited knowledge, why the bt changes from 22nd to the cm ones on the 24th? What did it do other than the obvious? Will everyone be using this going forward on slim roms?
[Nexus 5 Android Development] Hopper8:
So far all the changes are from fusionjack adding them. Official slim is also getting some updates to Bluetooth but we already have those. The fixes from the 22nd to 24th are additional fixes that were picked by fusionjack. Not everyone will be using the fixes unless official slim merges them.

Sent from my Nexu5
[Nexus 5 Android Development] fusionjack:
it is because cm currently has more bluetooth changes/fixes than any other roms even aosp and it looks like slimroms also follows cm.

the bt fc loop fix that i mentioned last night is actually a revert to a reverted commit. i know it is hard to explain :p

at the beginning, there is a commit which i believe to fix fc loop for example in bt. slim has cherry-picked it and then has reverted it. i think it is because of soft-reboot issue. so the fix that i suggested to Hopper8 is to revert this reverted commit.

i'm curious whether this commit could solve your fc issue because cm still has this commit (with working power button) and yet you had the same issue in the past with cm based rom. based on the logcat, that should be the fix.
[Nexus 5 Android Development] bobby janow:
Can you imagine reading this first thing in the morning? ? I'd be willing to try the double revert and test today to finally get it all working.
[Nexus 5 Android Development] fusionjack:
lol...either [MENTION=4851213]Hopper8[/MENTION] or me could provide a test build for you, but with the cost of soft-reboot when 'long' pressing power button.

if this is the fix, then i want to investigate further to get both (bt fc and power button reboot) working. however, i don't think i'll have time to investigate it before my upcoming vacation. :(
[Nexus 5 Android Development] bobby janow:
I'll try it out if you build it. I'll get some logs too. I'm curious about this and I think it will be more of an issue as cars get this functionality.

edit2: I see that Robbie has a new Saber build out. Did he pull the BT reverts? (Just flashed it and BT works on his build) I understand the CM is cutting edge, I ran their stuff for years on various devices, but why with a pure aosp phone such as this are we using commits that break our stuff? Naturally, I can find a rom along the lines of Purity or stock, but that's really not the point. This rom has everything I need, great battery life, perfect options, and now it's broke. (well not broke, but you know what I mean) I'm just missing the logic here. What did the CM BT give us that we already didn't have?

I don't mean to be contentious, I should probably not post after 2 cups of coffee, so please don't take this as a criticism of any work that you devs do. It's a thankless job and very appreciated by all of us.
[Nexus 5 Android Development] Hopper8:
I'm not going to get a chance to build tonight, it's late here and I'm not even home yet. Too much wind tunnel testing :p

I can compile in the morning if I see fusionjack doesn't post a build :)

Sent from my Nexu5
[Nexus 5 Android Development] bobby janow:
No problem and no rush. I'll just text while driving. lol. OT for just a sec, do you test a cyclist on a bike or a simulation of it? And what exactly are you looking for? I understand you might not be able to reveal this info until it's published.
[Nexus 5 Android Development] Phazmos:
Just a thought, if someone really needed this bt to work, an option could be to use quick tile to reboot.

I use that more often than the power button.
[Nexus 5 Android Development] bobby janow:
Great idea. The quick tile flips to recovery too which is the only other time I long press anyway.
[Nexus 5 Android Development] Phazmos:
Same here
[Nexus 5 Android Development] tcowl:
I've been running this rom for a few days and i've been having some issues with data connectivity. I'm thinking it's related to the mobile network battery saver feature. when i unlock the phone my phone takes anywhere from 1 min to 10 mins to regain data connection (I have sprint btw, so i wouldn't be surprised if this is a session handling issue with them) Is there anything I can do or any advice that my help my situation? I'm really digging this rom i'd like to keep running it.
[Nexus 5 Android Development] fusionjack:
it is working like that...it needs to restart the modem, so it'll take time to connect from 2G to 3G or whatever you set there.

Sent from my One A0001