Develop Bugs

[Q] can't play voice mail from call log anymore!!

I have Verizon GN rooted with latest CM9
set my google voice mail instead of carrier voice mail to play it from call log. Everything was working very well for couple months. However, few days ago stops working. It will show that I have a new voice mail in the call log, and it will show me from whom, but when i open it and hit play it will kick me out back to call log and wont play it!!!!
I was thinking maybe a bug from CM9!!! Can anyone check that for me on his device and confirm it?
I was searching for that problem before I decided to post this, but all what I find is about Sprint and I know it is something different from this one.
Regards,
Bassil

Its either only me, or no one uses google voice for the voice mail from call log except me

I'm having the same problem all of a sudden. I wonder if it's a new bug introduced in CM9 because it works on my old builds on my Nexus One but doesn't work on the Galaxy Nexus or my HTC One X running CM9.
My Google-fu indicates that it might be a codec error, but I don't see any recent changes that would account for this.
sassafras

It looks like it is crashing trying to load the variablespeed playback lib.
Still don't see any change in the CM9 repos that would cause this problem.
sassafras

sassafras_ said:
It looks like it is crashing trying to load the variablespeed playback
Click to expand...
Click to collapse
Exactly, this what is happening to me!!! It wasn't like this with the older versions of CM9. I guess either from the new builds or from Verizon disabled it!!!

Same here
Sent from my Galaxy Nexus

I don't think it's carrier side. I think it's a bug new since a recent build of CM9

I think it's from the Android build 4.0.4, not from cm9 because I changed from cm9 to another rom with same android 4.0.4 and having same problem.

bassil2022 said:
I think it's from the Android build 4.0.4, not from cm9 because I changed from cm9 to another rom with same android 4.0.4 and having same problem.
Click to expand...
Click to collapse
Which ROM? Are you sure it doesn't use the CM9 codebase?
sassafras

I've been told that Google voice replay from the dialer will fail on any linaro build. I think, but could be wrong, that the latest CM9 and AOKP both are now linaro. I'm using stock 4.0.4 and it works fine.

I experienced the same exact issue, also some m3 files wouldn't play.
I was running latest BlackIce which is cm9 based. Just flashed it Monday, reverted back to my nandroid and everything started working correctly. It must be something with the latest updates made on CM9.
Sent from a phone...

sassafras_ said:
Which ROM? Are you sure it doesn't use the CM9 codebase?
sassafras
Click to expand...
Click to collapse
AOKP

I switched to an old build by CM9, and now its working
I was already backed up. So I just restored. It was bulid 5/20

Pretty safe to say it's a CM9 bug, but still no idea what is actually causing it.
sassafras

sassafras_ said:
Pretty safe to say it's a CM9 bug, but still no idea what is actually causing it.
sassafras
Click to expand...
Click to collapse
It's pretty well established that it's a linaro issue.
Sent from my Galaxy Nexus using Tapatalk 2

The latest cm9 nightly (July 9) seems to have fixed this. It works for me now at least.
T-mobile gs2

Bluetooth Message Access Profile (MAP) and JB

Hi Guys,
anyone know a JB ROM that has this feature from CM 9 ?
Bluetooth Message Access Profile (MAP)
I know some SII JB Roms have this ported from CM9 but not sure about SIII.
Thanks,

Raul77 said:
Bluetooth Message Access Profile (MAP)
Click to expand...
Click to collapse
Try CM10... if it's not in there yet, it should be in AOKP

garyd9 said:
Try CM10... if it's not in there yet, it should be in AOKP
Click to expand...
Click to collapse
Thanks, i am actually on AOKP now, its 100% not there. Will try CM10. thanks.

CM10 has it (tried it a few days ago).

smelenchuk said:
CM10 has it (tried it a few days ago).
Click to expand...
Click to collapse
Just incase anyone is searching for this, this works GREAT on CM. thanks for all the suggestions

I am running CM10 M2 and cannot seem to find this featue. My ford sync says text unavailable.

