Database Info

Android Bluetooth Stack Development

Hey I know I'm more of a leech than a seed but I want to start an open discussion / brainstorm about the limited bluetooth capabilities within Android. Specifically on the HTC Dream (G1).
I don't have a strong grasp on Linux but I've been playing with different flavors since i was 13 (11 years). I don't have the knowledge or the support to even attempt this.
HOWEVER I do have a job and I do have the money (donation) to support anyone with the ability and the time.
That being said I would like to talk to anybody who would be Seriously interested in developing additional profiles for the bluetooth stack.
Anyone who has wanted to FTP over bluetooth or for me send my phonebook to my Lexus GS350 I would appreciate donations towards a common goal.
The $ would go to the developer or team. Of course after that it would have to be open source and free to the community.
I have not created a paypal or account for pooling donations but whoever is seriously interested contact me. I've got $300 (donation) to get you started (motivated)
Au Revoir,
-Koocat

how do i make it bold lol

koocat said:
Hey I know I'm more of a leech than a seed but I want to start an open discussion / brainstorm about the limited bluetooth capabilities within Android. Specifically on the HTC Dream (G1).
I don't have a strong grasp on Linux but I've been playing with different flavors since i was 13 (11 years). I don't have the knowledge or the support to even attempt this.
HOWEVER I do have a job and I do have the money (donation) to support anyone with the ability and the time.
That being said I would like to talk to anybody who would be Seriously interested in developing additional profiles for the bluetooth stack.
Anyone who has wanted to FTP over bluetooth or for me send my phonebook to my Lexus GS350 I would appreciate donations towards a common goal.
The $ would go to the developer or team. Of course after that it would have to be open source and free to the community.
I have not created a paypal or account for pooling donations but whoever is seriously interested contact me. I've got $300 (donation) to get you started (motivated)
Au Revoir,
-Koocat
Click to expand...
Click to collapse
i'm all about development and hard work, but with the release of blutooth 3.0, wouldn't it be better just to save the $ and put it towards the next android device that is compatible with bt3.0( which utilizes wifi for bt transfer...not to mention the improved battery life). what are your thoughts?

its not about the money. I'm using dudes cupcake rom whatever latest rom .92 and as far as i know there is no way to send my phone book to my Lexus when it prompts me to create a phonebook and because of this I can't use voice dial and nazi lexus basicly won't allow you to input anything while the car is in motion. the specs released on 1.5 only included stereo bluetooth theres still no push allowed or PBA

jaaronmoody said:
i'm all about development and hard work, but with the release of blutooth 3.0, wouldn't it be better just to save the $ and put it towards the next android device that is compatible with bt3.0( which utilizes wifi for bt transfer...not to mention the improved battery life). what are your thoughts?
Click to expand...
Click to collapse
would my car even work if bt is trans over wifi spectrum?

koocat said:
would my car even work if bt is trans over wifi spectrum?
Click to expand...
Click to collapse
no, and sorry for the confusion. My point was that this android incarnation is lacking in bluetooth capabilities, and there has just been a new bluetooth technology released, not only having the wifi capability, but also all current profiles. I am sure that android will support this in the future with hardware in a new device, but for now, they are probably content with what they have, since it is an evolving technology.

jaaronmoody said:
i'm all about development and hard work, but with the release of blutooth 3.0, wouldn't it be better just to save the $ and put it towards the next android device that is compatible with bt3.0( which utilizes wifi for bt transfer...not to mention the improved battery life). what are your thoughts?
Click to expand...
Click to collapse
Umm, Bluetooth 3.0 standard was just released. We're not going to be seeing any Bluetooth 3.0 devices for another few years, one at the minimum. Not to mention that the OP's Lexus would still require a transfer via Bluetooth 2.0 technology.

I would be content if an open phone with an open platform supported bluetooth features I could actually use.
I manually added one contact into the lexus and manually set the voice rec. and then attempted to call using 'dial by name' and it will only work if the dream is unlocked and awake.
BT 3.0 will be great. but I'd have to get a new phone and depending on the backward capabilities a new car too.
but that brings the question "how long do i have to wait for bt 3.0"
"how long do i have to wait for cupcake"
I was hoping with 1.5 they would expand on the BT stack and they did but not for anything I can use. whats funny is 2 years ago when I had Verizon and a Voyager I thought I was cool to have stereo bluetooth headphones to rock out too. and they want to market stereo bt as being a great new feature but its not new

