yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] andQlimax:
From the 4.2.2 to 4.3 changelog http://www.funkyandroid.com/aosp-JDQ39-JWR66V.html it seems that Bluetooth Low Energy has been disabled for Galaxy Nexus

Here the commits: https://android.googlesource.com/device/samsung/tuna/+/d07ee45 and https://android.googlesource.com/device/samsung/maguro/+/b40835e

The comment says: " Turn off BLE, GATT, and SMP of Bluetooth stack, bug 8664724 "

So it seeems they first implemented BLE for the galaxy nexus, and then disabled it because of a bug? It would be interesting to know what is the bug

Someone correct me if i'm wrong
[Samsung Galaxy Nexus] Kittiesoncrack:
Maybe It will be available when 4.3.1 or when 4.3.2 comes.
[Samsung Galaxy Nexus] andQlimax:
Yeah if the bug is solvable, unless it's an hardware / kernel related problem that they will not care to solve

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Stigy:
Any idea what would happen if a dev compiled their ROM with the changes made before that commit?

Possibility of it working?
[Samsung Galaxy Nexus] madd0g:
Hmm , reviewing the changelog, Xie did the same for old N7 (grouper), which seem to have the same BT chip Broadcom BCM4330. So must be something with that. But thing is, S3 has the same chip and they had BLE working with Samsungs stack. Would be interesting if this could work with undoing the commit.

What ****ing sucks in this matter is, that Google being Google can't comment on anything. If they said : look we had this issue and we can't deliver it, sorry", it would be better then just leaving us in the dark.
[Samsung Galaxy Nexus] Carlos_Manuel:
So for enabling those it should be enough to change -... FALSE to -...TRUE

Or then just removing those lines and adding the permission file line into device.mk

For BLE, gatt and SMP also kernel needs something.. I check what I can do with those things and also I have to check the kernel commits. :cool:
[Samsung Galaxy Nexus] Stigy:
Please let us know. That would make this phone last me SO much longer since its been really responsive and decent battery life lately.
[Samsung Galaxy Nexus] Carlos_Manuel:
I didn't find any BLE related files or texts from tuna's and also glass's kernel, and see,ed like even mako's kernel doesn't have nothing about it...

But, external_bluetooth_bluedroid has the files for BLE,'m no sure is CM's BT repository updated to JB 4.3's repository, but I'll check it out later.

My ROM unoffical CM10.2 should have those BLE, GATT, SMP things enabled in the upcoming version, but I don't know does those work..
[Samsung Galaxy Nexus] Carlos_Manuel:
BLE seems to be working and will be included to my upcoming unofficial CM10.2 build..
[Samsung Galaxy Nexus] madd0g:
Just a hint: it's surely not tested with a device yet, so let's take this claim with a grain of salt ;] If anyone has a BLE capable accessory, has a GN and is willing to try out a ROM build, please help.
[Samsung Galaxy Nexus] Carlos_Manuel:
+1
[Samsung Galaxy Nexus] Stigy:
I just got my Fitbit One (BLE) so as long as I can revert back to 4.2.2 I'm down. PM me if needed.
[Samsung Galaxy Nexus] madd0g:
This would be perfect, Pebble is one of such devices. Here's the thread : http://xdaforums.com/showthread.php?t=2380195

There seems to be some issues currently with the link, hope this gets resolved.

As far as reverting goes, I hope you know how to nandroid.
[Samsung Galaxy Nexus] Stigy:
Oh I can test with my Pebble as well - totally forgot.

I've been Nandroiding since the T-Mobile G1. :)

Edit: Crap, my device is toro (Verizon) - thought I mentioned that above.
[Samsung Galaxy Nexus] CommanderROR:
Hmm...how would you test with Pebble? It has dual mode radio and I'm jot sure if they even activated BTLE for Android yet. If you can telle how to set it to BT4.0 mode, then I'm willing to test. I've got a BT4.0 Tablet (Samsung) and the Gnex.
[Samsung Galaxy Nexus] Stigy:
Yup you're correct, got caught up in the hype, haha.

