Database Develop

1.3 is out!

Got this tweet today:
1.3 Firmware is here! The Award-Winning NOOK Color now has People, Time, SI, Fitness & more. Details: bit.ly/pty5x6
I wouldn't suggest updating until we get a root going on it.

Yep, here is the official info on the B&N site:
Barnes & Noble is providing a firmware update for NOOK Color that contains exciting new features and provides ongoing performance improvements. Among the new features, NOOK Color v1.3 now offers access to special edition NOOK Magazines™ with enhanced interactivity and bonus features. The software update will be automatically downloaded to devices that are registered and connected to Wi-Fi®, beginning the week of August 22nd. There's no need for you to take any action. However, if you'd prefer to update your device immediately, the software update is also available via a manual download offered here, with further instructions below. To check the current software version of your NOOK Color, please click here to learn more.
Get Version 1.3.0 Today
What's new in Ver1.3.0?
The NOOK Color Ver1.3.0 update contains new features and enhancements, including:
Access to a selection of new special edition NOOK Magazines -- People, Time, Sports Illustrated, Fortune, Parents, and Fitness – featuring print edition content, plus video, audio and fun extras.
Access to the largest digital magazine selection available anywhere.
Print subscribers to People, Time, Sports Illustrated, and Fortune get free NOOK editions of those magazines.
Parental control to easily disable the Web browser.
Ongoing enhancements to Wi-Fi connectivity and other performance improvements.

I assume they're still running Froyo

fireware 1.3
Loaded on the stock side of a dual-boot Nook Color.
Seems faster boot so far and a lil faster web browser.
And yes.... still Froyo.

votinh said:
I assume they're still running Froyo
Click to expand...
Click to collapse
2.2.1 - here's the build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MASTER
ro.build.display.id=MASTER.1.3.0
ro.build.version.incremental=1.3.0
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=Wed Aug 17 15:21:14 PDT 2011
ro.build.date.utc=1313619674
ro.build.type=user
ro.build.user=build
ro.build.host=dhabuildimage17
ro.build.tags=test-keys
ro.product.model=NOOKcolor
ro.product.brand=nook
ro.product.name=zoom2
ro.product.overall.name=NOOKcolor
ro.product.device=zoom2
ro.product.board=zoom2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=BarnesAndNoble
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=zoom2
ro.build.sourceversion=full
ro.build.description=1.3.0.521.int.enc.rrdp.s44977
ro.build.updatetype=Full
ro.build.fingerprint=enc/zoom2/zoom2/zoom2:2.2.1/MASTER/1.3.0:user/test-keys
# end build properties
###################################
#Browser Performance Optimizations
###################################
browser.tioptimization=true
connection.concurrent=10
###################################
# system.prop for zoom2
# This overrides settings in the products/generic/system.prop file
#
# rild.libpath=/system/lib/libreference-ril.so
# rild.libargs=-d /dev/ttyS0
# ro.sf.lcd_density=240
ro.sf.widthpixels=600
ro.sf.heightpixels=1024
ro.sf.lcd_density.xdpi=169.33333
ro.sf.lcd_density.ydpi=169.33333
opencore.asmd=1
keyguard.no_require_sim=1
wifi.interface=tiwlan0
alsa.mixer.playback.master=DAC2 Analog
alsa.mixer.capture.master=Analog
#ro.media.dec.aud.wma.enabled=1
#ro.media.dec.vid.wmv.enabled=1
dalvik.vm.heapsize=64m
ro.opengles.version=131072
ro.sf.hwrotation=270
# Define JPEG codec to load. (Set libskiahw with 1 & Set ARM with 0)
jpeg.libskiahw.decoder.enable=1
# Define JPEG Threashold for Image size (bytes)
jpeg.libskiahw.decoder.thresh=1000000
browser.tioptimization=true
connection.concurrent=10
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
#Disable some feature depending on the board capabilities
ro.disable.bluetooth=0
ro.disable.camera=1
ro.disable.hdmi=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=false
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

