Develop Bugs

Bluetooth Issue

Hey there,
I'm having a problem with the bluetooth on my desire...
I'm running stock android 2.2, unrooted...
The phone seems to work totally fine, but the bluetooth refuses to connect to my car kit... it has worked fine from day one and now all of a sudden it connects for a few seconds and then disconnects, and then when you go into the bluetooth settings to re-connect it, the menu just hangs... if you leave it for a few seconds the phone then reboots...

TrueTenacity said:
Hey there,
I'm having a problem with the bluetooth on my desire...
I'm running stock android 2.2, unrooted...
The phone seems to work totally fine, but the bluetooth refuses to connect to my car kit... it has worked fine from day one and now all of a sudden it connects for a few seconds and then disconnects, and then when you go into the bluetooth settings to re-connect it, the menu just hangs... if you leave it for a few seconds the phone then reboots...
Click to expand...
Click to collapse
Hi,
Have a look here: http://forum.xda-developers.com/showpost.php?p=9511037&postcount=2

jmelhus said:
Hi,
Have a look here: http://forum.xda-developers.com/showpost.php?p=9511037&postcount=2
Click to expand...
Click to collapse
THANK YOU so much! That looks like it'll do the trick, now my only problem is how the eff do I install it? I've tried to copy it to the root of the mem card but it looks like the recovery thing on my phone is toast... even though it's got stock firmware on it...
Will it be easier to root the phone?

Ok, I am now Rooted and running LeeDrOiD 2.2f which apparently includes the Bluetooth fix as mentioned above...
But the problem persists...
It's definitely not the radio, because it pairs and works perfectly with another phone.
Any other ideas?

TrueTenacity said:
Ok, I am now Rooted and running LeeDrOiD 2.2f which apparently includes the Bluetooth fix as mentioned above...
But the problem persists...
It's definitely not the radio, because it pairs and works perfectly with another phone.
Any other ideas?
Click to expand...
Click to collapse
Which bluetooth fix is implemented in leedroid? I would rather recommend you a cyanogenmod 6.1 ROM, or a ROM that's built on CM. For me this fix implemented there has worked. FYI, CM are AOSP and without sense.
Sent from my HTC Desire using XDA App

The fix is "[MOD][21-July] Fix Bluetooth CarKit disconnection" and apparently fixes the issue...
Hmm, I kinda like the sense interface so would be sad to see it go...

My Desire also has a bluetooth problem in connecting with my car. Not the disconnections, but phonebook/callist access fails. Installing an AOSP Rom (or MIUI) fixes the problem, but I do like sense too.
I've concluded the sense-bluetooth stack is the culprit, however I don't have the knowledge to change the stack. Thus, I'll wait until somebody has fixed it or HTC updates the stack or until I'll buy a new phone

I am happy to say that the problem is gone when using Cyanogen Mod 6.1.0
It doesn't transfer the phone book, but the phone function works... so I'm happy...
Just have to now get used to android without sense... hmmm...

TrueTenacity said:
I am happy to say that the problem is gone when using Cyanogen Mod 6.1.0
It doesn't transfer the phone book, but the phone function works... so I'm happy...
Just have to now get used to android without sense... hmmm...
Click to expand...
Click to collapse
Hi, as i am having the same issue and dont really want to use a Cyanogen rom , before i do what vehicle did you get it to work with.
cheers

It was with a Pioneer DEH-P710BT head unit with built-in bluetooth...
The strange thing is that it worked absolutely perfectly for MONTHS and now all of a sudden is giving problems...
It is however, definitely the phone giving the problem because the head unit pairs perfectly with any other phone, and when using the cyanogen mod rom, the desire works perfectly with it.

3 bugs I have with ALL 4.2.1 roms.

Just wondering if these are problems everyone is facing, or just me, and if there is maybe a fix for some of them. They have been broke for MONTHS, and I can't figure out why I don't see more people talking about them, or why they haven't fixed them yet.
1. Bluetooth A2DP streaming is broke - Okay, this one I know is common knowledge, so we can skip this one. Supposed to be fixed officially by Google in 4.2.2. I can live with this.
2. The native WiFi hot-spot only works without encryption. All WiFi hot-spot apps from the Play Store are broken as well. Either you can't connect to the phone from your laptop/device, or the SSID isn't broadcasted at all, and you can't see it from anything.
3. When using a Google app that requires the microphone, whatever app you are using will crash. I have noticed this with Google Now, and most annoyingly the keyboard. The worst thing about this is that if you accidentally hit the mic key on the keyboard, the keyboard crashes, and it doesn't work again until you wipe the phone and re-install the Rom. Rebooting doesn't even solve it.
All three of these problems persist for me through out all the roms I have tried. This means CyanogenMod10.1, Kangdroid, PAC, Paranoid, Slimbean, etc. I know most of those are based on CM10.1, so that explains why they are all broke, but why have they been broke for so long, or is it just me?

Never seen #3 happen (I use it quit a bit). Wifi hotspot issue is known.

Aerowinder said:
Never seen #3 happen (I use it quit a bit). Wifi hotspot issue is known.
Click to expand...
Click to collapse
Yeah, that bug alone didn't happen when I first started using 10.1. Not sure when it started to be honest.

Update google search for the keyboard I think

mt3g said:
Update google search for the keyboard I think
Click to expand...
Click to collapse
That's very possible. It's one of the first things I try when I get the latest nightlies, so I probably try it each time before I have updated anything.
Is there any reason to think that the hot-spot issue will be resolved in 4.2.2?