Pebble didn't activate BLE on their end so you can't test it yet as far as I'm aware.

I'd have to test with my Fitbit but I'd need a toro build to do so.
[Samsung Galaxy Nexus] madd0g:
Your tablet might have 4.0 hardware but isn't supported in software, at least not with the Android API until you run 4.3. Not sure if they implemented Samsungs BT BLE stack though.
[Samsung Galaxy Nexus] CommanderROR:
I'm pretty sure it's Samsung stack...

Os there an apk of that ble testing app? Might help clear this up until Pebble updates to new Android API...
[Samsung Galaxy Nexus] Stigy:
Its the Pebble watch itself that hasn't activated BLE, not the apps on your phone.
[Samsung Galaxy Nexus] speedyink:
My Motoactv has BT 4.0. I just don't know how to tell if that's the mode it would be using, since it works just fine with my 4.1.2 GNex.
[Samsung Galaxy Nexus] Stigy:
I think to test, you need a BLE-only device.

I noticed on my iPod touch though that it needed no setup. Maybe have your phone forget the watch and then try to sync it via the app?
[Samsung Galaxy Nexus] speedyink:
Ahh, that makes sense. Is there really that big of a power drain difference? I can leave my phone and watch paired all day with negligible difference in battery to with it not connected.

I'd have to flash 4.3 first to try it. Still not quite sure how to tell the difference..it usually syncs up using the companion app anyways. I think you're right, might be way easier to try a device that only supports BTLE 4.0
[Samsung Galaxy Nexus] Stigy:
If someone can compile an AOSP toro ROM with these commits un-done I can do testing.

I've never compiled a ROM from source although maybe this is a good time to learn.
[Samsung Galaxy Nexus] betizad:
I have a gsm galaxy nexus running 4.3 right now. I'd be able to make a cwm backup and test your ROM. I do have a fitbit too which only has v4.0 BT.

Pm me the details.
[Samsung Galaxy Nexus] edikat:
I also would love to have this functionality... can test with some BLE devices we have handy in the office....

Love my Galaxy Nexus (almost as much as my Nokia E90 :) ) and only keeping it around now for BLE.... else will be forced to upgrade which I don't want as I also have an Otterbox for it and its a really cool combo....

Many thanks!
[Samsung Galaxy Nexus] CommanderROR:
In that case, head over to the following thread and get testing.

One guy apparently already got it working with a Runtastic heartbeat sensor.

http://xdaforums.com/showthread.php?p=44120937#post44120937
[Samsung Galaxy Nexus] edikat:
many thanks CommanderROR... confirmed pairs with Polar H7 BLE device!!!

fantastique!
[Samsung Galaxy Nexus] jon9314:
Anyone have a toro and ble device?
[Samsung Galaxy Nexus] GalaxyDozie:
Apple doesn't add new features to old phones.. they just bring em along with old features.. they keep all 3rd party apps compatible while dropping support for their own in house software..

iPhone was my first phone.. Still use an iPhone 4 and it doesn't get new features..
[Samsung Galaxy Nexus] Stigy:
Yes and yes - I have toro and a BLE device (Fitbit One).
[Samsung Galaxy Nexus] Judge584:
Oh really ? So you have notification bar since day one? Oh wait ... No... Notification bar was an added feature from IOS5 ;) And what about apple ota update? Again a new feature added by apple even on old iphones.
[Samsung Galaxy Nexus] jon9314:
Would you mind testing this ROM for ble ?

http://xdaforums.com/showthread.php?p=44128360
[Samsung Galaxy Nexus] fifarunnerr:
And what about Maps turn by turn, Siri, Panorama, pictures while recording, Facetime over cellular, and probably even more? Not supported on the iPhone 4.

Source: http://support.apple.com/kb/ht5457
[Samsung Galaxy Nexus] Judge584:
Never said apple is delivering all new features to old devices, just said it does with some of them in reply to GalaxyDozie who has pretend just the opposite. And GalaxyDozie was replying to a thread were I said Apple is fully supporting devices older than 21 months, by saying that I was meaning in term of os updates. And os updates are not only good for new features, but also for the improvements they provide about bug correction and security enhancement. It is, for me, at least as much important.
[Samsung Galaxy Nexus] CommanderROR:
Please return to topic.