JRust00 said:
I am running CM10 M2 and cannot seem to find this featue. My ford sync says text unavailable.
Click to expand...
Click to collapse
I switched back to AOKP 10/16, its working there now. sorry not on CM anymore.

I recall spotting a fix for MAP in the CM10 changelogs in the past day or two; I'm not sure what was broken or when, but presumably the break happened before M2.
If I get a chance I'll check if the latest nightlies still have MAP working.

smelenchuk said:
I recall spotting a fix for MAP in the CM10 changelogs in the past day or two; I'm not sure what was broken or when, but presumably the break happened before M2.
If I get a chance I'll check if the latest nightlies still have MAP working.
Click to expand...
Click to collapse
Is mail working with bluetooth map on CM10 oder aokp or just sms?
thanks.

Slim bean 4.2.1 stable release mentions MAP in their change log. Have not tried it yet though. Looking to find one that works with Dodge uconnect.

hatgirl223 said:
Slim bean 4.2.1 stable release mentions MAP in their change log. Have not tried it yet though. Looking to find one that works with Dodge uconnect.
Click to expand...
Click to collapse
As long as it supports MAP shouldnt be a problem. I´m still searching for a ROM/solution to read my mail on an BMW CIC entertaining system. Touchwiz does sms but no mail...
Cheers

[MOD] Google Wallet

Flashing this zip should allow you to use the Google Wallet app on your Verizon HTC One.
Now, I've tried it on mine, and it works fine, but I'm on the NOS ROM, version 1.0.1 from newtoroot, so I don't know if it works on other ROMs, so if you want to give it a shot, make sure to make a backup through Clockwork or TWRP first.
Also, if it doesn't work, try uninstalling and reinstalling the Google Wallet app.
If it doesn't work with other ROMs, then please upload your ORIGINAL build.prop, and I will do my best to keep up with making the changes and uploading the proper zips as quickly as possible.
The way this works is it just replaces the build.prop under the system folder with an edited version that allows the app to work by making it think it's a different phone that the app works with. So, if you have any issues because of the changed build.prop, let me know.
DOUBLE LINKS FOR MORE POWAHHHHHHH!!!!!!!!
https://www.dropbox.com/sh/au1mikbe7wibm28/-Mxdu4uHPa

Thanks for this, but I believe it belongs in the Themes & Apps section

So we just flash this in recovery? I am currently on NOS ROM 1.0.2. This is going to be fantastic if it works!! I thought we were never going to be able to use Google Wallet.
EDIT: Looks like it works fine on NOS ROM 1.0.2. I am going to test it out on Tuesday at work. Hopefully it works!

Syn Ack said:
Thanks for this, but I believe it belongs in the Themes & Apps section
Click to expand...
Click to collapse
Ok, mods can feel free to move it, it just looked like it belonged here.
Frankie1588 said:
So we just flash this in recovery? I am currently on NOS ROM 1.0.2. This is going to be fantastic if it works!! I thought we were never going to be able to use Google Wallet.
EDIT: Looks like it works fine on NOS ROM 1.0.2. I am going to test it out on Tuesday at work. Hopefully it works!
Click to expand...
Click to collapse
Awesome! Let me know if you have any troubles with it, it's working perfectly fine for me so far.
For future reference, yes, just flash in recovery.

Nice! thanks for this hopefully whenever s-off comes I can flash this

123421342 said:
Nice! thanks for this hopefully whenever s-off comes I can flash this
Click to expand...
Click to collapse
You can flash it now, just boot into recovery if you have a custom recovery installed.

Google Wallet on VZW CDMA HTC One
You obviously got an HTC One day one, unlocked, and custom recovery. I was waiting to hear more about whether or not our CDMA version of the HTC One had the Secure Element inside it, like the Sprint One does, and unlike the GSM One.
This post leads me to believe there is a Secure Element inside the VZW One. You have installed it and verified it working at a PayPass merchant?
I know that I missed the boat for now on bootloader unlock, but this is the last bit of information I need before throwing my support behind the HTC One on Verizon.
Thanks for this thread and the zip, OP!

