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
Related
Does anyone know if the Bluetooth SMS MAP protocol is supposed to work in 4.2.2 AOKP (I'm running milestone 1)? My Honda Civic doesn't think the phone supports it, so I'm guessing it's not working, but wanted to make sure there wasn't something I was missing. Also, I'd love to know if anyone is working on it or knows what the status is. I moved from an old hacked-up CM10.1 over to AOKP hoping maybe this had been fixed/was working, but alas, it looks like I'm still out of luck.
If I had more time, I'd offer to fix it up myself (and may still) if someone could point me in the right direction to get started. From what I saw in old posts back during the CM9 days this was working, so it seems that it'd be possible to revive without too much deep knowledge of the protocol itself (some already did the hard work)...
-Daniel
Okay, does anyone know if any of the 4.2.x ROMs support bluetooth sms map?
dath1974 said:
Okay, does anyone know if any of the 4.2.x ROMs support bluetooth sms map?
Click to expand...
Click to collapse
well there are known bluetooth issues with 4.2.2 roms
I have a bluetooth headset which seems to work fine...
however I have a bluetooth mouse which recognizes but doesn't work in 4.2.2 roms
All 4.1.2 roms built off official stock seem to have bluetooth working fine...
hope this helped m8
In JB, a new Bluetooth stack was implemented. The MAP profile code, which was added to AOKP in ICS, is no longer valid. From what I have read, the new BT stack is not open source, so devs will not be able to reimplement MAP, at least for now.
Sent from my SGH-T959 using Tapatalk 2
Hey guys,
I got tired of the Bluetooth headset issue stopping me from using cm10.1 as my daily driver on long car rides. So here is a temporary fix I made by reverting these two commits and rebuilding the CM kernel.
https://github.com/CyanogenMod/lge-...e1dd464b1e5aba74f7293c5e18f#drivers/bluetooth
https://github.com/CyanogenMod/lge-...49e0a49c9d90f2bafbf08822863#drivers/bluetooth
The official bug report can be found here, https://jira.cyanogenmod.org/browse/CYAN-518. If you are affected by this please head over and vote for it.
This is a temporary fix until CM patches the bug. I haven't had the time to really test the impacts of the reverting but it does cause a wake lock when BT is on. When I find time I'm going to look into fixing the removed code instead of simply removing it. Any other dev is welcome to pitch in. Current work on this project can be found here, https://github.com/nexwave-mat/lge-kernel-iproj/tree/cm-10.1-bluefix.
Usual policies apply. This is a WIP and I do not take any responsibility for problems resulting from its use.
Click to expand...
Click to collapse
File attached to post. Install as a regular zip in recovery. Wipe cache/dalvik.
MD5: c50b6630e6cab493af59c00df0821e52
Tested with version cm10.1-20130503-NIGHTLY-p930 of cyanogenmod. Kernel built on 2013/05/04 @10:57pm with repo sync about 30min prior to that.
@lyfkevin feel free to include this in your WIND kernel if you see fit.
Warning:
There was an official patch merged into CM. I would strongly suggest to discontinue use of this. More details, http://forum.xda-developers.com/showthread.php?t=2140790&page=27#269.
Just saw this, https://github.com/cyanogenmod/andr...mmit/ef61f8ebbf1119a29617dddbcf0a7753bf29bf2b. I will test and report back here if it is a fix or not for our devices problems.
the new kernel code have fixed this problem
nexwave-mat said:
Just saw this, https://github.com/cyanogenmod/andr...mmit/ef61f8ebbf1119a29617dddbcf0a7753bf29bf2b. I will test and report back here if it is a fix or not for our devices problems.
Click to expand...
Click to collapse
msjd said:
the new kernel code have fixed this problem
Click to expand...
Click to collapse
I installed 5/7 nightly and BT still crashed.
Sent from my GT-N8013 using xda premium
I installed 5/7 nightly and BT still crashed.
Click to expand...
Click to collapse
I have same.
nexwave-mat said:
Just saw this, https://github.com/cyanogenmod/andr...mmit/ef61f8ebbf1119a29617dddbcf0a7753bf29bf2b. I will test and report back here if it is a fix or not for our devices problems.
Click to expand...
Click to collapse
I played around with Bluetooth on full stock version 10.1-20130507-NIGHTLY-p930 of cyanogenmod and was not able reproduce any Bluetooth crashes.
I will keep playing with it but so far so good for me.
Click to expand...
Click to collapse
Looks like the fun isn't over. Just got a Bluetooth crash on full stock cm10.1 RC1.
nexwave-mat said:
Looks like the fun isn't over. Just got a Bluetooth crash on full stock cm10.1 RC1.
Click to expand...
Click to collapse
With or without Wind, and what version?
Sent from my LG-P930 using Tapatalk 2
For those flashing WIND kernel along with this fix, make sure you flash the fix after flashing WIND and not the other way around because, correct me if im wrong, flashing WIND over the fix will overwrite the BT commits.
NFleck said:
With or without Wind, and what version?
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
just1nsama said:
For those flashing WIND kernel along with this fix, make sure you flash the fix after flashing WIND and not the other way around because, correct me if im wrong, flashing WIND over the fix will overwrite the BT commits.
Click to expand...
Click to collapse
Full stock would imply without Wind. For that matter, and sorry if I wasn't clear, the fix is a custom build kernel. It replaces Wind or any other kernel currently on the device. The only changes between my "fix" kernel and stock are the two reverted commits in the OP.
If time permits I will look into it more and come up with a better solution. Although I read in an other post that @rmcc might be looking into this issue shortly. Although nothing is for sure...
I dun hv BT headset to test.
How does Bluetooth in wind 2.0rc0 work? Does it work well during turn on?
My friend dczz gave me another patch which fixed BT wakelock (battery drain) when BT switch off.
lyfkevin said:
I dun hv BT headset to test.
How does Bluetooth in wind 2.0rc0 work? Does it work well during turn on?
My friend dczz gave me another patch which fixed BT wakelock (battery drain) when BT switch off.
Click to expand...
Click to collapse
I'll test it with cm10.1 RC1 in the morning.
lyfkevin said:
I dun hv BT headset to test.
How does Bluetooth in wind 2.0rc0 work? Does it work well during turn on?
My friend dczz gave me another patch which fixed BT wakelock (battery drain) when BT switch off.
Click to expand...
Click to collapse
Yes it works well. I just turn off BT when done using and reset phone to stop battery drain. Text messaging over BT does not work but other than that it stays on and connected.
Sent from my GT-N8013 using xda premium
lyfkevin said:
I dun hv BT headset to test.
How does Bluetooth in wind 2.0rc0 work? Does it work well during turn on?
My friend dczz gave me another patch which fixed BT wakelock (battery drain) when BT switch off.
Click to expand...
Click to collapse
Replied in your kernel thread, http://forum.xda-developers.com/showthread.php?t=2119976&page=44#433.
Official CM patch
It seams there was a patch for our Bluetooth issue merge into the CM kernel a short while ago, http://forum.xda-developers.com/showthread.php?t=2140790&page=27#269.
@lyfkevin correct me if I'm wrong but I thing it would be better to revert your current Bluetooth fixes and merge CM's patch for version 2.0 of your WIND kernel. In theory it should stop crashes and allow deep sleep with BT on. Now we just need to test it. Let me know if and when you will have a new build up and I will gladly test it out.
nexwave-mat said:
It seams there was a patch for our Bluetooth issue merge into the CM kernel a short while ago, http://forum.xda-developers.com/showthread.php?t=2140790&page=27#269.
@lyfkevin correct me if I'm wrong but I thing it would be better to revert your current Bluetooth fixes and merge CM's patch for version 2.0 of your WIND kernel. In theory it should stop crashes and allow deep sleep with BT on. Now we just need to test it. Let me know if and when you will have a new build up and I will gladly test it out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=41241105&postcount=437
I just added a comment to the CYAN-518 that might explain some of the issues, or perhaps an additional bluetooth issue in cyanogen.
Just a quick note, I'm running the nightly 5/11 (day after the RC2 release). I'm able to connect to my Bluetooth portable speaker no problem and also I have a Sensordrone bluetooth device (multiple environment meters in one) and no issues connecting with that either.
...Previously I had the 5/6 nightly and it didn't even "see" any bluetooth devices.
Namuna said:
Just a quick note, I'm running the nightly 5/11 (day after the RC2 release). I'm able to connect to my Bluetooth portable speaker no problem and also I have a Sensordrone bluetooth device (multiple environment meters in one) and no issues connecting with that either.
...Previously I had the 5/6 nightly and it didn't even "see" any bluetooth devices.
Click to expand...
Click to collapse
I have test a nighly (guess it was 5/1 or 5/2) with the same result. Will give feedbck on RC2 on BT behaviour in next days.
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'
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.
I was the kind of guy who want to try some of the new version for this phone...
One issue I saw on each version except the original from bell is ... the bluetooth is not always working propely... not sure if @tdm can see the difference between v20f and cm bluetooth but since i'm back with this one i don't have to fight to have it connected to my car radio!
Anyone else having issue like mine??
Sent from my LG-P930 using xda app-developers app
Even the stock Gingerbread firmware wouldn't work with bluetooth keyboards (the stock ICS just cops out and has a message pop up that says that the phone is not compatible with bluetooth keyboards!). I found that only Cyanogenmod 9 RC1 and RC2, and Cyanogenmod 10.1.x stable builds work with bluetooth keyboards. Try Cyanogenmod 10.1.3 and see if that fixes the bluetooth problem.
handofstand said:
Even the stock Gingerbread firmware wouldn't work with bluetooth keyboards (the stock ICS just cops out and has a message pop up that says that the phone is not compatible with bluetooth keyboards!). I found that only Cyanogenmod 9 RC1 and RC2, and Cyanogenmod 10.1.x stable builds work with bluetooth keyboards. Try Cyanogenmod 10.1.3 and see if that fixes the bluetooth problem.
Click to expand...
Click to collapse
I have also experienced no bluetooth issues with Mokee 02072014 release version. Very reliable, bluetooth works like stock, no BSODs or reboot problems, and best of all its Kit kat.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
I have also experienced no bluetooth issues with Mokee 02072014 release version. Very reliable, bluetooth works like stock, no BSODs or reboot problems, and best of all its Kit kat.
Click to expand...
Click to collapse
I should try that version.
HoNo!'s almost-stock V20F and Sphinx 4.1 are the ones I found to have a reliable BT connection to FORD Sync, automatic connection. Everything else I tried I have to manually connect it and sometimes I have to do it 3-4 times to get connected with the exception of Carbon ROM which is pretty much 1 shot and it would be connected. I wouldn't even care for BT if it is not for the cellphone use bylaw in our town.