This is about BTLE on the Galaxy Nexus, not about iOS vs. Android!

Thanks.
[Samsung Galaxy Nexus] Seraz007:
well the latest cm10.2 has BLE :D
[Samsung Galaxy Nexus] Stigy:
Yup the commits have been merged I believe - and I have seen confirmation in other threads of it working with BLE devices.

I just need to find out if the Fitbit app needs updating or not to work. Guess I will have to test personally tonight.
[Samsung Galaxy Nexus] Carlos_Manuel:
BLE CHANGES For Maguro have not been Merged to CM10.2!

JFYI!

As you guys know, it seems like my ROM is the only JB 4.3 ROM for Maguro with BLE support..

I don't update that ROM anymore, I continue working on my older ROM.
[Samsung Galaxy Nexus] firecracker13:
I believe that fitbit has stated that it needs to update its app. I'm not sure if the .apk from an SIII, IV, or Note 2 would work though since they already have bluetooth sync support.
[Samsung Galaxy Nexus] Stigy:
I believe its the same APK, but Fitbit had to do BT for individual phones based on the way Samsung implemented Bluetooth Low Energy in their own way since Android didn't directly support it.
[Samsung Galaxy Nexus] madd0g:
http://xdaforums.com/showthread.php?t=2387107

No need for a custom ROM, the files can be used on stock image as well, since there are no dependencies on the framework.
[Samsung Galaxy Nexus] Leonardo777:
I have the Verizon Gnex (toro) and a fitbit. I tried the BLE libraries on the thread linked below. They are for tuna, but supposedly work for toro. Well, they did indeed activate the BLE and synced with the fitbit, but in the process, disabled BT 3.0 functionality. Almost there!! So does anybody know of any BLE libraries for toro that activate BLE without messing up BT 3.0/2.0?

http://xdaforums.com/showthread.php?t=2387107
[Samsung Galaxy Nexus] Sdobron:
All works fine in CM...
[Samsung Galaxy Nexus] Leonardo777:
Thanks, I thought that was a likely answer. I am on the Shiny 4.3 rom and like the near stock experience. But what the heck, might as well take the dive! I guess I'll have to flash CM. I'll flash the last stable (10.1.3) which I assume incorporates BLE support.

Again, thanks for the help.
[Samsung Galaxy Nexus] tshelby73:
Don't think ble was incorporated until cm 10.2
[Samsung Galaxy Nexus] Leonardo777:
All is good. After backing up files, I applied the BT libraries from wbedard and low and behold....BT headset works AND syncs with fitbit! I am one happy camper. Thanks all.
[Samsung Galaxy Nexus] HyperEscape:
So after reading all the 11 pages, can someone please confirm the following for a potential Galaxy Nexus buyer like me :)

The questions are for GT-i9250 Maguro (International Version)

1. Since recently Android 4.4 KitKat has also been released OTA for Galaxy Nexus, does the stock ROM contain support for Bluetooth Low Energy 4.0. Please correct me if I am wrong.

2. If remaining on 4.3, which ROMs have the working support now for BLE 4.0 (Stock, CM, any other, please post links) .

Thanks for your replies.
[Samsung Galaxy Nexus] jay-kopf:
Answer for Question 1:

AFAIK there is no Stock KitKat ROM for Galaxy Nexus:support.google.com/nexus/answer/3468085?hl=en

Google will not release a stock ROM with BLE enabled for Galaxy Nexus because Galaxy Nexus (Samsung GT-I9250) is only certified for Bluetooth 3.0 androidauthority.com/galaxy-nexus-passes-bluetooth-android-4-3-224336/

Answer for Question 2:

Cyanogenmod 10.2 has Bluetooth BLE for Galaxy Nexus (maguro).
[Samsung Galaxy Nexus] HyperEscape:
Thanks for the answers and correction.