Strange, I flashed it, and it doesn't seem to work, Google wallet gives me an error when I open it . What's even more weird is that I Skyped with a friend immediately before and after I flashed it and after it gave me this strange hue, only affecting the front facing camera. When I restored, it went away. This is on stock rom debloated with gray the wolf's mod.
Sent from my HTC6500LVW using xda app-developers app

I'm guessing there's no way to get this installed without root
Sent from HTC One with Xda app

megaorange1 said:
I'm guessing there's no way to get this installed without root
Sent from HTC One with Xda app
Click to expand...
Click to collapse
You have to be boot loader unlocked.

It didn't work with Andybones' Bonestock ROM. So I did a quick restore.
Should I post my original build.prop?

GrayTheWolf said:
You have to be boot loader unlocked.
Click to expand...
Click to collapse
That's what I was afraid of.
Sent from HTC One using xda-developers app

Mr.Preacher said:
It didn't work with Andybones' Bonestock ROM. So I did a quick restore.
Should I post my original build.prop?
Click to expand...
Click to collapse
I was able to install it and everything on NOS 1.0.2, but I tried to use it today at a vending machine and was unsuccessful. My NFC credit card worked fine. It recognized the phone and everything but payment was unsuccessful.
I wonder if this means the Verizon HTC One lacks secure element for payments?
NaitsirkC, have you been able to make NFC purchases with this mod?

I'm confused. Can we not download it from gapps?

jski711 said:
I'm confused. Can we not download it from gapps?
Click to expand...
Click to collapse
You can, but it won't work when you try to open it and use it because Verizon blocks it. This mod will allow you to use the app. It just doesn't seem to work for NFC payments for me right now.

jski711 said:
I'm confused. Can we not download it from gapps?
Click to expand...
Click to collapse
You can download it but you get an error when you try to run it saying it is not yet available for your device or mobile network. As I understand this is a Verizon only thing...I believe they are trying to push their own solution.

Awesomeness. I'm so pissed I missed out on bootloader unlock. Im enjoying a stock phone for the time being but man Verizon is turning into the "crapple" of Android!!!

jski711 said:
Awesomeness. I'm so pissed I missed out on bootloader unlock. Im enjoying a stock phone for the time being but man Verizon is turning into the "crapple" of Android!!!
Click to expand...
Click to collapse
Not so fast though. This allows Google Wallet to function on the phone, but I am not entirely sure the Verizon HTC One is able to make NFC purchases. Hoping NaitsirkC can chime in regarding if he has had success making NFC payments.

Frankie1588 said:
Not so fast though. This allows Google Wallet to function on the phone, but I am not entirely sure the Verizon HTC One is able to make NFC purchases. Hoping NaitsirkC can chime in regarding if he has had success making NFC payments.
Click to expand...
Click to collapse
Unless the VZW One is different then the GSM variant's, then Wallet won't work. The only HTC that is confirmed to have a Secure Element is the Sprint HTC One. I'm guessing that the VZW One doesn't have an SE and will rely on the NFC sim card that works with ISIS mobile payments. This special sim card has the SE built into it and ISIS looks to it to initiate payments. Google Wallet is not coded to look for an SE on a sim card, and I doubt that will change anytime soon.
If anyone is interested, look into SimplyTapp. They are working on a cloud based Secure Element that won't require the SE to be on the phone, thus enabling NFC devices like the DNA and VZW One to use a mobile payment system.

