Develop Bugs

[Q] [solved] Bluetooth ICS 4.0.4 (sandvold) VW RCD 510

Hello,
may me be helped here? I have a HTC Desire with ICS 4.0.4 of Sandvold.
In the car always I have to confirm the bluetoothpairing twice until it is coupled. I have a handfree-kit for Volkswagen with a RCD 510, in the simple version (supports handsfree profile). In my opinion, it is no problem with rSAP!
With Android vers. 2.3 the pairing was automatically...
Thanks in advance
BR
Sauerland
HTC Desire with [BETA 0.11][03.06] ICS for Desire[ALL HBOOTS][4.0.4]
VW Golf VI RCD 510

Hello,
next problem with Bluetooth.
I've tested to pair my ics desire with a galaxy s2, it doesn't work and pairing with a galaxy
s3 doesn't work also.
Does someone know a solution or a hint/tipp?
BR
Sauerland

I found nothing wrong with Bluetooth.
I can connect easily with my Car using Bluetooth and tried sending files to 4-5 different phones without any error.
its worth mentioning which Version of ROM you are using.
usually Full Wipe before flashing ROM Removes 99% Troubles

Hmm,
I've done a full wipe before.
But I'll do so again next weekend with version 0.13, hopefully that it works better.

So, I've done a full wipe and reinstall Version 0.13,
pairing is ok, but the telefone in my car rings but I can't speak/hear anything.
The phone goes always in "private mode". Change it to "hands-free", to "private mode" and return will not solve the problem. Eyerytime a call comes in the radio "rings", but the phone stays in "private mode".
The same problem after a full wipe and version 0.13.1 install

Ics 4.0.4 v.13.1 Bluetooth
Hello!
I've done a full wipe and install Version 0.13.1. After activating/disactivating bluetooth the systems gives me an error (com.android.phone). After pressing the ok button I have to reboot the phone, because there is an sim card error as well. After rebooting the phone runs normal, but everytime I use bluetooth I have the same problem again.
Before I had installed the ICS 4.0.4 v.12 and never occured an error like this. Anybody there with the same problem or the solution?
Thanks for help and greetings
Dami7

Hello,
i have also a problem with pairing.
My BT from the car does not find my hone at all. yes i made it vissible.
BT in the car works, can pair with other phones. BT on the phone works, can connect to my laptop.
But no connection to my car??
with android 2.x it worked??

R0yke said:
Hello,
My BT from the car does not find my hone at all.
....
But no connection to my car??
with android 2.x it worked??
Click to expand...
Click to collapse
Same for me.
My car does'nt find the phone, telefonbook can't sync, handsfree does'nt work, but I can answer the call without handsfree.
with Android 2.3.x no problem

Me too. Any help?

Had exactly same issue with 0.13.1: no audio through bluetooth headset or car handsfree + com.android.phone crashing when disabling bluetooth.
Downgrade to 0.12 seems to have fixed both problems for me.

Known issue reported in the development thread for 0.13.1.
Sandvold says he should have a new build (0.14) soon, no news on whether that fixes it or not however.

Yes, the new release will fix something:
Sandvold:
....and start working tomprrow.
Usb tether is fixed pluss adhoc. But its a bit unstable so wont release it and need to build a new one.
Click to expand...
Click to collapse
He says nothing about BT, but I'll hope it will fixed too

Hey, good news, the version 0.14 fixes the problem with audio through the headset/car speaker.
The last problem is phonebook sync with my car audio system, always the error message "phonebook sync incomplete" appears at the audio system display.
I'll hope sandvold fixes this issue too...

[solved] Bluetooth ICS 4.0.4 (sandvold) VW RCD 510
I've solved the phonebook-access with the Phone Book Access Protocol (PBAP)-Addon,
found here: http://forum.android-rsap.com/viewtopic.php?f=33&t=221
Now I can hear the audio through the speaker, and the RCD 510 always sync the phonebook with my HTC Desire ICS.
Tested with VW Golf VI, RCD510, "low-cost" original Handsfree-Kit from VW.
ICS Vers. 0.14 from Sandvold

Upgrading to .014 has also resolved this for me