koocat said:
I would be content if an open phone with an open platform supported bluetooth features I could actually use.
I manually added one contact into the lexus and manually set the voice rec. and then attempted to call using 'dial by name' and it will only work if the dream is unlocked and awake.
BT 3.0 will be great. but I'd have to get a new phone and depending on the backward capabilities a new car too.
but that brings the question "how long do i have to wait for bt 3.0"
"how long do i have to wait for cupcake"
I was hoping with 1.5 they would expand on the BT stack and they did but not for anything I can use. whats funny is 2 years ago when I had Verizon and a Voyager I thought I was cool to have stereo bluetooth headphones to rock out too. and they want to market stereo bt as being a great new feature but its not new
Click to expand...
Click to collapse
This is an appropriate place to post issues with supported bt profiles already supported, but there is no guarantee that it will be addressed. i'm not speaking for anybody here, but me... butif it were my build, i probably wouldn't modify it for one make of car. There are other vehicles where this is working...am i right? i think so.
so far i think only broadcom has achieved and are planning to produce the new standard, but how long will it be till we see it??? my guess is 6mo- 1yr. Yes, stereo bluetooth is not a new thing, but i'm sure you can grasp the technology curve. "they" are only gonna release what they have to, in the time that will make sense to them, not the consumers. This
is a business, and will be treated as such. For how many years have we been scratching at the heels of EVERY advancement, just to PURCHASE it as soon as it comes around. edit...but to go along with you i was looking forward to file transfer myself, and it didn't happen.

what can i do on my car to verify the bluetooth version installed?, or bluetooth capabilities if you know what i mean
its a mazda 3 2010 sport
Thank you.

Your exactly right and thats what makes Android such a beautiful thing. Because we are longer governed by whatever corporate timeline 'they' decide. the timeline is to maximize profit. cupcake is marketed as a feature update to show dedication to their product and to their customer base but its not a dedication because they were forced to evolve it to make it compatiable with additonal hardware and minimize the media attention towards custom devleopment and end user modification. Google doesnt want to piss off Apple or HTC or T-mobile or Vodaphone ect because thats business.
Google doesnt care if you transfer over bt they dont care if you mod your phone. but when Apple says no mulitouch and vodaphone says No Bluetooth profiles they don't have much of a choice if they want Android to succeed.
and Thats why they made it open.
same with rooting your phone google had to fix it beacuse if they make it look easy they run into problems. T-mob or voda don't want you to teather your phone and use it as a modem and root allows this. so you must disable and discourage root and tell people its a security risk.
fcuk T-mobile and their G1 bs marketing. My phone is a Dream.
---btw the new radio gives me 3G in my house now wootwoot so i can actually talk on the phone with t-mobiles shi*ty service--- I only left Verizon because phones suck Donkey...Anyways..
its not just one car. go http://en.wikipedia.org/wiki/Bluetooth to see all supported profiles
there are profiles that all cars support. most likely PBA "phone book access"
I know when the Prius 1st came out I was like 16 or 17 lol and none of VZW phones could send phone book data to the Prius only because VZW policy with phone makers demanded they crimple BT profiles even on smart phones. so you couldn't FTP a mp3 and set it as ur ringtone you had to buy the ringtone for 2.99 or what i did back them I used Bitpim but you get the idea.
-Koocat

alfmetal said:
what can i do on my car to verify the bluetooth version installed?, or bluetooth capabilities if you know what i mean
its a mazda 3 2010 sport
Thank you.
Click to expand...
Click to collapse
I would google some keywords and try and find a user forum for Mazda cars.
I know theres clublexus.com where I have learned a lot about my car.
for some Lexus (i know for sure the GS and LS models) you turn the car on, then hold down the INFO button while turning the Lights from OFF to ON four times. and the car enters a Service Diagnostic mode and you can view different settings and run diagnostics, clear error codes and rescan. I know theres a spot to view the bluetooth version and software version. You can adjust the Mic volume, send and recieve volume and adjust voice quality.
You really don't need to adjust your car (thats not what this post is about).
Depending on your car you can get updates from the dealer and you can find software mods online for some cars.
example; lexus had a override in the system menu to allow user input while the car was in motion. IN 07' that option was removed on all models so for my 07 Lexus i found a post from someone that had taken the Nav disc for the same model in 06 and he modded and issued a ISO for users burn to get that override feature back.
-Koocat