Zynesterysdan said:
Strange, I flashed it, and it doesn't seem to work, Google wallet gives me an error when I open it . What's even more weird is that I Skyped with a friend immediately before and after I flashed it and after it gave me this strange hue, only affecting the front facing camera. When I restored, it went away. This is on stock rom debloated with gray the wolf's mod.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah, the camera issue happened to me too, I'm working on a fix for it though. As for it not working, it's possible that there is too much of a difference between the build.prop on stock compared to the NOS ROM that it just simply doesn't work on stock.
Mr.Preacher said:
It didn't work with Andybones' Bonestock ROM. So I did a quick restore.
Should I post my original build.prop?
Click to expand...
Click to collapse
If you'd like, I'll try to make some time to edit it if you post it. If you want to try to do it yourself, just open up your build.prop, find the following values:
ro.product.model=
ro.product.name=
ro.product.device=
(these should all have something HTC related after the '=', I'm at work right now though and can't check to see what they are by default)
and change them to this:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
After doing this, save the edited build.prop to your SD card, because without S-off, it will get changed back after rebooting (unless the updated NOS ROM actually has system write support now, which I can't find out from any of the discussions, and don't want to flash it until all the bugs get worked out). After saving it, you'll need to put it into a flashable zip. If you don't have one, there's one here: http://forum.xda-developers.com/showthread.php?t=2418856
Make sure it's under the system folder; if it gets flashed to any other location, it won't work. Rezip, then flash away.
Frankie1588 said:
I was able to install it and everything on NOS 1.0.2, but I tried to use it today at a vending machine and was unsuccessful. My NFC credit card worked fine. It recognized the phone and everything but payment was unsuccessful.
I wonder if this means the Verizon HTC One lacks secure element for payments?
NaitsirkC, have you been able to make NFC purchases with this mod?
Click to expand...
Click to collapse
Frankie1588 said:
Not so fast though. This allows Google Wallet to function on the phone, but I am not entirely sure the Verizon HTC One is able to make NFC purchases. Hoping NaitsirkC can chime in regarding if he has had success making NFC payments.
Click to expand...
Click to collapse
bb12489 said:
Unless the VZW One is different then the GSM variant's, then Wallet won't work. The only HTC that is confirmed to have a Secure Element is the Sprint HTC One. I'm guessing that the VZW One doesn't have an SE and will rely on the NFC sim card that works with ISIS mobile payments. This special sim card has the SE built into it and ISIS looks to it to initiate payments. Google Wallet is not coded to look for an SE on a sim card, and I doubt that will change anytime soon.
If anyone is interested, look into SimplyTapp. They are working on a cloud based Secure Element that won't require the SE to be on the phone, thus enabling NFC devices like the DNA and VZW One to use a mobile payment system.
Click to expand...
Click to collapse
I haven't actually tried making any transactions on it, I just got the app working. Has anyone been able to make a successful purchase using this? If not, then it's kind of useless, and I apologize for wasting your time with it If it is working for some people, however, then can anyone tell me if they've been having the same issue with the camera as the first person I quoted? If it is working for some people, then I'll work on fixing it.

[ROM] [JLS36I] [Android 4.3.1] AOSP - Reference - 20131010

AOSP - Reference - JLS36G
As requested by undarated in my Reference ROM for the Galaxy Nexus GSM (Maguro), I took on the challenge to make a build for Toro. This is as pure as Android gets, compiled straight from Googles AOSP repository. I added absolutely nothing to the build (apart from the binairy drivers), partly because I want it to be as pure as possible for now and partly because I'm not a developer by any means
You can see this as a Reference ROM, all other ROMS are essentially based on this.
First thing that striked me was its speed. This ROM flies on Maguro and Iḿ sure it does the same on Toro! Google did a great job with 4.3.1 and is still continiously updating the AOSP sources
DISCLAIMER: As I don't own the device I couldn't test this myself of course, but undarated tested a pre-test and it didn't kill his phone
Anyway, here the link, it's on Google Drive (builddate 2013/10/10):
https://docs.google.com/file/d/0BwNDN4ITQ7phYzEyRldQLXZCeEE/edit?usp=sharing
The 'official' GApps (Google Play Store, GMail, Google+, etc):
http://goo.im/gapps
You can also use the experimental GApps for Android 4.3 (thanks to BaNkS, follow his thread here):
http://www.androidfilehost.com/?a=show&w=files&flid=7775
As this ROM is so pure, it even comes unrooted, you can find Chainfire's latest SuperSU here:
http://download.chainfire.eu/supersu
Changes to the AOSP tree can be found here:
https://android-review.googlesource.com/#/q/status:merged,n,z
If it works well and there's a demand for it, I try to update it regularly
Have fun