Hi
Same phone same ics version 4.0.4, car audio is clarion fb-288 and for me I get asked to reenter the code every time. Also worked fine with 2.2.x and 2.3.x.

ludagad said:
Hi
Same phone same ics version 4.0.4, car audio is clarion fb-288 and for me I get asked to reenter the code every time. Also worked fine with 2.2.x and 2.3.x.
Click to expand...
Click to collapse
I had that too, did a factory reset on sandvolds rom, and reflashed the latest. Problem solved. But i moved on now. You should try nikez 4.2.1 rom, its about as far as sandvold was with 4.0.4. Also an evervolv rom. Its amazing how smooth it is, and latest release is quite stable too. I assume sandvold stopped devving, as he is vanished for several months now. So time to move on!
Sent with my HTC Desire with Red Tapatalk because my XDA premium app is beeing a female dog!

pair to clarion fb-28* works again
PuffMaN said:
I had that too, did a factory reset on sandvolds rom, and reflashed the latest. Problem solved. But i moved on now. You should try nikez 4.2.1 rom, its about as far as sandvold was with 4.0.4. Also an evervolv rom. Its amazing how smooth it is, and latest release is quite stable too. I assume sandvold stopped devving, as he is vanished for several months now. So time to move on!
Sent with my HTC Desire with Red Tapatalk because my XDA premium app is beeing a female dog!
Click to expand...
Click to collapse
I managed to fix the problem in the original from by replacing the Bluetooth.API with a download from Androidforums. There is a post there that has 3 versions attached. I used the 4.0.1 sz 407 KB. Works like a charm.
I hadn't checked for other ICS rooms since I got this one. I didn't know there was something else.... THANKS! Time to backup now

ludagad said:
I managed to fix the problem in the original from by replacing the Bluetooth.API with a download from Androidforums. There is a post there that has 3 versions attached. I used the 4.0.1 sz 407 KB. Works like a charm.
I hadn't checked for other ICS rooms since I got this one. I didn't know there was something else.... THANKS! Time to backup now
Click to expand...
Click to collapse
Nikez 4.2.1 is not an ICS rom, but the latest and greatest JB
ROM thread found here:
http://forum.xda-developers.com/showthread.php?t=1766550
Q and A found here:
http://forum.xda-developers.com/showthread.php?t=1944226
Almost all ROMs for desire are found here:
http://forum.xda-developers.com/showthread.php?t=809328
Take a look
Sent with my HTC Desire with Red Tapatalk because my XDA premium app is beeing a female dog!

[Q] Bluetooth doesn't work for me with 4.2.1

It used to work perfectly for me in the car (the only time I use Bluetooth) to use the hands-free stuff with IceColdSandwich 8.8.
I've tried Jellybean 4.2.1 by Randomblame and CodefireX but it won't pair.
In both cases when I power-up the car it tries to connect to the phone, and each time the phone pets out a beep and asks for the pairing code. It then will not pair.
Any suggestions? I'd really like to get the hands-free stuff working again.

Try the latest codefireX SR6 version. Many users have reported perfectly working bluetooth since 2-3 versions ago.
Sent from my Desire HD using xda premium

First:sorry for my bad English
JellyTime 4.2 project, last codfirex sr6, aokp Jbean, unofficial cm10.1, have a fully working bluethoot....

I tried CodefireX SR6 but still no good sorry.
I prefer Randomblame's Jellytime as well, if possible.

*bump*
Anyone please?

Receiveing files by bluetooth on the phone doesn't work for me either.
using CodefireX SR8 now (HTC desire HD)

Just a FWIW if anyone else has the same problem and finds this thread with a search - I have now fixed the problem by going to Jellytime R6.1 but I think the real solution was to flush the cache partition and Dalvik cache.
Bluetooth works just fine now.

[Q] Bluetooth stack or driver issue?

So I've tried every custom ROM for my E973 and I've noticed something odd. The ROMs built using the team LGOG tree seem to have an issue initializing bluetooth. It takes about 6-7 sec for bluetooth to come on, and android beam file transfer doesn't work. On the other hand, with Paulicat's AOKP and dvhexer's CM 10.1, bluetooth initializes within a second or two and android beam works fine. Is this down to drivers or some other difference in the bluetooth implementation? Would it be possible to create a flashable zip to apply to the ROMs with slow bluetooth to make it faster/more stable?