lostboy1952 said:
Loaded on the stock side of a dual-boot Nook Color.
Seems faster boot so far and a lil faster web browser.
And yes.... still Froyo.
Click to expand...
Click to collapse
How did you go about updating the stock side? I have Phiremod as the first boot, and stock Nook as the second. I've updated Phiremod before just using Clockwork, but not sure how I'd update the stock side.
thanks!

According to this thread over at B&N forums:
http://bookclubs.barnesandnoble.com...folk/m-p/1139798/message-uid/1139798#U1139798
B&N has overclocked to 900mhz on stock.

doncaruana said:
2.2.1 - here's the build.prop:
ro.build.version.incremental=1.3.0
ro.build.date=Wed Aug 17 15:21:14 PDT 2011
ro.build.date.utc=1313619674
ro.build.description=1.3.0.521.int.enc.rrdp.s44977
ro.build.fingerprint=enc/zoom2/zoom2/zoom2:2.2.1/MASTER/1.3.0:user/test-keys
Click to expand...
Click to collapse
Thanks for posting that, I'm updating my other thread with this.

jpeg42 said:
According to this thread over at B&N forums:
http://bookclubs.barnesandnoble.com...folk/m-p/1139798/message-uid/1139798#U1139798
B&N has overclocked to 900mhz on stock.
Click to expand...
Click to collapse
Are they using Dal's kernel?

Any kernel version changes?

what wifi improvements? adhoc/infrastructure fix maybe?

Is it safe to allow the update to go through if you are running CM7 off of SD?
I would hate to find any nasty surprises like a force boot from emmc only.

Imbroglio said:
Is it safe to allow the update to go through if you are running CM7 off of SD?
I would hate to find any nasty surprises like a force boot from emmc only.
Click to expand...
Click to collapse
No way. The boot firmware will always boot the sd card first. If it doesn't, I will personally go to the closest BN store and punch the first staff person I see.

Imbroglio said:
Is it safe to allow the update to go through if you are running CM7 off of SD?
I would hate to find any nasty surprises like a force boot from emmc only.
Click to expand...
Click to collapse
Why not remove your uSD off the NC and let the update runs?

Imbroglio said:
Is it safe to allow the update to go through if you are running CM7 off of SD?
I would hate to find any nasty surprises like a force boot from emmc only.
Click to expand...
Click to collapse
Just remove the SD card and update like normal.
Sent from my NookColor using Tapatalk

lostboy1952 said:
Loaded on the stock side of a dual-boot Nook Color.
Seems faster boot so far and a lil faster web browser.
And yes.... still Froyo.
Click to expand...
Click to collapse
Lostboy, how did you do the update? I was thinking that might be able to by just booting into Nook OS and doing the update. I am dual boot with CM7 nightlies.
--bill

According to the developer of DVD Catalyst 4, the 1.3 update solves the video playback degradation issue that was introduced with 1.2:
http://www.tools4movies.com/2011/08/bn-nookcolor-1-3-update/
That's very good news for anyone who wants to stick with the stock OS.

dsf3g said:
According to the developer of DVD Catalyst 4, the 1.3 update solves the video playback degradation issue that was introduced with 1.2:
http://www.tools4movies.com/2011/08/bn-nookcolor-1-3-update/
That's very good news for anyone who wants to stick with the stock OS.
Click to expand...
Click to collapse
That's good news, that means new video drivers and/or kernel, once B&N releases the source for 1.3 the benefits should come rolling into CM7.

joenathane said:
That's good news, that means new video drivers and/or kernel, once B&N releases the source for 1.3 the benefits should come rolling into CM7.
Click to expand...
Click to collapse
I wasn't aware B&N was releasing any of their source code....

If I am running CM7 on emmc then I don't do anything. Is that right?

[ROM] S5570XWKS7 [15.10.2011][Android 2.3.5]