Thanks, I came here just to look for something exactly like this. I'll let you know if it blows up my phone (Don't worry, I know how to recover it).
First thing I tried doesn't work. Its an issue with AOSP and Verizon (CDMA?). MMS won't send if you are connected to WIFI. The MMS needs to go through the 3G/4G towers and the switch to 3G/4G doesn't happen. You need to manually turn off WiFi for it to work.

rufflez2010 said:
Thanks, I came here just to look for something exactly like this. I'll let you know if it blows up my phone (Don't worry, I know how to recover it).
First thing I tried doesn't work. Its an issue with AOSP and Verizon (CDMA?). MMS won't send if you are connected to WIFI. The MMS needs to go through the 3G/4G towers and the switch to 3G/4G doesn't happen. You need to manually turn off WiFi for it to work.
Click to expand...
Click to collapse
Will this MMS fix work?https://db.tt/JXsuV6r8
♦ToroNex-Vanir

Sweet! Wanted a stock rom updated JLS36G instead of JWR66V.

rufflez2010 said:
Thanks, I came here just to look for something exactly like this. I'll let you know if it blows up my phone (Don't worry, I know how to recover it).
First thing I tried doesn't work. Its an issue with AOSP and Verizon (CDMA?). MMS won't send if you are connected to WIFI. The MMS needs to go through the 3G/4G towers and the switch to 3G/4G doesn't happen. You need to manually turn off WiFi for it to work.
Click to expand...
Click to collapse
Is this clean build affected by the 4.3 radio issue? Do you reconnect to Data? Do you have any 3/4G switching issues?

yawdapaah said:
Is this clean build affected by the 4.3 radio issue? Do you reconnect to Data? Do you have any 3/4G switching issues?
Click to expand...
Click to collapse
I was only on WiFi. I haven't left my apartment yet but I will tomorrow night. I went to paranoid android but I'm not sure I'm going to stay on it.
Sent from my Nexus 7 using Tapatalk 4

jorgen2009 said:
AOSP - Reference - JLS36G
As requested by undarated in my Reference ROM for the Galaxy Nexus GSM (Maguro), I took on the challenge to make a build for Toro. This is as pure as Android gets, compiled straight from Googles AOSP repository. I added absolutely nothing to the build (apart from the binairy drivers), partly because I want it to be as pure as possible for now and partly because I'm not a developer by any means
You can see this as a Reference ROM, all other ROMS are essentially based on this.
First thing that striked me was its speed. This ROM flies on Maguro and Iḿ sure it does the same on Toro! Google did a great job with 4.3 and is still continiously updating the AOSP sources
DISCLAIMER: As I don't own the device I couldn't test this myself of course, but undarated tested a pre-test and it didn't kill his phone
Anyway, here the link, it's on Google Drive (builddate 2013/10/07):
https://docs.google.com/file/d/0BwNDN4ITQ7phOEFxa00tUDVCTHM/edit?usp=sharing
Experimental GApps for Android 4.3 (thanks to BaNkS, follow his thread here):
http://www.androidfilehost.com/?a=show&w=files&flid=7775
or the official GApps:
http://goo.im/gapps
As this ROM is so pure, it even comes unrooted, you can find Chainfire's latest SuperSU here:
http://download.chainfire.eu/supersu
Changes to the AOSP tree can be found here:
https://android-review.googlesource.com/#/q/status:merged,n,z
If it works well and there's a demand for it, I try to update it regularly
Have fun
Click to expand...
Click to collapse
Hey I see you made it over. I'm about to download and test it again myself.