r.asimi said:
So I've tried every custom ROM for my E973 and I've noticed something odd. The ROMs built using the team LGOG tree seem to have an issue initializing bluetooth. It takes about 6-7 sec for bluetooth to come on, and android beam file transfer doesn't work. On the other hand, with Paulicat's AOKP and dvhexer's CM 10.1, bluetooth initializes within a second or two and android beam works fine. Is this down to drivers or some other difference in the bluetooth implementation? Would it be possible to create a flashable zip to apply to the ROMs with slow bluetooth to make it faster/more stable?
Click to expand...
Click to collapse
man, Still haven't had a response.
For what it's worth, I'm in the same boat as you. AOKP and AOSP will work everytime. Everything else won't work as well as stock. I got nothing to report that fixes bluetooth. If you find out why, let me know.
I use bluetooth a lot.

mathsz said:
man, Still haven't had a response.
For what it's worth, I'm in the same boat as you. AOKP and AOSP will work everytime. Everything else won't work as well as stock. I got nothing to report that fixes bluetooth. If you find out why, let me know.
I use bluetooth a lot.
Click to expand...
Click to collapse
Try dvhexer's cm 10.2

Can you tell what bluetooth version on custom roms?

Is there any way to tell what version bluetooth is on a rom? I use a fitbit flex which needs blutooth 4.0. Any roms ive tried that are android 4.2 or 4.3 doesn't work with the flex. I would love to figure this out so I could use the newer software and still be able to sync my fitbit. Thanks

eeyore6802 said:
Is there any way to tell what version bluetooth is on a rom? I use a fitbit flex which needs blutooth 4.0. Any roms ive tried that are android 4.2 or 4.3 doesn't work with the flex. I would love to figure this out so I could use the newer software and still be able to sync my fitbit. Thanks
Click to expand...
Click to collapse
Which 4.3 roms haven't worked for you? Technically speaking they should all work, but I know Vanir didn't. CM10.2, PAC, Slimbean and others worked for me with my devices. I just remember Vanir not working even though it was 4.3.

Anything thats been 4.2 or 4.3. I know the cm I tried, a pacman one too. Fitbits website said with custom roms there have been some issues implying they didnt have the correct drivers. I have a jedi thats working but that goes back to 4.1. On the other roms when I go into the fitbit app to sync, the button to the right up top you would click to sync, never shows up on the 4.2 and 4.3 roms.

To clarify, my bluetooth to talk on the phone works but the software to sync up with the fitbit itself on the app does not work.

Probably use the application manager in settings and see the BT apk version.

You have to edit your build.prop to reflect one of the white-listed product models...
See: http://forum.xda-developers.com/showthread.php?t=2436260&highlight=fitbit+sync

Problem with O-Click & 32GB Oppo N1

Hi, I have a problem with O-Click and Cyanogenmod. I have the 32GB Oppo N1 and while the O-Click works fine with ColorOS I haven't managed to make it work successfully with Cyanogenmod. I have upgraded the O-Click firmware via ColorOS.
Has anyone else encountered this problem?
Sent from my N1 using Tapatalk

aeacus said:
Hi, I have a problem with O-Click and Cyanogenmod. I have the 32GB Oppo N1 and while the O-Click works fine with ColorOS I haven't managed to make it work successfully with Cyanogenmod. I have upgraded the O-Click firmware via ColorOS.
Has anyone else encountered this problem?
Click to expand...
Click to collapse
If I remember correctly, it should be able to work the same way. Ensure Bluetooth is on, go into the O-Click settings, then search. After you do that, just click the O-Click one time so it starts searching for the phone. It should be able to pair.
I did run into a problem once where I had to go to the Bluetooth settings and forget the O-Click because it wouldn't connect. It was paired, but it never actually connected. Once I did that, I just paired them again and it worked. You could give that a shot if it shows as paired in the Bluetooth settings. Just delete it out of there and try again.

