I have a stock, unrooted Galaxy Nexus GSM purchased new from Google currently running 4.3.
I have a FitBit Flex which will only sync with phones that have Bluetooth Low Energy support.
I can not find any information on any of the KitKat ROMs out there for Galaxy Nexus to see if I install it, will Bluetooth LE work?
If it does then work, my next concern would be if the FitBit app would recognize that the Bluetooth LE works and it would then be able to sync, or if it simply would still see it as a Galaxy Nexus which they do not list as a supported device: http://www.fitbit.com/devices
If anyone can offer me some advice here, I'd greatly apprecaite it!
Thanks.
(btw, sorry if this is in the wrong froum. please move it if it is)
adamwsh said:
I have a stock, unrooted Galaxy Nexus GSM purchased new from Google currently running 4.3.
I have a FitBit Flex which will only sync with phones that have Bluetooth Low Energy support.
I can not find any information on any of the KitKat ROMs out there for Galaxy Nexus to see if I install it, will Bluetooth LE work?
If it does then work, my next concern would be if the FitBit app would recognize that the Bluetooth LE works and it would then be able to sync, or if it simply would still see it as a Galaxy Nexus which they do not list as a supported device: http://www.fitbit.com/devices
If anyone can offer me some advice here, I'd greatly apprecaite it!
Thanks.
(btw, sorry if this is in the wrong froum. please move it if it is)
Click to expand...
Click to collapse
See here.
http://forum.xda-developers.com/showthread.php?t=2492436
With any kitkat rom I install only the modified apk from that thread and everything is ok!
Il you wanna stay with 4.3 you must install btle libraries as mentioned in the thread.
Gnex supports BLE with almost every KK rom.
(try BLE Checker on play store: on my Vanir says Supported!)
yes, and wrong place to ask this
caluz78 said:
See here.
http://forum.xda-developers.com/showthread.php?t=2492436
With any kitkat rom I install only the modified apk from that thread and everything is ok!
Il you wanna stay with 4.3 you must install btle libraries as mentioned in the thread.
Click to expand...
Click to collapse
THANK YOU, THANK YOU, THANK YOU!
I used The Nexus Root Toolkit (by WugFresh) to Unolock and Root my GNex. Then I used the link you gave me to get the BTLE files and the FitBit apk. I installed everything and it freakin' works!!! I'm so happy!
I'm so annoyed at Google for letting support of this device go after only 18 months. I bought it because they praised it as being thee flagship, unaltered, always up-to-date phone to have. I figured I'd be on the latest version of Android with this phone for many years. I wanted to keep it stock, but they've forced me to now go rooted. I suppose I could now flash a KK ROM, but I'm not sure what that would benefit me at this point.
Thank you again SO much for your help and fast reply! (Even if I did post this in the wrong place!)
Love XDA!
Ok, so I have to update what happened. Everything seemed to be working fine until I got into my car. My GPS has a bluetooth connection. It would connected, but then almost immediately the Bluetooth service would crash on my phone. Happened over and over again. Even after a reboot. Then when I got home, I tried it with my bluetooth speaker. Same exact thing. I figure the bluetooth binaries that I installed screwed up my connections that used to work. I even tried re-pairing them. Didn't help.
I gave up and decided to wipe everything and flash KK. I used CM11 nightly. Now everything, so far, is working as expected. GPS, speaker & fitbit. CM KK takes some getting used to over stock JB. I don't know what changes are KK and which are CM.
Related
Q&A for [ROM] [4.4.4] [SM-T31X] SlimKat (unofficial)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Hi,
I am using this ROM for a while now and I'm happy with it.
The only problem I have is Bluetooth audio streaming to a Bluetooth speaker.
It works perfect with version 7.8, but all other versions above I'm having problems with proper streaming.
Anyone else experience that?
Any ideas?
Waiz for.next.build. SlimRoms.merged a lot of upstream changes for Bluetooth now.
Send from OnePlus One using Tapatalk
Thanks for your quick response.
Do you know about this problem? It's working very good with 7.8, but all other versions are really bad for Bluetooth.
Anyway, I wait until you compile and upload the next release, and then I give it a try.
Thanks to you and I really appreciate your work. :thumbup:
Sent from my SM-T310 using XDA Free mobile app
@hejo1 next build sometimes next week. I had to reinstall my Xubuntu, syncing all source now again... SlimRoms will buildvnew official weekly tomorrow which will be the source.
Send from OnePlus One using Tapatalk
Hello
Can someone kindly suggest some settings for pac performance (governor, tcp, etc) that will speed up/fine tune this already slick rom.?
Slim ROM
I just wanted to answer a question regarding Slim Rom for galaxy Tab 3 8.0 not being able to root after flashing this ROM, you need to go to development and change root settings
What causes bad Bluetooth signal?
Newest Build
Hi,
i just installed Version 9 of this rom and it is actually very good and very fast.
I am just having the problem to create any folder on my homescreen.
If i move one icon over the other one it just jumps away.
Can anyone tell me how i can create a folder, to put some icons in there like for example a Systemfolder for all apps they have to do with system, or any other folder?
OK, finally i am able to geht some folders. But if i give them a name , i cant See für Name unless i open the folder.
And also the Name of the apps are gone.
Is that normal? Anyone have any idea?
Thanks.
t310 help
I'm trying to get this ROM flashed I'm running TWRP v2.6.0.0 will this work to install, every time i try to install it fails! I'm no expert, so any help would be great.
Thanks
[email protected]
Update your recovery @tadhope
Send from OnePlus One using Tapatalk
Thanks to all who helped, I updated twrp and it worked great now working on a galaxy s4 and Asus tf700t
Anyone know if you can use a galaxy note 3 unlocked T-Mobile on Metro PCS
Issue with Samsung Kies
i flashed Slimkat 9 ROM in my tab 3 311 and it worked. Dont have any problem. But i am no longer able to connect my Tab 3 311 to my pc via Samsung Kies. It says reboot your device every time and still nothing. Need Help
AalekhRoy said:
i flashed Slimkat 9 ROM in my tab 3 311 and it worked. Dont have any problem. But i am no longer able to connect my Tab 3 311 to my pc via Samsung Kies. It says reboot your device every time and still nothing. Need Help
Click to expand...
Click to collapse
Kies only works for unrooted stock roms.
If you want to backup contacts, sms etc. take avlook on My Phone Explorer.
Send from OnePlus One using Tapatalk
Android-Andi said:
Kies only works for unrooted stock roms.
If you want to backup contacts, sms etc. take avlook on My Phone Explorer.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
The thing is I have made an backup of my device applications, contacts and all by using Samsung kies before flashing this slimkat 9 ROM. Now as I want to restore those apps, instead to download them all over again, I can't connect with kies.
So if you can give me some tips how to get those apps restored back on my tab, it would be a great help.
P.S - I love this ROM, my first custom ROM. Plz help
There is no way to get Kies work on custom roms.
Maybe google if there is a way to extract a kies backup.
Send from OnePlus One using Tapatalk
Android-Andi said:
There is no way to get Kies work on custom roms.
Maybe google if there is a way to extract a kies backup.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Thanks a lot !!
One more thing... DSP manager keeps crashing every time I play a song or even open any music player.
Need Help
I flashed this ROM in my tab 3 311 and it is a great ROM. The only major problem i faced is I can't connect usb pendrive via otg cable.
Split view
Is there a split view function?! i didn't find anything in recent panel regarding split view.
package access helper has stopped
Hi,
im a bit new to the custom rom scene, i recently installed the latest slimkat build on my galaxy tab 3 8.0 and a few apps come up with the message "package access helper has stopped" i did a quick google search but seems like there's no fix. Just thought id ask here anyways if anyone knows of a work around? If not do you know what roms do work fully?
Cheers
After impatiently waiting for that day to arrive, here it is: Android 6.0 for our dear s4 is there thanks to our great dev @AntaresOne.
He brought us an unofficial cm13 for the unified s4 variants (jflte) which is stable enough to be used as a daily driver. All credits go to him.
Almost all the basic functions work.
FYI, it's a goodbye gift.
Download link: http://forum.xda-developers.com/showpost.php?p=63729768&postcount=312
Please, used the gapps suggested by the dev. Otherwise, you may face bootloop.
Enjoy but remember to thank @AntaresOne for this awesome work!
Reserved
Reserved...
I'm downloading it right now and going to give it a shot. Hopefully everything works out, including using streaming services like Netflix or Hulu Plus. Will report findings soon.
I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?
madcow007 said:
I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?
Click to expand...
Click to collapse
It's not implemented yet
Flash failed... Hmmm. Maybe corrupt data?
bbroad4455 said:
Flash failed... Hmmm. Maybe corrupt data?
Click to expand...
Click to collapse
It should work if the signature verification is skipped.
Also be sure that the downloaded file is correct; some of the mirrors do not yield the correct file andd have a different checksum.
The checksums should be:
Code:
cm-13.0-20151108-UNOFFICIAL-jflte.zip
Size: 297,677,777 bytes
CRC32: 919fb9b9
MD5: cfc714dda4be22afabdaa95e98f72bed
SHA-1: 97d993fccce699fdeb15bb1d39ad074220ce4a75
SHA-256: a3eff70e51b3c32f94808f9ade592d9cb9e1da07113773f2aa30d62503429295
Successfully flashed here. However internal and external mic don't work as well as auto time zones. Other than that, I haven't noticed an issue. I guess at first glance it also does not appear to be rooted.
Trying this on my Metro PCS S4 (jfltetmo) since it's not my daily driver and not connected to their network. So far it seems to be stable, but the battery usage is not good at the moment. The top of the list shows "Uncounted" using the battery the most. Not sure what that means. I am willing to help with testing this rom for this model jfltetmo, so if you want any info from this phone, let me know what and how to get it, and I will gladly share.
This thing did not work for me, leaving the phone stuck at the Galaxy S4 screen at boot. Restored using Odin and stock image, my device is the M919V.
CM 13flashed
Everything works fine but microphone. It does not work at all; call, skype, hangout, voice recorder, etc.
pointdotslash said:
Everything works fine but microphone. It does not work at all; call, skype, hangout, voice recorder, etc.
Click to expand...
Click to collapse
It's a known issues in all cm13 built. No fix for it yet.
Is this ROM dead? or will it be updated to work with microphone fix?
madcow007 said:
I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?
Click to expand...
Click to collapse
It cannot. Since ICS, T-Mobile's WiFi Calling has depended on TouchWiz to work. Sadly, for the S4, TouchWiz is stuck on 4.4.4 KitKat and likely won't be moving up to Lollipop. As of now, I keep a working KK TW Rom backup up as a Nandroid in case I need it but I've since resigned myself to moving on.
Need something to fix 6.0
I downloaded the Android 6.0 marshmallow for tmobile and the 6.0 gapps i flash them with TWRP recovery on my galaxy s4 I cannot create an APN because it says my device model is unknown and sims card is not inserted what do I need to do to fix this or is it just a CM bug.
Same^ any help
i used these micro gapps http://opengapps.org/
madcow007 said:
I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?
Click to expand...
Click to collapse
I think that a work around would be to call with hangouts... That's what I use to call over Wi-Fi
Sent from my SGH-M919 using Tapatalk
jfltetmo
vasolini said:
Trying this on my Metro PCS S4 (jfltetmo) since it's not my daily driver and not connected to their network. So far it seems to be stable, but the battery usage is not good at the moment. The top of the list shows "Uncounted" using the battery the most. Not sure what that means. I am willing to help with testing this rom for this model jfltetmo, so if you want any info from this phone, let me know what and how to get it, and I will gladly share.[/QUOTEiwould definatly interested in this that i have s4 with 5.1.1 rooted aicp rom w/twrp.
]
Click to expand...
Click to collapse
I recently loaded CM12 on my LG G3 D850 (only variant without Android 6 )
Everything went well until I tried pairing my SW3 via NFC via Wear, not only does it not recognize it, it makes the harp noise of nfc contact but does nothing and then stays on a very bright stock firmware that never goes off...very silly ..so I have to shut it off everytime
Already frustrated that Android 6 wasnt available at the end of three frustrating days of my first attempt at a ROM, now I am ready to switch back to (yucccckkk!!) stock if no solution is available.
I also upgraded my gApps to stock from mini (and that wiped out a whole buncha stuff but thats another story) and tried software update (but CM has its own updater which said nothing to update)
Would appreciate any ideas from the experts here, thanks in advance !
The NFC on the SW3 currently only transmits a URL to the "Android Wear" app. in PlayStore.
ranf said:
The NFC on the SW3 currently only transmits a URL to the "Android Wear" app. in PlayStore.
Click to expand...
Click to collapse
I didnt get you; even with that functionality in NFC, the SW3 connects without an issue with stock firmware but not with CyanogenMod - any reason for this ?
Did you factory-reset the watch after flashing CM on the phone? You need to (AFAIK).
It works for me CM11 + SW3
Working here too with cm 12.1
rojaxda said:
I recently loaded CM12 on my LG G3 D850 (only variant without Android 6 )
Everything went well until I tried pairing my SW3 via NFC via Wear, not only does it not recognize it, it makes the harp noise of nfc contact but does nothing and then stays on a very bright stock firmware that never goes off...very silly ..so I have to shut it off everytime
Already frustrated that Android 6 wasnt available at the end of three frustrating days of my first attempt at a ROM, now I am ready to switch back to (yucccckkk!!) stock if no solution is available.
I also upgraded my gApps to stock from mini (and that wiped out a whole buncha stuff but thats another story) and tried software update (but CM has its own updater which said nothing to update)
Would appreciate any ideas from the experts here, thanks in advance !
Click to expand...
Click to collapse
I'm not entirely sure what you mean: NFC doesn't do much, definitely can't use it to pair the device; which device has a "very bright stock firmware?"
Did you factory reset the watch and set it back up with the new phone rom?
gtriamy said:
I'm not entirely sure what you mean: NFC doesn't do much, definitely can't use it to pair the device; which device has a "very bright stock firmware?"
Did you factory reset the watch and set it back up with the new phone rom?
Click to expand...
Click to collapse
Haah...that was a tongue of the slip..what I meant to say was the stock firmware on the watch was very bright and annoying
Anyway I switched to a nightly CM12 and all was well. Thanks for responding ! Now just waiting for CM13 for the D850
rojaxda said:
Haah...that was a tongue of the slip..what I meant to say was the stock firmware on the watch was very bright and annoying
Anyway I switched to a nightly CM12 and all was well. Thanks for responding ! Now just waiting for CM13 for the D850
Click to expand...
Click to collapse
OP
Are you waiting on Official CM13? There are much better alternatives to be had for the D850, and if your insistent on CM, Unofficial CM13 has been out for sometime.
oogsaggie said:
OP
Are you waiting on Official CM13? There are much better alternatives to be had for the D850, and if your insistent on CM, Unofficial CM13 has been out for sometime.
Click to expand...
Click to collapse
not at all...so what are the alternatives ??
http://forum.xda-developers.com/att...ficial-d850-resurrection-remix-5-0-1-t2978808
http://forum.xda-developers.com/att-lg-g3/development/rom-orionlp-rom-lg-g3-d850-t3173254
Never used Orion, but used the RRemix MM Rom up until today on my D851. I assume it would be as reliable on the 850. I suspect you are only looking in "Original Development" instead of simply "Android Development" in the ATT G3 forums. Enjoy friend.
cm11 + sw3
QBANIN said:
It works for me CM11 + SW3
Click to expand...
Click to collapse
hi there,
can u tell me how
cause my phone is already have CM11 but can't sync with my SW3 :crying:
or did i must rooting my SW3 too?
pulpen said:
hi there,
can u tell me how
cause my phone is already have CM11 but can't sync with my SW3 :crying:
or did i must rooting my SW3 too?
Click to expand...
Click to collapse
Nothing special. Just installed Android Wear app and factory reset SW3.
Hello I'm not too knowledgeable in this... Right now I'm running 4.4.2... I was looking for a stable option in MM that could be rooted... Doesn't that exist?
Thanks for directing me if it does, honestly im not sure where to find the info...
I have a sm-t520 running build KOT49H T520UEUANI1
Thanks for the help!
Anyone?
Read this thread on how to Root and Install TWRP
http://forum.xda-developers.com/gal...-how-to-root-install-custom-recovery-t3087451
This MM Rom is PERFECT!
http://forum.xda-developers.com/gal...-xsm-t520-unofficial-cyanogenmod-13-t3466579/
I have had my Tab Pro rooted and running a Rom since I bought it. I just Rooted and Installed the above ROM on my Wife's Tab Pro last weekend. Took me less than 30 minutes to have everything done and she LOVES the new ROM.
paascal said:
Anyone?
Click to expand...
Click to collapse
install the CM13 that you can find in here. I have been running it on my T525 since the warranty expired, so for the last 2 years. Good luck
Does everything work out there are some glitches??
paascal said:
Does everything work out there are some glitches??
Click to expand...
Click to collapse
It would be helpful to everyone, including yourself if you were to give us a clue as to which Device you were inquiring about. As there are multiple versions of the Tab Pro, across many different sizes. It would also be helpful if you noted wether or not your Device has additional LTE, or is of the simpler WiFi ONLY variety.
That said the T320 (8.4" WiFi), is the (or was the...), best supported Device of the Family. Which had full CyanogenMod Support.
The T325 (8.4" LTE), OtOH never enjoyed any official Support, but, has otherwise Steller Support the whole time.
As for the others I can not speak on matters of which I know not, others will have to step up for the T52x (Tab Pro 10.2"), or the T90x (Tab Pro 12.2"), but I gather those were also working fine.
But, to answer your question, from the viewpoint of a T325 Owner. I find CM-13.0 to be very stable, and quick, and there are no issues worth reporting. 'Cause everything is working.
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
mik101 said:
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
Click to expand...
Click to collapse
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
drnightshadow said:
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
Click to expand...
Click to collapse
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
mik101 said:
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
Click to expand...
Click to collapse
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
drnightshadow said:
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
Click to expand...
Click to collapse
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
mik101 said:
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
Click to expand...
Click to collapse
Ok ok I have 2 whyred devices(2nd has smashed screen, i leave it connected in car)...hope that makes sense now
Let me simplified this... whyred and android auto is working! Yeah you need to hasel a bit but its working, at least in my Nissan OEM HUR from 2019. You just need to find right GAPPS version. I think its from feb. 2020, anythig newer breaks androidauto. Than just freeze all google stuff or it will update and breaks again. I cant remember all details couse it's too long ago I did it. Sorry, but you'll need to experiment by yourself.
Ahh almost forget...my FW is 10.0.3 I think. Not the latest.
Good luck and stay safe.
It's a big gapps problem and not about the devices. I am on redmi note 4x and have the same problem. My whyred have too. All original devices work. And my mido work before too. Its all about gapps.
I am very much thankful for all developers here but please don't talk its fixed. Its not especially on android 11 builds. There is non fully working gapps out just betas talk work but not. I have many devices. I flash and hundreds of others cellphones.
For all people search. Help to develop or wait for a right gapps build and report to all.