CM --> MIUI --> CM Bluetooth Dies! - Nexus One General

Hi folks,
I tried out the MIUI ROM and liked it, but for various reasons, I wanted to go back to CMod again. So, I restored my NAND backup of my CM6 install. When I did this, I noticed that Bluetooth was no longer working correctly, i.e. it would pair successfully with my radio, but it failed to connect to it.
When I restored my MIUI backup, bluetooth worked again.
I cleared every cache known to man and once more returned to my CM backup, but once again my Bluetooth failed to work.
In the end, the only thing that seemed to fix the problem was wipe all the settings (again) and flash the latest CM nightlies (very nice btw!). After this, all was well.
I am attaching a logcat file if anybody is interested in the Bluetooth output. My totally uniformed suspicion is that it had something to do with the way MIUI uses the Bluetooth stack to get the radio working, but I'm sure somebody out there knows better than I do.

Related

Problem with Bluetooth paring on CM6 and CM7

Hi,
I've been trying to use CM6 and CM7 but with both versions I run into Bluetooth pairing issues. The main problem is seen when trying to pair from my phone to my car. I get asked to enter a pin (that has been displayed by the car), but only get a few seconds to do so before I get an error message displayed. I've tried various kernels (same problem), and I'm using the latest radio rom. Things seem to be fine with stock 2.1 and with wildpuzzle. When flashing the roms I'be made sure I clear the cache, the dalvik cache and reset to default. Is there anything else I can try?
Thanks
Andy
Hi Andy,
Did you ever get a fix for this? I am having a similar issue, however my device does not give me a prompt at all for the bluetooth passkey.
Thanks,
Jessica
Use bluetooth file transfer from market. It works
Didn't work for me, still looking for a way round this.

[Fixed] CM 7 RC2+ No Bluetooth

Hi there.
I have been using CM 7 since the first round of Nightlys and it has always working fine. Except for a few FC's its been very stable.
All the way up to RC2 everything worked very well, untill the Nightly builds after RC2, then my Bluetooth stopped working.
I have tried every release upto RC4 and still I cant get my Bluetooth headset to connect.
I have tried flashing both the kernel mod and radio to RC4 from this thread; http://forum.xda-developers.com/showthread.php?t=1015532 but still no Bluetooth.
Everything else works great, but I need the bluetooth, so I am back on RC2 again.
Has anyone had any issues with this?
Thanks in advance.
No, I am on RC4 and BT works fine. Just sent and received a bunch of files and contacts between the Wildfire and an old Nokia.
Try a fresh install with everything wiped.
I have just tried a Fresh Install.
I installed RC4 and Wiped all Data and Cache using ROM Manager.
But still i cannot sync my Bluetooth headset.
File transfer might work (havent tried it), but not the headset.
I think it must have been my Bluetooth headset.
It works fine on other phones but not on my Wildfire with RC2+ installed.
I just bought a new headset and it sync'd straight away with #35, so for now, this problem is solved.

Real Problem after Updating to the latest nightly

Hello together,
after ive updated yesterday to the nightly 204 ive got a serious problem.
Every time i use the mobile data connection....the phone is rebooting.
The really wired thing is that after ive restored my backup which was totally stable, the problem is still there. Even when i try my really old recovery of the stock sense...the phone is rebooting something like 20 seconds after using
a mobile data connection (which is working in that amount of time)
I have really no idead what to do now.....any help is welcome.
Thx in advance!
Try reflashing the radio. (All 3 versions, if one of them doesn't solve the issue) I believe pyroblazer was having a similar issue on the RemPuzzleROM and a radio reflash fixed it.
at first i want to thank 3xeno for his quick help (as he always does). Really thanks..the community lives because people like you.
Ive solvend the problem....after 2 times wiping all... the only backup which is working flawless is my old stock sense, all other cm7 backups reboot after using mobile data connection. When i wipe all and install a clean cm7 nightly 204 ...its working too, but at moment ive no time to install everything, so i will keep the stock sense for some days.
The wired thing is...that this bug appears after i updated from the 202nightly to 204 and especially wired is that all my cm7 backups are now affected by this problem that never happend in the past.

[Q] Wifi Problem

Hi
I have some strange problems with wifi - I can see the networks, but when I connect it just appears as "Remembered" and nothing happens.
I thought that was an rom issue (MIUI GB 2.3.7 V48), but after changing rom to NexusHD2-ICS-4.0.4-CM9-HWA_V2.7 it still doesn't connect.
Tried WiFix and it didn't work. Main issue why i changed from MIUI was randomly muted mic in calls, but that's offtopic.
Any suggestions?
EDIT: Before trying another MIUI to solve mic issue wifi worked like charm, before flashing zip did full wipe, cache wipe and dalvik wipe.
Cheers,
Flaffie.
i dont know ,……
bump

[Q] Wifi won´t activate on stock 4.2.2/cm 10.1

Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Joharnis said:
Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Click to expand...
Click to collapse
Im having a similar problem, i think we have to flash a different radio ?
Still nothing
Flash a different radio? What excactly does that mean? I must admit I have not heard of that :laugh:
By the way, I just unrooted my device and relocked the bootloader, but that didn´t fix the problem either.
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
sigma392 said:
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
Click to expand...
Click to collapse
I just tried the franco R163 with prima drivers, that did not fix it. But, speaking of the bluetooth, i´ve just noticed that the same problems occurrs with that. I trie to turn it on an it stays at "turning on bluetooth" without actually turning on. Maybe that helps to know what the problem is.
What other kernel with prima drivers would you recommend?
Edit:
I´ve read through a few threads on that bluetooth-issue, which apparently is more common than my wifi issue. I was wondering if my wifi-issue could have something to do with the bluetooth, because other users who have said bluetooth issue found their bluetooth temporarily on after reboot; then after a while the bluethooth issue appeared again.
In my case the bluetooth doesn´t appear to be on, but i was thinking that maybe it is, but the software fails to display that and that that is interfering with my wifi.
Could that be a possibility?
Out of the box my nexus 4 refused to connect to my TPLINK wr941ND router, wifi was set months ago, nexus 7 works as charm same with evo 3d and others. I thought wtf and turned on wifi on broadband modem, it showed up on nexus 4.... And suddenly network from router poped up as well. I switched off wifi on modem and nexus lost wifi from router. At this moment I went for a walk... When I come back done factory reset, reboot the router, no effect. Changed settings from WPA2/QSS to WPA without QSS - no change, then I changed channel from #13 (best in my location, all my neighbours using #1 and #6) to #1 and instantly nexus found network.... So it seems that sumthing is apparently with wifi, when I changed channel back to #13 it drops the connection and says that networtk is out of range. So finally I checked all the channels from 1st to 13th and it works from #1 to #10, 11 till 13 dunt work. Maybe this info will help sumone with simillar problems.

Categories

Resources