S5570XWKS7:
Android 2.3.5
Code:
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XWKS7
ro.build.version.incremental=XWKS7
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Sat Oct 15 17:15:04 KST 2011
ro.build.date.utc=1318666504
ro.build.type=user
ro.build.user=root
ro.build.host=DELL133
ro.build.tags=release-keys
ro.product.brand=samsung
ro.product.model=GT-S5570
ro.product.name=GT-S5570
ro.product.device=GT-S5570
ro.product.board=GT-S5570
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-S5570
ro.product.cpu.abi=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=msm7k
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-S5570-user 2.3.5 GINGERBREAD XWKS7 release-keys
ro.build.fingerprint=samsung/GT-S5570/GT-S5570:2.3.5/GINGERBREAD/XWKS7:user/release-keys
# Samsung Specific Properties
ro.build.PDA=S5570XWKS7
ro.build.hidden_ver=S5570XWKS7
ro.build.changelist=650682
ro.build.buildtag=
# end build properties
Download:
CSC:FOP
http://hotfile.com/dl/133844590/52f89f3/GT-S5570_FOP_S5570XWKS7_S5570OXXKS2_S5570XWKS2.rar.html
CSC:DBT
http://hotfile.com/dl/134566361/137fb74/GT-S5570_DBT_S5570XWKS7_S5570XWKS2_S5570DBTKS1.rar.html
Pass: sampro.pl