yawdapaah said:
Is this clean build affected by the 4.3 radio issue? Do you reconnect to Data? Do you have any 3/4G switching issues?
Click to expand...
Click to collapse
Bump

Not to sound like a Debbie Downer here, but is there any reason why we shouldn't expect this ROM to have the same issues affecting every other 4.3 ROM for the VZW Gnex? I mean, I'm still going to flash it... but still. (BTW, I'm not being facetious, I really would love it if this ROM wasn't plagued with the data handoff issues other ROMS are struggling with.)

jaredsleboeuf said:
Not to sound like a Debbie Downer here, but is there any reason why we shouldn't expect this ROM to have the same issues affecting every other 4.3 ROM for the VZW Gnex? I mean, I'm still going to flash it... but still. (BTW, I'm not being facetious, I really would love it if this ROM wasn't plagued with the data handoff issues other ROMS are struggling with.)
Click to expand...
Click to collapse
Same good ol' data handoff issues apply here.
Sent from my Galaxy Nexus using Tapatalk 4

parkson said:
Same good ol' data handoff issues apply here.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
I'm sorry guys, but I can't do much here. This is way out of my expertise, even from all Toro experts themselves if I understand it correctly.
What I can do, is give you a new build. Google just released Android 4.3.1 on AOSP (JLS36I) and I build a fresh build. See OP for the link.
It seems the PA Gapps don't work (for Maguro at least). I tested my Maguro build with the 'official' Gapps and that does work however.
Let's hope this build fixes the known problems

jorgen2009 said:
I'm sorry guys, but I can't do much here. This is way out of my expertise, even from all Toro experts themselves if I understand it correctly.
What I can do, is give you a new build. Google just released Android 4.3.1 on AOSP (JLS36I) and I build a fresh build. See OP for the link.
It seems the PA Gapps don't work (for Maguro at least). I tested my Maguro build with the 'official' Gapps and that does work however.
Let's hope this build fixes the known problems
Click to expand...
Click to collapse
BAM!!!!!! 3g/4g handoff works and airplane mode works perfect coming back out. HECK YES!!!!!!

Flashed the new build with banks gapps working great thanks
Sent from my AOSP on Toro using XDA Premium 4 mobile app

Baby_Phil said:
Flashed the new build with banks gapps working great thanks
Sent from my AOSP on Toro using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Banks gapps?

yawdapaah said:
Banks gapps?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2012857
Sent from my AOSP on Toro using XDA Premium 4 mobile app

Not a huge issue, but the carrier text in the notification shade is "T-CDMA64" or something like that.

ironfisted said:
BAM!!!!!! 3g/4g handoff works and airplane mode works perfect coming back out. HECK YES!!!!!!
Click to expand...
Click to collapse
Any issues now that you tested for a day or two? Anyone else to confirm that 4.3.1 may have fixed hand-off issues?

someotherguy said:
Any issues now that you tested for a day or two? Anyone else to confirm that 4.3.1 may have fixed hand-off issues?
Click to expand...
Click to collapse
Still working great for me
Sent from my Galaxy Nexus using Tapatalk 4

I can confirm myself that data handoff issues are not there for me anymore. I'm running a testing build of Shiny ROM on 4.3.1 and all handoffs worked as flawlessly as 4.2.2. No grey bars, and quick switching. I did run this one last night and had no issues either. Glad we finally have working data again!!!

someotherguy said:
Any issues now that you tested for a day or two? Anyone else to confirm that 4.3.1 may have fixed hand-off issues?
Click to expand...
Click to collapse
I'm not seeming to have any data drop issues with handoff... 4.3.1 is running really nice. What are you guys using for kernel though in 4.3+? I'm still on stock but need color controls.

Any roms / kernels with Bluetooth 4.0?