Ya, and I don't know, it might be coding that is needed within AOSP, does wifi tether encrypted not work on the Nexus 4 or GNEX?

Just an update for anyone who is searching and finds this thread by some chance...
It looks like 4.2.2 did not fix the HotSpot issue, but it did fix the Bluetooth streaming. I tried the SmoothRom 4.2.2 release, to test these things.
PAC-man rom 4.2.1 is my current favorite rom, and they did somehow fix both of those issues recently. Probably had something to do with 4.2.2's release this week. So if someone is looking for a 4.2 rom with working Bluetooth, and WiFi tether encryption, you might want to give that rom a try.
It is right here:
http://forum.xda-developers.com/showthread.php?t=2015525

4.2.2 has working everything. On Liquid Illusion you need to flash a custom kernel that is updated to have encrypted hotspot.
Sent from my SGH-T999 using xda premium

ArkAngel06 said:
Just wondering if these are problems everyone is facing, or just me, and if there is maybe a fix for some of them. They have been broke for MONTHS, and I can't figure out why I don't see more people talking about them, or why they haven't fixed them yet.
1. Bluetooth A2DP streaming is broke - Okay, this one I know is common knowledge, so we can skip this one. Supposed to be fixed officially by Google in 4.2.2. I can live with this.
2. The native WiFi hot-spot only works without encryption. All WiFi hot-spot apps from the Play Store are broken as well. Either you can't connect to the phone from your laptop/device, or the SSID isn't broadcasted at all, and you can't see it from anything.
3. When using a Google app that requires the microphone, whatever app you are using will crash. I have noticed this with Google Now, and most annoyingly the keyboard. The worst thing about this is that if you accidentally hit the mic key on the keyboard, the keyboard crashes, and it doesn't work again until you wipe the phone and re-install the Rom. Rebooting doesn't even solve it.
All three of these problems persist for me through out all the roms I have tried. This means CyanogenMod10.1, Kangdroid, PAC, Paranoid, Slimbean, etc. I know most of those are based on CM10.1, so that explains why they are all broke, but why have they been broke for so long, or is it just me?
Click to expand...
Click to collapse
I've had #3 happen, and it can be fixed by clearing the data for the keyboard and the voice search (I don't remember if the voice search part was an app, but I remember looking for it). Just go to apps and wipe the data.

milesmarrero said:
I've had #3 happen, and it can be fixed by clearing the data for the keyboard and the voice search (I don't remember if the voice search part was an app, but I remember looking for it). Just go to apps and wipe the data.
Click to expand...
Click to collapse
Thanks for the info, but updating to the newest Google App from the PlayStore fixed it for me.
Your solution would probably fix the need to reflash.

JB Rom with ICS Bluetooth Stack?

Are there any JB/4.2.2 Roms with the ICS Bluetooth Stack? Is this even possible? I've recently flashed CM 10.1 RC2 and love the project butter feel - it's amazing, but my bluetooth is so unreliable as to render it useless - says it's connected, try to make a call, and it won't connect to the car... and then sometimes will then come up 4 minutes into the conversation, etc.
I didn't have these troubles on earlier Android versions, and it's driving me to get a new phone sooner than I'd like.

Pyperkub said:
Are there any JB/4.2.2 Roms with the ICS Bluetooth Stack? Is this even possible? I've recently flashed CM 10.1 RC2 and love the project butter feel - it's amazing, but my bluetooth is so unreliable as to render it useless - says it's connected, try to make a call, and it won't connect to the car... and then sometimes will then come up 4 minutes into the conversation, etc.
I didn't have these troubles on earlier Android versions, and it's driving me to get a new phone sooner than I'd like.
Click to expand...
Click to collapse
Flash the bluetooth fix.

nikon120 said:
Flash the bluetooth fix.
Click to expand...
Click to collapse
Where can I find this? (Stock, kernel, FC09 modem) My google-fu and thread search is failing me...
... and saved:
DynamicN said:
http://d-h.st/PNh
Thank Unjustified Developer for this zip.
Click to expand...
Click to collapse

Yup, that didn't work for me, 47 seconds from dial to car audio picking up connection, but then no audio and the phone Bluetooth had grayed itself out. Tried a fix permissions tenor but nothing. Maybe I have the wrong file (fingers crossed)?
tapatalkin'

[Q] wifi not working

Hello I need help... if anyone knows of a patch or fix this problem please let me know please

What rom are you running? As far as I know, wifi is working in all roms.

audit13 said:
What rom are you running? As far as I know, wifi is working in all roms.
Click to expand...
Click to collapse
Happens to me it is working but suddenly it is not working anymore and I've tried every rom: avatar: ho! no!: Cm10.1: liquid nitro ... And the different baseband... begin working in early but then does not work.... I think this is due to the problem that I have with BSOD...

elfiloso said:
Happens to me it is working but suddenly it is not working anymore and I've tried every rom: avatar: ho! no!: Cm10.1: liquid nitro ... And the different baseband... begin working in early but then does not work.... I think this is due to the problem that I have with BSOD...
Click to expand...
Click to collapse
Sounds like it may be a hardware issue as every rom I have tried works with wifi, although wifi works best if I stick with ICS roms.

Look now I'm on Gingerbread and Lob works perfectly but sometimes goes crazy and reboots start ...
Sent from my LG-P930 using xda app-developers app

Is it possible your phone is defective because it's rebooting? I have used quite a few roms and wifi always works and no random reboots.

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.