So which ROM is best and stable one based on the pure or hybrid combination of CM, aOSp/AOSp with support for BLE 4.0.

Thanks for your support.
[Samsung Galaxy Nexus] djtutis:
As we can see, Google herself tried to make GNex users to buy her new Nexus 5 because of the prediction from analysts of low sales. So, they decided to abandon the development of this device to enforce GNex users to buy a bad copycat of LG G2...
[Samsung Galaxy Nexus] HyperEscape:
Ok I guess the phone which came after GNex was nexus 4...after which came nexus 5, so would be planning for it now...hopefully it should be compatible with all BLE apps and hardware.
[Samsung Galaxy Nexus] kam1kazze:
Anyone know if ROM mod (ex. Paranoid) with 4.4 kitkat supprot bluetooth 4.0 le?

I would buy a heart rate monitor bluetooth 4.0...
[Samsung Galaxy Nexus] Shambola:
I'm interested too.

I don't want to change phone for this reason.
[Samsung Galaxy Nexus] Carlos_Manuel:
What I know most of the KK ROMs for Tuna has BLE support enabled. And yes, AOSPA has BLE 4.0 support enabled for tuna https://github.com/AOSPA/android_device_samsung_tuna/commit/b1e4c6085c33ffc2de7d2ca4dbd9564c5e680504 And also all 3.0.x kernels for Tuna has BLE support...
[Samsung Galaxy Nexus] kam1kazze:
For Maguro is the same?
[Samsung Galaxy Nexus] Carlos_Manuel:
Tuna= Maguro - gsm

Tuna= Toro - cdma

Tuna= Toro+ - cdma
[Samsung Galaxy Nexus] Shambola:
Cool,

now I'm waiting for Vanir's commit.
[Samsung Galaxy Nexus] Carlos_Manuel:
https://github.com/VanirAOSP/device_samsung_tuna/commit/07750cc516faede3e6445bdfa92fbce881cf4c28
[Samsung Galaxy Nexus] Shambola:
Cool!! You made my day
[Samsung Galaxy Nexus] zhourj:
how to use these two files?

I just dug out my old nexus, I want to try enabling the BLE on the stock rom, can I do it? And how to use these two files on Github? Just make a zip and flash?
[Windows Mobile Development and Hacking General] ohault:
Hi,

I wonder if somebody has already been able to create a ROM from scratch using Microsoft Plateform Builder.

Olivier
[Windows Mobile Development and Hacking General] mamaich:
you cannot. PB does not contain a sample platorm that can boot on PXA 263.
[Windows Mobile Development and Hacking General] ohault:
There is already a driver for INTEL PXA 263 and two BSP published on

http://openwince.sourceforge.net/

http://openwince.sourceforge.net/pxa2x0/

Based on http://wiki.xda-developers.com/wiki/HimalayaHardware, and openwince a specific BSP could be created for Himalaya Hardware.

http://msdn.microsoft.com/embedded/usewinemb/ce/bsp/howtos/default.aspx
[Windows Mobile Development and Hacking General] zhoudan:
maybe we should try WinCE 5.0 platform builder

I'm trying to install an evaluation version, it supports xscale, worth trying
[AT&T Samsung Galaxy S II SGH-I777] steelforce:
OK, here's the deal. My i777 was running SlimROM, updated, and now my power button is inop. Flashed back to stock ICS, but I forgot to do one critical step - a complete wipe before installing. Now my phone gets stuck at the "Rethink Possible" screen, and I can't do anything else.

I've booted into 3e recovery and tried recovery --wipe_data through adb, but it still hangs. (as suggested here). I've got a jig, forced it into download mode, and tried flashing another ROM, but I still get stuck on the Rethink Possible screen.