Bah! @ Bluetooth 3.0. Totally overhyped standard. Could be completely done with adhoc wifi and would be easier and more than 2x as fast.

[email protected]:
Yeah, it is... It's just a wifi coop mode, which requires both parties to have a wifi-radio free to use...
It's not really an optimization of bluetooth :/
Everyone else in here:
Well, i'm not sure you're gonna catch many devs in here (There doesn't seem to be any

[email protected] said:
Bah! @ Bluetooth 3.0. Totally overhyped standard. Could be completely done with adhoc wifi and would be easier and more than 2x as fast.
Click to expand...
Click to collapse
Power management is much better in Bluetooth. Combining the two gives the best of both worlds. BT 3.0 will be able to connect, go into low power states and only turn on WiFi if a higher speed transfer is required.
BT 3.0 is more than just BT+WiFi anyway. The ability to have an Alternate Mac-Phy (AMP) like WiFi is one feature. There are other new features as well (like better quality of service). Also, an AMP could be a Ultra Wide Band (UWB) radio, with speeds much higher than WiFi with lower power consumption. The potential for 3.0 is really interesting.
But as others have stated in the thread, it will be a while before there are any implementations. We are just starting to see 2.1 devices in the market.
paesano

I know this is only my 2nd post, but I too am looking for better BT Stack. Dont get me wrong I love that I got back my stereo BT on my Pioneer Avic-D3 but unlike my Nokia N95 and my Tilt which lets me transfer my contacts to my Headunit.
Also another thing I miss is sending contact info from one phone to another!
Waiting for the time I can ditch my ipod and be apple-free LOL

I think a total update of the bluetooth would be cool. I think the 3.0 is a bit away but besides just a specific car profile i think it should be and all around compatible bluetooth. with all the devices and allow file transfer as well something that non g1 phones can already do. I think that alone will make it feel much better until until the newer technology is intergrated. That would probably lean me more to donating

I have two old Motorola RAZR's and they transfer data over BT, it is really surprising that the Dream falls short in this area.

I just miss the very basic file transfer (obex) to move images, mp3, contacts, etc. from device to device. I know I can set up an ftp or webserver to allow phone to phone access, but quite frankly we shouldn't have to use a work around for such a standard phone option. ALso, I like to bluetooth pictures from my phone right to the Kodak picture printer in Walmart and other stores. There is no way to install an FTP server or client on that machine (without some hacking).
I would donate if we had some devs on here taking up the task.
Rick

JackD3ath said:
I have two old Motorola RAZR's and they transfer data over BT, it is really surprising that the Dream falls short in this area.
Click to expand...
Click to collapse
Personally, I'm not surprised that the Dream falls short in Bluetooth support. My experience with Bluetooth in Linux has been very unsatisfying. I don't know if that stems from the Blue Z stack, or if no one cares enough to do things properly. The last couple of times I upgraded Ubuntu or Kubuntu, Bluetooth was totally broken, and I had to figure out my own workarounds to get some of the functionality I needed.
What I would currently like to see is DUN support, so that my Tom Tom can access the internet. Very few BT phones don't have DUN, especially on T-Mobile. Makes me wonder why T-Mobile wanted to get the Tethering apps out of the marketplace. You can tether with almost every Bluetooth phone they sell!
paesano

[Q] Bluetooth 4.0 support?

Hi,
I recently bought a Bluetooth heart rate monitor to use with my Verizon Galaxy S3. It uses Bluetooth 4.0, and I found out later that apparently almost no Android phones (including the S3) include support Bluetooth 4.0 (at least as far as I understand this). I've been trying to search for info on this and haven't really found anything except it's not currently supported.
Does anyone here have any idea of how close support is? I've seen some suggestions that it might be in Jelly Bean, but I haven't been able to verify that yet. Also, I guess just having BT4.0 support isn't enough, it would also need some sort of heart rate monitor profile, so if you know anything about when this might be included I would be very grateful!
Thanks,
Jon

Wow I am shocked at my results of findings on this. I was also under the impression 4.0 works. I wanted a smart watch.........
Samsung does know about this issue, here http://goo.gl/TgAFA (very very long link)
There are 9 pages of reports.

tonu42 said:
Wow I am shocked at my results of findings on this. I was also under the impression 4.0 works. I wanted a smart watch.........
Samsung does know about this issue, here [removed to allow post] (very very long link)
There are 9 pages of reports.
Click to expand...
Click to collapse
I hadn't found that before, but it doesn't surprise me. What I haven't been able to find out is if this is something the developers who create custom ROM's can add this themselves, or they will have have to wait for Samsung (or Google?) to add it?

Interesting, and Bluetooth 4.0 is what Apple is touting to use as a replacement for NFC - it would probably behoove Samsung to get this working properly (sounds like they are responding positively in their developer forum).
From the manual:
Bluetooth
Your phone supports Bluetooth® 4.0.
Bluetooth profiles
Bluetooth profiles are specifications for services supported
by individual devices. Profiles improve the ability of different
devices to work together. Your phone supports these
Bluetooth profiles:
• Headset: HSP v1.2 profile supports use of compatible Bluetooth
headsets for mono voice.
• Handsfree: HFP v1.5 profile supports Bluetooth headsets, and
may also support other compatible Bluetooth devices with
speakerphone capabilities.
• Stereo: A2DP v1.2, AVRCP v1.0, GAVDP 1.2, AVCTP 1.3 and
AVDTP 1.2 profiles support delivery of stereo audio to compatible
Bluetooth devices.
• Object Exchange: OPP v1.0 profile allows sending and receiving
of contact name cards (vCard 2.1) and calendar events
(vCalendar) between devices. PBAP v1.2 supports exchange of
Phone Book Objects.
• Human Interface Devices: HID v1.0 profile supports certain
interface devices.
• Personal Area Networking: PAN 1.0 supports exchange of data
with other devices.
• Message Access Profile: MAP 1.0 allows exchange of text
messages between devices, such as with an automotive handsfree
device.
• Health Device Profile: HDP allows communication with medical
devices.
Click to expand...
Click to collapse
- ooofest

Is there a way to enable the "PAN" profile on The HTC One X running ICS?
Under the settings of the specific paired device, there is no PAN profile available to select.
Someone suggested to edit the build.prop file.
Any suggestions if this would work?
Sent from my HTC One X using xda app-developers app

Operation "Tuna Balls" (UNOFFICIAL CyanogenMod 9 from source)

Hello,
I have released a very ugly, hacked up dump of my work from July when I attempted to port CyanogenMod 9 to the Nexus Q. It is incomplete, but compiles still, and functional. Developers might find this of use.
There was a large amount of interest in this work when I released a video of 'proof of concept' that went viral in July, before the consumer launch. This work was all created before Google pulled the launch (July), and many weeks before AOSP or OMAP repos had the source for device/vendor.
I call it "Tuna balls" due to the fact it's a raw rip off of the Tuna/Maguro base from CM9, dated July 2012, when I forked and modified it.
The codenames of the branches may be wrong. A lot of the 'bugs' may be easy to fix. Unfortunately, I never came back to this project after July.
As someone who strives for complete, QA process builds, I kept this private for months. I know it's not complete, please understand things don't work flawlessly. No audio (possibly hard to fix) and crashing System UI (probably easy to fix) can ruin your experience, but this can be hacked into shape
* GIT SOURCE *
https://github.com/kornyone/android_device_google_steelhead
https://github.com/kornyone/android_device_tuna_balls
https://github.com/kornyone/vendor_google_steelhead
https://github.com/kornyone/google-kernel-steelhead
Here are my notes/bug list from Github:
"Operation Tuna Balls"
This is a partially complete attempt at porting CyanogenMod 9 (Android 4.0.4) to the Nexus Q.
At the time of original creation (July), there was no other source available. As such, I used the Tuna/Maguro bases to port to the Steelhead, as there were so many common pieces.
This combination worked well for the majority of things. Known bugs never resolved since this project was orphaned in July include:
* No working audio. Mixers fail to load with tuna audio_hw.c. The OMAP "Steelhead" and AOSP "Phantasm" repositiories online have a -very- hacked up version of this file, but intended for Jellybean (as of writing). Also, OMAP has the audio listed as a known issue in their source releases.
* No working NFC. This could be easy to solve, I did not spend much time on it.
* System UI crashes. This should be a simple matter of finding this conflicting Tablet/Phone System UI layouts being requested (should be an overlay setting, likely).
Most everything else works. This includes:
* Bluetooth pair all the things, no hacks needed.
* Wifi works.
* XHDPI resolution works (when System UI doesn't crash).
* HW Acceleration in games work.
* Google Play Market is open for use.
--------------
While I am a maintainer for CyanogenMod, this work is not official in any way. It is incomplete, and I am more or less abandoning it at this point due to a broken Nexus Q and lack of free time. Please hit me up on Freenode (kornyone) for questions, ##nexusq is still open.
Thanks!

Proof of concept (so people don't have to dig this stuff up):
Video concept -- (Very rough) --
Photo gallery on G+ with screenshots -- https://plus.google.com/100539377198423911977/posts/GRxhSLRnNss

very nice mate
Sent from my Xperia T using tapatalk 2

kornyone. I was wondering where you put this. Thanks for the source release, it will come in use. I have a big move coming up but plan to pick up where you left off and maybe get some other devs in on this. Again, thanks for the xmas present!

how hard would this be to run cm 10 on it?

kornyone,
I was able to build and install your cm9!
Of course I have the same issues as you (systemui crashes, no sound) but hey it's something!
Thanks for everything and I hope there is still some progession on this!

Bluetooth problems with connectivity to car kits.

Good afternoon all,
I thought i would put this to the masses and see if anyone has the same difficulty and problems as me when connecting my phone's bluetooth to the car kit.
Current car kit: THB BURY bluetooth cradle universal
Phone. HTC Sensation xe
Software: 4.1.2 bruces rom cm10
On 4.1.2 cm10 builds i have NO problems connecting to my car kit but when i have a CM10.1 / JB 4.2 rom on the phone then all roms ive tried they all do not connect to the car kit.
I found the following which developers / OP's might be able to help with and finally sort out the glitch that is occuring with 4.2 roms and connectivity to car kits.
--------------------------------------------------------
Latest News
Google confirms Android 4.2 Bluetooth streaming flaw
GalleryPosted on16 Jan 2013 at 09:47, by Gareth Halfacree
Google has admitted that its latest Android 4.2 Jelly Bean software release carries a bug that prevents devices running it from operating Bluetooth-connected devices correctly - and promises that a fix is due shortly.
Android 4.2 launched with the cut-price LG-manufactured Nexus 4 smartphone, adding a wealth of new features including a 360-degree panoramic photo mode and support for multiple user accounts on tablets to the existing 4.1 OS. It is currently only available on Google's own-brand Nexus products - including the Nexus 4 smartphone and the Nexus 7 and Nexus 10 tablets - with third-party manufacturers working to bring the new features to their own devices as soon as possible.
Those who have taken Android 4.2 on board, however, have been left with a flaky Bluetooth connection that causes audio drop-outs when streaming using the Advanced Audio Distribution Profile (A2DP) support built in to the operating system.
The problem, which may have been present to a lesser extent in Android 4.1 but which is causing severe heartache for early adopters, makes audio streaming via Bluetooth almost unusable on the device, with severe lag and frequent cut-outs. Numerous reports have been made by users to Google through the official bug-tracking service, and now there's an official response: the flaw is confirmed, and a fix is due.
Responding to customer complaints, a Google spokesperson admitted that the Bluetooth software stack in Android 4.2 has a glitch - but that the problem has been tracked down and eradicated. "We have fixed the A2DP streaming stutter problem on N7 [the Google Nexus 7]" the spokesperson told complainants. "The next release [of Android] should have the fix. Sorry about the problem." While the spokesperson talks of a Nexus 7 fix, the current generation Nexus devices share a common software stack - meaning the same fix should also apply to the Nexus 4 and Nexus 10.
That next release, Android version 4.2.2, has not yet been given a timescale for release, but Google is likely to be rushing this one out of the door ahead of numerous cut-price tablet launches that will tempt buyers away from its Nexus family of devices.

Hi, Yes that's true, Waiting for Kernel Fix, bluetooth need to restart 2 o 3 times to be detect, but cant paired :crying::crying:

[RESEARCH][ANT+][CM12.1/CM13.0][HLTE]How to implement ANT+ on AOSP Roms 5.1.1+

Hello community,
after many hours of research and different attempts to get ANT+ working with CM12.1 on my N9005 I want to start some kind of information exchange on XDA to bundle all previous experiences.
ANT+ is a low power bluetooth mode, which is used to connect professional sports/outdoor equipment like heart rate belts, speed or cadence sensors, powermeters and so on. BTLE (bluetooth low energy) mode is provided as an alternative, but most equipment manufacturers do no support BTLE because ANT+ is optimized for stability and durabiltiy and has some advantages over BTLE (i.e. optimized device protocols for lower energy expenditure).
There are two smartphone manufacturers out there which support ANT+ natively (depending on the built-in hardware) since some generations - Samsung and Sony. (I read about the OPO (One Plus One) got native ANT+ support in the meantime.)
The qualcomm edition of the Note 3 (N9005) uses a broadcom 4335 wifi/bluetooth chip which is capabable of ANT+. Samsung stock roms provide native ANT+ support but if you switch to a newer CM12.1 or CM13 rom (maybe because of the great performance or KNOX and other bloatware issues), you will unfortunately loose the native ANT+ support. The same goes for the S4 and S4 active too like mentioned in several threads and communities.
There were several attempts to get ANT+ working on CM12.1. One of te most important attempts was made by @christer12 which seemed to be successful:
http://review.cyanogenmod.org/#/c/110547/
http://review.cyanogenmod.org/#/c/110396/
Some days later he stated on his twitter page "ANT+ on hlte don't work properly, because ANT+ in cm-12.1 is not properly integrated for bcm4335.. =(".
ANT-wireless provides a kind of "reference architecture" for the inclusion of ANT+ in Android roms:
https://github.com/ant-wireless/ANT_in_Android
But when comparing this approach with the one used in Samsung stock roms there are some differences. Samsung does not use a native library called "libantradio.so". Their AntHALService (interface between vendor hardware drivers and common ANT+ software) is built on the broadcom SDK which uses the class package com.broadcom.bt (with it's own radio manager implementation). This package is integrated in the Samsung stock rom /system/framework folder as java archive (JAR).
So my intention was to switch to the samsung aproach and use the broadcom libraries (in combination with Samsung vendor libs) for a "custom" AntHalService. That worked out ok, but at the moment I'm experiencing some difficulties in testing. The virtual machine of my android studio does not support bluetooth out of the box and my device (CM12.1) show a runtime reference error (NoClassDefFoundError) while accessing the broadcom classes. All classes are in the APK/classpath but CM12.1 seems to behave differently.
As I'm interested in other experiences and new ideas I just wanted to start this thread.
Thanks in advance and regards,
B

Reserved

I found this very interesting thread of xda-user @iRant which shows neccesary changes in the CM mainline code and seems to be the base for the ANT+ support in CM11:
http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990
https://android-review.googlesource.com/#/q/owner:"James+Bootsma"+status:open
This solutions implements - amongst others - some vendor specific functions/commands (*VS) in the Bluetooth stack which were missing in the mainline code.

https://play.google.com/store/apps/details?id=com.z2software.antplus
Wasn't it working ?

newintage said:
https://play.google.com/store/apps/details?id=com.z2software.antplus
Wasn't it working ?
Click to expand...
Click to collapse
Sorry for the late reply. I messed up my phones CSC and had to reflash my phone several times. ?
Thanks for the link. ? I found some posts concerning ANT+ enabler but they did contain inconsistent results. So I did a little research and recognized that the last update from 2015/12/20 seems to fix some CM problems. Reading that I bought the app to try it out myself.
Results:
In general it seems to be working, but not really reliable yet. I got some "adapter not detected" messages and had to reboot my phone two times to reactivate bluetooth again. I will send an e-mail to the developer to analyze the problems.
As CM is open source a "commit solution" should be more "integrated" but I could live with a workaround if it's really reliable.

I am very interested in this as I was using my tablet (Samsung tab pro 10.1) to connect to my Garmin via ANT+. Since using a CM based custom ROM there is no longer any support. I was using a custom ROM on my Note 3 that was based upon a stock samsung one that included support for ANT+. If it can be included there then why not on CM ROMS?

ANT+ enabler used to work for CM 12.1 , but then it stopped working , i just tried it again and not working. if you flash Teamsek V17 , it starts working, but anything after 17.2 and things stop working. I have NOT tried CM13. (I assume the result is the same)