Do any of the custom roms or kernels have bluetooth 4.0 support? The T989 uses a Broadcom 4330 chipset which has Bluethooth 4.0+HS. From what I understand the stock rom does not have the updated 4.0 drivers. This makes many of the new devices using Bluetooth Low Energy not compatible (many of the fitbit type devices).
Any ideas?
Thanks!

From what I know it has v3.0 with A2DP, HS and that's it. Remember this phone is from 2011. But the GS3 has 4.0
Sent from my SAMSUNG-SGH-T989 using Tapatalk

I dont think our phone has bt 4.0 its a hardware limitation from what i understand

Syzee101 said:
I dont think our phone has bt 4.0 its a hardware limitation from what i understand
Click to expand...
Click to collapse
Hmm... Even with the Broadcom 4330?
https://www.broadcom.com/products/Wireless-LAN/802.11-Wireless-LAN-Solutions/BCM4330
I've done some digging around and it appears that the 4330 can be made to enable BTLE. It requires updated Broadcom drivers and android 4.3+. There are a number of phones using this same chipset that have gotten BTLE to work (and pair with Fitbit like devices). Looks like the drivers need to be enabled in the kernel compile.
I've got a Samsung Galaxy Nexus running CM11 and it has the 4330 chipset as well. I used this .apk to check for BTLE support and it reports that it is enabled. Unfortunately I don't have any BTLE devices to test with it.
http://weimenglee.blogspot.com/2013/10/check-if-your-android-device-supports.html
If anyone is running a CM11 version can you use the file in the page I showed to check for support? If I get the time I may try CM11 on my wife's T989 and see....
EDIT:
Looks like with it is working with the Galaxy S2 ( i9100 intl.)
http://forum.xda-developers.com/showpost.php?p=48977119&postcount=147
Cool..... I may do the CM11 update then pick up a Fitbit and see if I can get it working....

oh, haha ive been misled this whole time! guess you learn something new everyday ill check it out on my device tonight. thanks for the find!

Syzee101 said:
oh, haha ive been misled this whole time! guess you learn something new everyday ill check it out on my device tonight. thanks for the find!
Click to expand...
Click to collapse
Did you get a chance to check for support?

Lost Dog said:
Did you get a chance to check for support?
Click to expand...
Click to collapse
sorry for the late reply,
I can confirm jedi mind trick 8 (4.1.2) doesn't support it... i haven't had much time to update to anything newer (CM11)

Syzee101 said:
sorry for the late reply,
I can confirm jedi mind trick 8 (4.1.2) doesn't support it... i haven't had much time to update to anything newer (CM11)
Click to expand...
Click to collapse
Thanks!
I've been trying to get CM11 working but I hit snag with the phone rebooting every few minutes (not a boot loop but after it's booted it's really unstable). Once I figure that out I can test!

Lost Dog said:
Hmm... Even with the Broadcom 4330?
https://www.broadcom.com/products/Wireless-LAN/802.11-Wireless-LAN-Solutions/BCM4330
I've done some digging around and it appears that the 4330 can be made to enable BTLE. It requires updated Broadcom drivers and android 4.3+. There are a number of phones using this same chipset that have gotten BTLE to work (and pair with Fitbit like devices). Looks like the drivers need to be enabled in the kernel compile.
I've got a Samsung Galaxy Nexus running CM11 and it has the 4330 chipset as well. I used this .apk to check for BTLE support and it reports that it is enabled. Unfortunately I don't have any BTLE devices to test with it.
http://weimenglee.blogspot.com/2013/10/check-if-your-android-device-supports.html
If anyone is running a CM11 version can you use the file in the page I showed to check for support? If I get the time I may try CM11 on my wife's T989 and see....
EDIT:
Looks like with it is working with the Galaxy S2 ( i9100 intl.)
http://forum.xda-developers.com/showpost.php?p=48977119&postcount=147
Cool..... I may do the CM11 update then pick up a Fitbit and see if I can get it working....
Click to expand...
Click to collapse
Hi, I tested it with this app and the result was LE not supported, see attached screenshot.
I'm on SlimKat ROM.