Is there a way that I can basically nuke all the contents of the phone so I can use it again? I've read through most of the documentation for adb, but I don't see an option.
[AT&T Samsung Galaxy S II SGH-I777] Caligula36:
Id wait until a dev chimes in, but my understanding is that as you can still get into DL mode, ODIN would be your best bet. Id flash one of the all in one ODIN ICS packages that also contain boot loaders (LL6 would be most recent). As a last resort you can also flash the stock .pit file and repartition the whole phone, BUT BE SURE TO BACKUP YOUR EFS FOLDER if possible. I say this as I did not do this and now have a generic IMEI on my phone, hindering some aps from working.

ADB is able to reformat and flash ROM packages as far as i know, though it should be unnecessary as long as you can still use ODIN. The only reason i used ADB was to resurrect a S2 i bought of someone that flashed a ROM from a i9100.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
You need root access to format the data partition. I don't use adb a lot, but I think you can boot into recovery, then "adb shell", then "format data." You might have to type "su." If that doesn't get you out of the Rethink Possible screen, the I would format data, format system, and format cache. Then turn the phone off, by pulling the battery if necessary, and enter download mode and flash the full stock distribution. As the previous poster suggested, UCLL6 would be a good choice. You can get it from the download repository. See the link in my signature.
[AT&T Samsung Galaxy S II SGH-I777] steelforce:
Thanks. I forgot to grab the phone before I left for the office this morning, so I'll try it when I get home later tonight.
[AT&T Samsung Galaxy S II SGH-I777] steelforce:
So, home with my phone. When I get into the shell, format isn't a valid command:

shell@android:/ $ format
format
/system/bin/sh: format: not found

Trying to su ends up segfaulting, so I don't think it's a permissions issue. Other sources suggest using fastboot, but as I understand it, the i777 doesn't support it.

I'm looking at the mounts - is there documentation on which of the /dev/block/mmcblk0pX partitions map to the mount points? I'm familiar with Linux (at least enough to get me in trouble), but I'm lost on where to go next.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
You have to have root access to do the format command. Requires the # prompt, like this:

adb shell
$ su
# format data
# exit
$ exit

Probably, cache is mounted but system and data are not mounted. It shouldn't make any difference though, if I remember right.

If you can't get the su command to give you the # prompt, then maybe adb is not connected to the daemon correctly?

Edit:

I have never used adb in recovery before, so for my own interest, I decided to do a little experimentation. First of all, to get a hash prompt in shell try

adb root

followed by

adb shell

From reading, it seems some people say both wipe and format commands should work in shell in recovery, but I couldn't get them to work. I would get "/sbin/sh: format: not found" error. So the work around is this:

adb shell
~ # mount /data
~ # rm -rf /data/*
~ # reboot

This will recursively force the removal of the contents of the data directory. I did not test this, but I did test "rm -rf /cache/*" and successfully removed the contents of the cache directory, so I know it should work.

If your system still doesn't boot, you could wipe cache and system as well as data and then reboot into download mode and flash the full stock tar

adb shell
~ # mount /data
~ # mount /system
~ # rm -rf /cache/*
~ # rm -rf /data/*
~ # rm -rf /system/*
~ # reboot download
[AT&T Samsung Galaxy S II SGH-I777] steelforce:
Ugh - adb root fails with the following error:

D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb root
adbd cannot run as root in production builds

Looks like it's because the build that I have flashed doesn't have root. Wicked catch-22, since I can't root the phone until I wipe the cache to actually boot.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Well, yes, you need root. You could flash one of the stock plus root packages, probably Entropy512's original uckh7 plus root since it has busybox, with odin, see links in my sig. I didn't see anything in your original posts that indicate the flash would fail.
[AT&T Samsung Galaxy S II SGH-I777] steelforce:
The flash doesn't fail, but it's never able to boot past the AT&T "Rethink Possible" splash screen. I've tried flashing a couple of different packages, but i'll try some more tonight.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Flash the rooted package and you will then have root. Whether the phone boots or not, the system will then contain the superuser.apk and the su binary. I suggested Entropy512's package because I'm not sure but I think you need busybox to use the unix commands in adb in recovery. My stock plus root packages don't have busybox, and if you can't boot, you can install it from the play store. Once you have root in the system, then adb root should succeed.
[AT&T Samsung Galaxy S II SGH-I777] steelforce:
I tried both of Entropy512's packages from here. Flashed them and tried to boot, both hung at the Rethink Possible screen. Rebooted into recovery, was able to connect to it via adb - but adb root failed on both.