wifi dis- and reconnects several times with this rom (sometimes the device doesn't reconnect too).
when i use a rom like S5570XEUKP1 for example, everything's good.
anybody have a solution for this?

no one have this problem with this fw too?

/push......

Nope never had this kinda of problem with this firmware.
I only reverted back to 2.2.1 (for now) because sometimes there was some lag and the animations were not so smooth as the old ones.

something really strange here -.-
when i google my problem with ks7, i don't find more user with same problem.
i reset my router too, but nothing chnages.
i do not understand, i'm at a loss.

ps2011 said:
something really strange here -.-
when i google my problem with ks7, i don't find more user with same problem.
i reset my router too, but nothing chnages.
i do not understand, i'm at a loss.
Click to expand...
Click to collapse
If your router supports it, try to set the WiFi to one of the 1st-6th channels.
I've seen some smartphones acting funny when the router wifi is working at 11-12 channels.

i see now, wifi problem relates not only to ks7, but all 2.3.5. fw's.

added: S5570XWKS7 CSC:DBT Android 2.3.5

Germany.
DBT = GERMANY
Am i right ?

moving this thread to android development

ps2011 said:
i see now, wifi problem relates not only to ks7, but all 2.3.5. fw's.
Click to expand...
Click to collapse
Hmm, maybe you should try to change the wifi settings? Worked for me!
1. >Settings > Wireless and networks > Wi-Fi settings.
2. Press menu-button > Advanced.
3. Change the 'Wi-Fi sleep policy'.
That solved the trick for me at least!

[System Dump] Android 4.1 Jelly Bean SDK...Let the hacking begin!!!

Android 4.1 Jelly Bean SDK Image System Dump
Here you go, I dumped the system of Android 4.1 Jelly Bean from Android 4.1 SDK image.... Let the hacking begin!!!
Download
Android-4.1-JellyBean-SDK-SystemDump.zip
MD5: 9461D2F1ED6B47D939AC8C52AC798A39
Build Prop File Content
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRN83C
ro.build.display.id=sdk-eng 4.1 JRN83C 391408 test-keys
ro.build.version.incremental=391408
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1
ro.build.date=Sat Jun 23 01:40:53 UTC 2012
ro.build.date.utc=1340415653
ro.build.type=eng
ro.build.user=android-build
ro.build.host=vpak16.mtv.corp.google.com
ro.build.tags=test-keys
ro.product.model=sdk
ro.product.brand=generic
ro.product.name=sdk
ro.product.device=generic
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=sdk-eng 4.1 JRN83C 391408 test-keys
ro.build.fingerprint=generic/sdk/generic:4.1/JRN83C/391408:eng/test-keys
ro.build.characteristics=default
# end build properties
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
The system dump for Android 4.1 has been pulled from the GSM Galaxy Nexus update, and ready for developers to get their talented little hands on
Download:http://minus.com/lby5qoGOSNGmyS
What i've done until now:
- /system/app
- fonts, framework, media, tts, usr, xbin
- copyed busybox from CM9
- Edited build.prop
- Added some missing files in /system/bin
Doing now:
Unpacking boot.img
Problems:
ramdisk

Sweeeeeeeeeeeetttttt

Let make this post on the top of thread....make easy for all our talent Rom Developer

:good:

oh~ wow!!!

NICE...but it would be better if a moderator or a senior developer makes a thread with more info...AND MAKE IT STICKY.....so that its more helpfull

Does it work, i mean... even a bit on our N7000 ?

Wait for imilka, cm team or kang team
Sent from my GT-N7000 using Tapatalk 2

Nice bro thanks :victory:

sorcio46 said:
Does it work, i mean... even a bit on our N7000 ?
Click to expand...
Click to collapse
ofcourse it will.....we have a dual core 1.4GHZ processor...Its a BEAST...it can take this Bean without much problems ...and this is an update to ICS...so our Note was made for ICS...It can take this too...

Rulinglionadi said:
ofcourse it will.....we have a dual core 1.4GHZ processor...Its a BEAST...it can take this Bean without much problems ...and this is an update to ICS...so our Note was made for ICS...It can take this too...
Click to expand...
Click to collapse
Ya...not much different...can't wait jellybean port at note

Rulinglionadi said:
NICE...but it would be better if a moderator or a senior developer makes a thread with more info...AND MAKE IT STICKY.....so that its more helpfull
Click to expand...
Click to collapse
Dun worried all senior developer will releases their own custom rom soon...

kfheaven said:
Dun worried all senior developer will releases their own custom rom soon...
Click to expand...
Click to collapse
True...we will be seeing a CM 9.1 midNightlies ....soon... :silly:

My body is ready.

Rulinglionadi said:
ofcourse it will.....we have a dual core 1.4GHZ processor...Its a BEAST...it can take this Bean without much problems ...and this is an update to ICS...so our Note was made for ICS...It can take this too...
Click to expand...
Click to collapse
Depending on lib dependancy on kernel drivers the best you can hope for will be a port based on ICS kernel which will be fugly.
Frameworks etc in their compiled state are only reversible to smali and xml so the significance of this isnt great for any real development. First one needs to wait for flagship releases and then the source to drop.
Sent from my GT-N7000 using xda premium

Lol, kinda defeats the whole standardization point,
Should be just as easy as mapping points. The interchangability is on the wrong layer. Wonder why that still isnt possible in OS land
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Lol, kinda defeats the whole standardization point,
Should be just as easy as mapping points. The interchangability is on the wrong layer. Wonder why that still isnt possible in OS land
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Go for it then
Sent from my GT-N7000 using xda premium

this is for the samsung galaxy note or to sdk on computer ? .

:good:

kfheaven said:
Android 4.1 Jelly Bean SDK Image System Dump
Here you go, I dumped the system of Android 4.1 Jelly Bean from Android 4.1 SDK image.... Let the hacking begin!!!
Download
Android-4.1-JellyBean-SDK-SystemDump.zip
MD5: 9461D2F1ED6B47D939AC8C52AC798A39
Build Prop File Content
Click to expand...
Click to collapse
:good::good::good:All the very Best our whole wishes with you......cant wait to be ported in jellybeam android v4.1.... :good::good::good:

OMAP4 Bluetooth 4.0 BLE

it seems that is working, tried it on 4.4.2, but no OAD support..
to enable it add the following line to android/system/device/motorola/omap4-common/common.mk
frameworks/native/data/etc/android.hardware.bluetooth_le.xml:system/etc/permissions/android.hardware.bluetooth_le.xml
next to
frameworks/native/data/etc/android.hardware.usb.host.xml:system/etc/permissions/android.hardware.usb.host.xml \
and (device specific) system/device/motorola/maserati/bluetooth/bdroid_buildcfg.h
#define BTA_DM_COD {0x1A, 0x01, 0x14}
#define BTIF_HF_SERVICES (BTA_HSP_SERVICE_MASK)
#define BTIF_HF_SERVICE_NAMES { BTIF_HSAG_SERVICE_NAME }
#define PAN_NAP_DISABLED TRUE
#define BLE_INCLUDED TRUE
#define BTA_GATT_INCLUDED TRUE
#define SMP_INCLUDED TRUE
after
#define BTM_DEF_LOCAL_NAME "Motorola Droid 4"
tried with new bluetooth firmware from https://github.com/TI-ECS/bt-firmware, is working but is not stable.
the default firmware is working well with the sensor tags

lucize said:
it seems that is working, tried it on 4.4.2, but no OAD support..
Click to expand...
Click to collapse
Great
I've just pushed your changes to my repositories, so they will be included in tomorrows nightly.
Merry Christmas,
Michael

Merry Christmas to everyone !
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Regards

lucize said:
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Click to expand...
Click to collapse
Ok, short gerrit crash-course
Configure your local git to commit with the name and email-address you want to be visible in public repositories
Create an account on http://review.cyanogenmod.org/
Upload an ssh public key there
Clone the repository you want to change with something like:
Code:
git clone ssh://[email protected]:29418/CyanogenMod/android_device_motorola_omap4-common
(This is not necessary if you are working on a direct CM clone and have no other changes in your repository)
Make your changes, commit them
Push your changes to gerrit:
Code:
git push ssh://[email protected]:29418/CyanogenMod/android_device_motorola_omap4-common HEAD:refs/for/cm-11.0
This will tell you an URL where your change is visible.
Go to that URL and add reviewers to your change. For example: Hashcode, David Hacker and probably me (Michael Gernoth)
If your change is acceptable, it will get merged into the CM repository
That's all, no great magic
For more info, have a look at: http://review.cyanogenmod.org/Documentation/user-upload.html
Best regards & thanks for your work,
Michael

lucize said:
Merry Christmas to everyone !
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Regards
Click to expand...
Click to collapse
Is that firmware part of CM11 or something that I'd have to install manually onto my Droid 4? If so, how does one upgrade the Bluetooth firmware?

bofis said:
Is that firmware part of CM11 or something that I'd have to install manually onto my Droid 4? If so, how does one upgrade the Bluetooth firmware?
Click to expand...
Click to collapse
is part of cm11, you can find it in /etc/firmware/
you can find it here
https://github.com/TI-ECS/bt-firmware/commits/master this is the history page where you can find various versions, but the last version from December won't load and the rest will not work with the headset (no sound)
htc one x has the same bluetooth chip and has a newer version of firmware, but the sound on headset will not work either, everything else seems to work
you can see the version at the beginning of the file, motorola has TI_P6_15.56
to update, turn bluetooth off, simply overwrite the file and the turn it on again.

I noticed that this eventually made it to CM11 for all of Moto OMAP cousins, except for the Bionic (Targa). Any reason that the Targa was left out? A lack of hardware support, or was it just never tested?

guyincog said:
I noticed that this eventually made it to CM11 for all of Moto OMAP cousins, except for the Bionic (Targa). Any reason that the Targa was left out? A lack of hardware support, or was it just never tested?
Click to expand...
Click to collapse
I don't know if it has the proper chip but the firmware is correct so it should be possible. I don't have one to test.
Regards

lucize said:
I don't know if it has the proper chip but the firmware is correct so it should be possible. I don't have one to test.
Regards
Click to expand...
Click to collapse
Thanks for the reply. I've got one, maybe I'll see if I can talk one of the builders for the Bionic will make a test build with the necessary common.mk change.
I apprciate the work on this, and the kernel update you've got in progress. Any extra features we can add to these old devices is a huge bonus.

This might be the wrong place to ask this, but does CM11 or CM11 on our phone support the APTX codec via Bluetooth?

bofis said:
This might be the wrong place to ask this, but does CM11 or CM11 on our phone support the APTX codec via Bluetooth?
Click to expand...
Click to collapse
it has the hardware support
http://www.aptx.com/product/motorola-razr-maxx-smartphone
but don't know about the rest of the things

Custom Bluetooth module for Nexus 5 (4.4.3) that works with BMW's ULF car kit

Apologies for the links: as I am a new user, I am not allowed to directly link to outside sources. Please replace _ with :// or . (Forum suggestion: use optional pre-publication review for posts from new users that depend strongly on external links.)
INTRODUCTION: My BMW 318 (E46, 2004) had a factory default BMW ULF bluetooth module (early generation) that worked fine with my BB Q10 and all phones up to Android 4.1. From 4.2 onwards, I and many others have been having problems with keeping the Bluetooth connection alive for more than a few seconds. This has been widely reported but never addressed in stock Android. As even the latest OTA upgrade to 4.4.3 didn't solve it, I decided to compile the required Bluetooth kernel module myself.
BACKGROUND: The change from the Bluez to Bluedroid system in Android 4.2 caused the compatibility issues. User 'wulu' at the forums of CyanogenMod reported on how he patched his CM10.2 (and later) to include a patch that solves the issue. I repeated his procedure for stock 4.4.3 for the Nexus 5.
Markus Schmidt's problem description & patch: https_github_com/Root-Box/external_bluetooth_bluedroid/commit/97d2f6346bad56299f60cfcd8c45ad893a0da78c
Wulu's specifics for Nexus 5 & BMW's ULF for CM: http_forum_cyanogenmod_com/topic/77834-bluetooth-connection-drops-car-kit-bmw/
METHODS:
The following procedure is specifically to compiled the Bluetooth kernel module for the Nexus 5 hardware and the 4.4.3_r1.1 (OTA) release. It should therefore only work for this specific combination. If you want to compile the module yourself, please read the linked pages with Google's excellent instructions: http_source_android_com/source/initializing.html
Here are a couple of notes I made that deal with some specifics for my Mac and the Nexus 5:
On Mountain Lion (Mac), I had to use Xcode 5.0.2 to get past a compile error. See instructions here on how to download and use the older 5.0.2 version of Xcode: https_groups_google_com/forum/#!topic/android-building/FPCSo1xKJ4U
Do not download the "master" source using the repo command, but download "android-4.4.3_r1.1". The master source has post-OTA changes that make a compiled module incompatible with the OTA release for the Nexus 5. "android-4.4.3_r1.1" was listed on those pages as specifically the version that was used for the OTA 4.4.3 upgrade for the Nexus 5.
Setup the environment as instructed and add the three proprietary driver sets listed for the Nexus 5 and 4.4.3 (see "Building for devices" on the Google pages).
There is no need to use the full patch. You can make the two small modifications to the bta_ag_sdp.c file using any text editor. Find the file first (find . -name "bta_ag_sdp.c") and commend out the two lines with the minus signs given in wulu's the first post (or Markus Schmidt's patch) by putting a # in front of both lines: #if (p_scb->peer_features == 0), #p_scb->peer_features = p_attr->attr_value.v.u16;.
Select the "aosp_hammerhead-userdebug" (=Nexus 5) option with the lunch command, and compile using the make command. I was able to follow the instructions pretty much to the letter without any problems.
After the compilation I had two version of the file, in four locations. They are easily found using the find command (find . -name "bluetooth.default.so" -exec ls -la {} \. The bigger one (in the symbols subdirectory) is for debugging. The smaller one is the one I used (and which is linked in this message). It was located at "./out/target/product/hammerhead/system/lib/hw/bluetooth.default.so" in my source tree.
After this, it was pretty straightforward. I rooted my Nexus 5, re-installed FX (with paid-for Root add-on, but the free ES File Explorer should also work), uploaded the file via Dropbox and its Save to SD, transferred it to the R/W mounted system directory to replace /system/lib/hw/bluetooth.default.so with it, and restarted my phone. I also modified the config file (/system/etc/bluetooth/auto_pair_devlist.conf) that blacklists BMW components by commenting out most lines, but I am not sure if this is helpful or not.
RESULTS: It seems a little bit less stable than the Bluetooth connection I had with my Blackberry, but it definitely works. I was able to transfer my contacts and to make and receive calls. For anybody with stock KitKat 4.4.3 on the Nexus 5, here is the bluetooth.default.so kernel module: http_s000_tinyupload_com/index.php?file_id=07750725920558658087
DISCUSSION: The compilation procedure can undoubtedly be optimized. I compiled the entire source tree over several hours, just to be sure I didn't miss out on things. Feel free to give tips, but I'm happy that it worked at all.
CONCLUSION: Thanks to wulu's advice in the CM forum thread I was able to compile a patched Bluetooth module for stock Android with KitKat 4.4.3 that works with my BMW 318 (E46, 2004) ULF car kit.

That´s great! :good:
Is it possible for you to provide the same for Nexus 5 - 4.4.4 OTA ?

mnasty said:
That´s great! :good:
Is it possible for you to provide the same for Nexus 5 - 4.4.4 OTA ?
Click to expand...
Click to collapse
Yes, great job!
Nobody have already done this for 4.4.4 ? I'll do this if I have time.

ZeroKcm said:
Yes, great job!
Nobody have already done this for 4.4.4 ? I'll do this if I have time.
Click to expand...
Click to collapse
4.4.4 from 4.4.3 is only security fixes, everything else is the same.

Does 5.0 Lollipop resolve the BMW ULF connection issue?
guys, do you think 5.0 Lollipop would resolve the current BMW ULF connection problem? Have anyone tried the 5.0 yet ?
I'm still in 4.4.3 working great on N5 paring ULF 8th Gen kit, thanks for S1010, wulu and Alpejohn guiding me the entire process.

REV HRD said:
guys, do you think 5.0 Lollipop would resolve the current BMW ULF connection problem? Have anyone tried the 5.0 yet ?
I'm still in 4.4.3 working great on N5 paring ULF 8th Gen kit, thanks for S1010, wulu and Alpejohn guiding me the entire process.
Click to expand...
Click to collapse
I have the same disconnect issue with my Seat, haven't tried the fix cause I was running 4.4.4 and there was no ready module for it, but lollipop didn't fixed it. I tried compilation without success. I followed all the instructions and compiled it successfully, but after replacing it, bluetooth fails to start. In the logcat logs I can see that it complains there is no bluetooth (something like that, don't have the exact logs to check it now), seems the compiled so file is not compatible.
If anyone can give a hand on this

Not sure if Seat using the same implementation as BMW ULF kit provides, my family also has a 06 Audi A4 with stock BT, I don't experience any connection issue from the stock 4.4.3 on N5. I would think Audi / Seat might use the same BT module as they share most of the VW parts.

I experience the same disconnects. I was experiencing it and with the old phone Galaxy Nexus, till one day I updated to cyanogenmod and the problem was gone. Then changed the phone with Nexus5 and again I have the same issues, tried everything with no luck. Changing the kernel, doing some stuff with paid bluetooth apps to manage the phonebook that the car is accessing. So I suspect the problem is the same
(Seems I'm still not able to post links, I just prepared one with the Blutooth device model number and year on it, if it mean anything to someone it is from 03.2007).

Don't work in lollipop, in your free time please compile a new file.
Thks.
S1010 said:
Apologies for the links: as I am a new user, I am not allowed to directly link to outside sources. Please replace _ with :// or . (Forum suggestion: use optional pre-publication review for posts from new users that depend strongly on external links.)
INTRODUCTION: My BMW 318 (E46, 2004) had a factory default BMW ULF bluetooth module (early generation) that worked fine with my BB Q10 and all phones up to Android 4.1. From 4.2 onwards, I and many others have been having problems with keeping the Bluetooth connection alive for more than a few seconds. This has been widely reported but never addressed in stock Android. As even the latest OTA upgrade to 4.4.3 didn't solve it, I decided to compile the required Bluetooth kernel module myself.
BACKGROUND: The change from the Bluez to Bluedroid system in Android 4.2 caused the compatibility issues. User 'wulu' at the forums of CyanogenMod reported on how he patched his CM10.2 (and later) to include a patch that solves the issue. I repeated his procedure for stock 4.4.3 for the Nexus 5.
Markus Schmidt's problem description & patch: https_github_com/Root-Box/external_bluetooth_bluedroid/commit/97d2f6346bad56299f60cfcd8c45ad893a0da78c
Wulu's specifics for Nexus 5 & BMW's ULF for CM: http_forum_cyanogenmod_com/topic/77834-bluetooth-connection-drops-car-kit-bmw/
METHODS:
The following procedure is specifically to compiled the Bluetooth kernel module for the Nexus 5 hardware and the 4.4.3_r1.1 (OTA) release. It should therefore only work for this specific combination. If you want to compile the module yourself, please read the linked pages with Google's excellent instructions: http_source_android_com/source/initializing.html
Here are a couple of notes I made that deal with some specifics for my Mac and the Nexus 5:
On Mountain Lion (Mac), I had to use Xcode 5.0.2 to get past a compile error. See instructions here on how to download and use the older 5.0.2 version of Xcode: https_groups_google_com/forum/#!topic/android-building/FPCSo1xKJ4U
Do not download the "master" source using the repo command, but download "android-4.4.3_r1.1". The master source has post-OTA changes that make a compiled module incompatible with the OTA release for the Nexus 5. "android-4.4.3_r1.1" was listed on those pages as specifically the version that was used for the OTA 4.4.3 upgrade for the Nexus 5.
Setup the environment as instructed and add the three proprietary driver sets listed for the Nexus 5 and 4.4.3 (see "Building for devices" on the Google pages).
There is no need to use the full patch. You can make the two small modifications to the bta_ag_sdp.c file using any text editor. Find the file first (find . -name "bta_ag_sdp.c") and commend out the two lines with the minus signs given in wulu's the first post (or Markus Schmidt's patch) by putting a # in front of both lines: #if (p_scb->peer_features == 0), #p_scb->peer_features = p_attr->attr_value.v.u16;.
Select the "aosp_hammerhead-userdebug" (=Nexus 5) option with the lunch command, and compile using the make command. I was able to follow the instructions pretty much to the letter without any problems.
After the compilation I had two version of the file, in four locations. They are easily found using the find command (find . -name "bluetooth.default.so" -exec ls -la {} \. The bigger one (in the symbols subdirectory) is for debugging. The smaller one is the one I used (and which is linked in this message). It was located at "./out/target/product/hammerhead/system/lib/hw/bluetooth.default.so" in my source tree.
After this, it was pretty straightforward. I rooted my Nexus 5, re-installed FX (with paid-for Root add-on, but the free ES File Explorer should also work), uploaded the file via Dropbox and its Save to SD, transferred it to the R/W mounted system directory to replace /system/lib/hw/bluetooth.default.so with it, and restarted my phone. I also modified the config file (/system/etc/bluetooth/auto_pair_devlist.conf) that blacklists BMW components by commenting out most lines, but I am not sure if this is helpful or not.
RESULTS: It seems a little bit less stable than the Bluetooth connection I had with my Blackberry, but it definitely works. I was able to transfer my contacts and to make and receive calls. For anybody with stock KitKat 4.4.3 on the Nexus 5, here is the bluetooth.default.so kernel module: http_s000_tinyupload_com/index.php?file_id=07750725920558658087
DISCUSSION: The compilation procedure can undoubtedly be optimized. I compiled the entire source tree over several hours, just to be sure I didn't miss out on things. Feel free to give tips, but I'm happy that it worked at all.
CONCLUSION: Thanks to wulu's advice in the CM forum thread I was able to compile a patched Bluetooth module for stock Android with KitKat 4.4.3 that works with my BMW 318 (E46, 2004) ULF car kit.
Click to expand...
Click to collapse

FYI, had similar issue with 2009 E61 5 series. Solution was third party app (Bluetooth Phone book) and a full software update for the car from the dealer. The app cost a few quid, the dealer software update much more!
That said, it works perfectly with stock Lollipop and I consider it money well spent.
---------- Post added at 09:15 PM ---------- Previous post was at 09:13 PM ----------
FYI, it was this app: https://play.google.com/store/apps/details?id=com.android_rsap.irmc