I've deleted it from bluetooth settings but it didn't help.
Also after I tried connecting to it via Buttons>O-Click settings I can't connect to it from Bluetooth menu either. Only if I disable and enable Bluetooth again I'm able to pair via Bluetooth menu only. But to get it to work I have to connect to it via button settings.
Does anyone know of a way to hard reset the O-Click device; When I opened it for the first time I remember it was blinking a green light. Is there anyway to put the device to that mode again? I tried to long press the button but nothing happens.
Sent from my N1 using Tapatalk

After searching in oppoforums I've found out that O-Click has problem with CyanogenMod. Original thread here http://www.oppoforums.com/index.php?threads/8100/
Has anyone managed to get it working in CyanogenMod?
Sent from my N1 using Tapatalk

aeacus said:
After searching in oppoforums I've found out that O-Click has problem with CyanogenMod. Original thread here http://www.oppoforums.com/index.php?threads/8100/
Has anyone managed to get it working in CyanogenMod?
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
There is an open Bug-Report about it: https://jira.cyanogenmod.org/browse/CMN-1
No one working on it as of now (at least no one has assigned to the task).

It seems like the O-Click connectivity issue only occurs with regular users. Every review site that talks about the CM edition of the N1 doesn't bring up any connectivity issue. in fact in review videos they show that it's working... What are they doing differently that everyone else seems to be failing at.. :S

Espada04 said:
It seems like the O-Click connectivity issue only occurs with regular users. Every review site that talks about the CM edition of the N1 doesn't bring up any connectivity issue. in fact in review videos they show that it's working... What are they doing differently that everyone else seems to be failing at.. :S
Click to expand...
Click to collapse
A user is A user...
No difference...
((developer options and rooting is different.))
But what they're having is the earlier version of the CM edition before the "update" that "broke" the O-Click functionality...

Silence in the woods...
And still no reaction from CM about this issue. Looks like we got screwed. The N1 is not tight to CM at all. There is not even a Forum for it on their Pages and the N1 is not in the List of Supported (or unsupported) Devices.
Guess, I'll flash the Color-OS, install Apex or Nova and wait for a fully working Omni Release.
Goodbye CM...

schauol1 said:
And still no reaction from CM about this issue. Looks like we got screwed. The N1 is not tight to CM at all. There is not even a Forum for it on their Pages and the N1 is not in the List of Supported (or unsupported) Devices.
Guess, I'll flash the Color-OS, install Apex or Nova and wait for a fully working Omni Release.
Goodbye CM...
Click to expand...
Click to collapse
I tried running ColorOS and sure O-Clicked kinda worked. I found the battery life to be pretty bad and the phone ended up using more RAM than compared to CM10.2 :S
When O-Click was connected to the phone in ColorOS, it worked like it should. It's when it gets disconnected when you try to reconnect it. I was forced to use both the device and the phone to reconnect which kind of defeats the purpose of the "locate" phone feature. I'd get the usual red blink when it's disconnected. lol
Maybe OmniROM will be better when it's complete. Or hopefully the CyanogenMod team still cares about their first official CM backed phone. lol.

Espada04 said:
Maybe OmniROM will be better when it's complete. Or hopefully the CyanogenMod team still cares about their first official CM backed phone. lol.
Click to expand...
Click to collapse
started working on it again just yesterday
Hope to have som app to test by end of the week

New announcement from CM team is pretty discouraging.
http://www.cyanogenmod.org/blog/a-case-study
So what this basically means is that N1, the first Cyanogenmod phone ever is actually not for "regular" CM users.
A user selecting any phone supported by CM team (i.e. Samsung Galaxy S3) will always be updated with the latest versions while N1 users will be on the waiting list. Too bad as I bought the N1 to support the team but if I want the updates rolling in I have to go with Omnirom.
Well i guess this is what they call "The end of an era!"

All People Update CM. there is the cm-11-20140724-NIGHTLY
First update to the latest nightly in CM page, after that you can update via OTA in your phone, there is Daily updates!!
O-Click, Works, meaby a second lag (while focusing?)
O-Touch Works, not as the touchpad of your lap but works, And for some reason changing the VM to ART works better for me.
3G works
Battery last very good, and its suposed to las more in stand-by if you use ART instead of Dalvik
ART works well by the way.