I'm getting closer and closer to punting and picking up a Nexus 4 after this....
[AT&T Samsung Galaxy S II SGH-I777] y0va:
With lineage recovery I do a full wipe like:

mkfs.ext4 -qFF /dev/block/by-name/userdata
mkfs.ext4 -qFF /dev/block/by-name/cache
mkfs.ext4 -qFF /dev/block/by-name/system
[AT&T Samsung Galaxy S II SGH-I777] isaqi_veras:
Is there any command to format system/cache/data by ADB? I would like to do the procedure without using TWRP
[Nexus 4 Accessories] 4Pr3mier:
Jaybird Bluebuds X or Aluratek ABH03F

Has anyone tried the Alurateks ones? They look very much like the Bluebuds X and could just be an imitation.

If anyone has any experience with BOTH, or know the differences, please share.

I have purchased and tried the Bluebuds X before and like a number reviewers on Amazon, could never get it to fit right in the ear.

The nozzle size of the buds were pretty big (>6.0mm diameter) and I didn't like the rubberized cord or those wing attachments.

Obviously I'm not trying to cheap out on a product, I just want something that is similar and fits better.

I might just have to buy some Comply T500 tips and see if it helps.
[Droid RAZR M Q&A, Help & Troubleshooting] syde1020:
My wife's phone is fully stock, and I believe up to date with the latest ota. The last one she received was around a month ago but since then she's had a lot of trouble with reboots. I've done a factory restore hoping it would correct the problem but it didn't. Anyone have a similar problem PR maybe an idea for a fix??
[Droid RAZR M Q&A, Help & Troubleshooting] sloosecannon:
If you're stock unrooted you could try going to VZW for warranty. Sounds like system may be messed up...

If you're adventurous, you could plug it in and run logcat and see what errors pop up before a reboot
[AT&T LG Optimus G] pivotraze:
I think this might have been answered before, but why can't the LG Optimus G use Google Wallet to make NFC payments? I use Vanilla Rootbox (the May 18 build) and it lets me install it, but I've been worried that running it might damage something since I read we can't use it.

My main question: Why can't we use it when the Nexus 4 (by most all regards, the same phone) can?
[AT&T LG Optimus G] Jophess:
No secure element.
[AT&T LG Optimus G] pivotraze:
So then I assume the Sprint version has it, and we don't?

http://xdaforums.com/showthread.php?t=2168685
[AT&T LG Optimus G] Jophess:
Since it works for them, I guess so. I don't really know anything about it other than the ATT OG not having it so it will never work.
[AT&T LG Optimus G] adfurgerson:
http://forums.att.com/t5/Android-Di...-called-quot-ISIS-quot-more-info/td-p/3265103

This may be why.
[AT&T LG Optimus G] pivotraze:
yeah. And our phone IS isis compatible (well, in the two cities it exists in, which mine is not one of.)
[AT&T LG Optimus G] Stealyourface:
Your assumptions are wrong. Go through this thread and you'll see that it doesn't work. Not without the xposed mod. And even then it's a hit and miss.
[AT&T LG Optimus G] pivotraze:
So why can't we use the Xposed mod? I just have a hard time believing that the Spring LGOG and AT&T LGOG could be so different (I thought the only real difference was the camera, TBH. I'm probably way off though. Idk.)
[AT&T LG Optimus G] Stealyourface:
You can use the xposed mod. It's not just for us. It's for any phone. The xposed framework has more use than just the wallet mod as well. But if I had to guess, I'd say it'd be hit and miss as well. (besides the radios, design change, and camera, they pretty much are the same)
[AT&T LG Optimus G] nygfan760:
We don't have secure element because AT&T sucks and wants to use ISIS which isn't even available outside of like two places.

There is this by CMs team https://play.google.com/store/apps/details?id=com.tapp