Develop Bugs

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.

Official CM13 crashing on wifi connection (Nightly 29-07)

Dear XDA members,
I'm sorry for posting in this section, but since I'm new to the scene I can't post questions or topics in the appropriate section. So sorry for my noobyness..
Anyway I installed the new CM13 Nightly today. It is working great and even got the storage bug (gallery crash) fixed by removing the line ro.sdcardfs.enabled=true from build.prop (hint for anyone else needing this fix ). However I've found a bug that was stopping me from using CM13 in the first place, it was rebooting my device everytime it started up and connected to wifi... Whenever I connect to my Apple Airport Extreme the device crashes and reboots (just like the gallery bug). It is an older model Airport Extreme (the 802.11n version, so no ac wifi). It doesn't happen on the other router installed here, which is a Comtrend.
Could someone tell me where and how I report this bug or maybe even how to fix it? I haven't seen anyone else post it on the forums and it doesn't happen on OxygenOS or pre-official releases of CM13 based roms.

Thank you!
ShotByMeir said:
Dear XDA members,
I'm sorry for posting in this section, but since I'm new to the scene I can't post questions or topics in the appropriate section. So sorry for my noobyness..
Anyway I installed the new CM13 Nightly today. It is working great and even got the storage bug (gallery crash) fixed by removing the line ro.sdcardfs.enabled=true from build.prop (hint for anyone else needing this fix ). However I've found a bug that was stopping me from using CM13 in the first place, it was rebooting my device everytime it started up and connected to wifi... Whenever I connect to my Apple Airport Extreme the device crashes and reboots (just like the gallery bug). It is an older model Airport Extreme (the 802.11n version, so no ac wifi). It doesn't happen on the other router installed here, which is a Comtrend.
Could someone tell me where and how I report this bug or maybe even how to fix it? I haven't seen anyone else post it on the forums and it doesn't happen on OxygenOS or pre-official releases of CM13 based roms.
Click to expand...
Click to collapse
Thanks for the gallery fix!
The thing was driving me nuts...
I'm on the July 30th nightly and there is no issue with the WiFi connection.

Corpal said:
Thanks for the gallery fix!
The thing was driving me nuts...
I'm on the July 30th nightly and there is no issue with the WiFi connection.
Click to expand...
Click to collapse
My wifi is working fine with any other router, my op3 just crashes when I connect to my Airport Extreme..

This seems to be a persistent bug because when i connect to my Apple airport Router my phone crashes too.

Hi
I've a same problem with connection on Airport. But my ROM is Ressurection Remix (Build 30/07/16). I think that the problem is present on all CM-Based ROM.

Jesus, finally, that bug make me crazy. Airport Extreme and CM13 in my OnePlus3 crash and reboot the device. Im waiting for fix patiently.
Whit oficially ROM or based ROMS all ok.
and, THANK YOU DEVELOPERS FOR ALL.
Best regards.
P. D. - Sorry for my poor english.

Wynztech said:
Jesus, finally, that bug make me crazy. Airport Extreme and CM13 in my OnePlus3 crash and reboot the device. Im waiting for fix patiently.
Whit oficially ROM or based ROMS all ok.
and, THANK YOU DEVELOPERS FOR ALL.
Best regards.
P. D. - Sorry for my poor english.
Click to expand...
Click to collapse
Yes me too, would like to post this in the Official CM13 Forum but can't since I'm a junior member :/
This is the only problem I have, CM13 is quite stable in its current condition

Seems to only be with the airport

Same problem
Thank you! I thought I was crazy. For some strange reason i crashes hard when getting an IP address. I connect via an old Apple time capsule.

rumagent said:
Thank you! I thought I was crazy. For some strange reason i crashes hard when getting an IP address. I connect via an old Apple time capsule.
Click to expand...
Click to collapse
Old airport extreme here and Does exactly what you said. Went back to OOS for this. I went to the dentist, connected to wifi and my phone rebooted. Was a bit too annoying

ShotByMeir said:
Old airport extreme here and Does exactly what you said. Went back to OOS for this. I went to the dentist, connected to wifi and my phone rebooted. Was a bit too annoying
Click to expand...
Click to collapse
Can you post the issue on the development thread. Please. I'm too new to do so.

akiva.r said:
Can you post the issue on the development thread. Please. I'm too new to do so.
Click to expand...
Click to collapse
Already did that. Someone was supposed to look into it but didn't. I provider logs, but I guess it is nog considered a very important bug I already started a thread in the cyanogen forums so let's hope that helps.
Btw if you want to use cm, you van use Arter97's build. That build with his kernel (you Have to add it manually) doesn't have the wifi bug official CM with his kernel also doesn't have the wifi bug.

Believe to have figured out the issue
I am having this exact same problem when connecting my OP3 to my Airport Extreme. I have messed around with several different ROMs and discovered that the original Oxygen OS and Freedom OS (basically a modified version of Oxygen) don't crash when connecting to the Airport Extreme. This has happened to me in two different places, with two different Airport routers. It would connect just fine until I first updated one router to the latest version for the Airport (version 7.7.7), and then a few days later the same upgrade with the other one before realizing that this was why my phone kept crashing! Problem is, is I'm not sure what firmware of the Airport actually worked with my OP3. I've tried downgrading my Apple router (generation 7), but it will only let me go down to version 7.7.3 which still crashes the phone.
It has to be an issue with router's version, rather than a ROM issue because this only started happening with me after the Airport update. Best thing probably to do at this point is report it to Apple, and hopefully they will do something about it instead of just locking every non-apple product out of their 'Apple Products only can communicate with one another circle'... I'm unable to post an actual link to the website to report bugs to apple, so here is the link in a 'disguised' manor. apple(dot)com(ForwardSlash)feedback(ForwardSlash)airportextreme(dot)html
I just typed out a bug report myself and sent it to apple. The more people that report it, the more likely they will be to fix it. In the meantime, I also requested that they provide me with the original firmware that the 6th generation Airport Extreme came with, because I know it worked with my OP3. If I get it, and it works I'll provide a Dropbox or Google Drive link for the download on a future reply to this thread.

cquick7 said:
I am having this exact same problem when connecting my OP3 to my Airport Extreme. I have messed around with several different ROMs and discovered that the original Oxygen OS and Freedom OS (basically a modified version of Oxygen) don't crash when connecting to the Airport Extreme. This has happened to me in two different places, with two different Airport routers. It would connect just fine until I first updated one router to the latest version for the Airport (version 7.7.7), and then a few days later the same upgrade with the other one before realizing that this was why my phone kept crashing! Problem is, is I'm not sure what firmware of the Airport actually worked with my OP3. I've tried downgrading my Apple router (generation 7), but it will only let me go down to version 7.7.3 which still crashes the phone.
It has to be an issue with router's version, rather than a ROM issue because this only started happening with me after the Airport update. Best thing probably to do at this point is report it to Apple, and hopefully they will do something about it instead of just locking every non-apple product out of their 'Apple Products only can communicate with one another circle'... I'm unable to post an actual link to the website to report bugs to apple, so here is the link in a 'disguised' manor. apple(dot)com(ForwardSlash)feedback(ForwardSlash)airportextreme(dot)html
I just typed out a bug report myself and sent it to apple. The more people that report it, the more likely they will be to fix it. In the meantime, I also requested that they provide me with the original firmware that the 6th generation Airport Extreme came with, because I know it worked with my OP3. If I get it, and it works I'll provide a Dropbox or Google Drive link for the download on a future reply to this thread.
Click to expand...
Click to collapse
It was a rom issue and it is fixed in CM builds after 18/9, I tested the commit before it went live. Don't use any kernel before that date and you're fine . The Apple routers are fine haha. There was a variable defined as a wrong type, which caused a stack overflow when connecting to an airport.

ShotByMeir said:
It was a rom issue and it is fixed in CM builds after 18/9, I tested the commit before it went live. Don't use any kernel before that date and you're fine . The Apple routers are fine haha. There was a variable defined as a wrong type, which caused a stack overflow when connecting to an airport.
Click to expand...
Click to collapse
Same issue with RR.How to solve using any zip or replacing files.?

amol1223 said:
Same issue with RR.How to solve using any zip or replacing files.?
Click to expand...
Click to collapse
Flash newer kernel over it or just wait for a new build.

amol1223 said:
Same issue with RR.How to solve using any zip or replacing files.?
Click to expand...
Click to collapse
Worked. Thanks a bunch.

has anybody had issues connecting to a car's bluetooth on Nougat 7.1.1 ?

un-pairing and re paring + reset car's Bluetooth - didn't solved it...
I remember that 6.1 had this problem too until monthly security fix it...
Any suggestions to fix this?

Sorry, no suggestions to fix it. Just confirming that I have car BT connectivity issues as well since 7.1.1.
I can connect the device, but the BT connection keeps dropping and coming back every few seconds.

Thanks for confirming this, tried the pixel 7.1 rom back in October and had the same issue, been waiting to hear if they fixed this on the official 5x rom but looks like they haven't, so sticking with 7.0 until they do.

I have no issues connecting, but I am using the PN 7.1.1 rom, not stock.

I'm on PureNexus, too, and had no problems, neither on 7.0 nor 7.1.

Yep here. Problem is with stock rom. Cm and purenexus works just fine. I wrote to google and they were suggesting 1:1 support which I can't use because of my country.
Sent from my Nexus 5X using Tapatalk

Also having this BT carkit connect issue since 7.1.1 update. It connects/disconnects every few seconds. I am on stock ROM.

Best shot is to wait for google to hopefully fix this, which I highly doubt.

OnePlus 3 Problems with Car Bluetooth connection

Hi all,
Since the last few firmware versions (OS 4.02 and above) I´ve been experiencing some issues exclusively with the Bluetooth connection of my car (Jaguar XE). I couldn’t fixed the problem even with the last firmware version rolled out via OTA (4.1.0).
In the last two months the connection of my Jaguar has not been stable at all. Most of the times I am able to pair my phone with the car, upload my contacts and so. However, once I start to transfer music of Spotify via Bluetooth, it keeps failing the "multimedia audio" and the connection is interrupted the whole time. I also lose the connection with the “phone audio”. I seems that my phone disables both connections intermittently. My guess is that Android Nougat is a "control freak" of permissions and this leads to issues with some car stero units.
In the previous versions of the firmware (4.01 and below) I didn´t experienced such problem. In the past I did have perfect connection to play spotify in my car with my same Oneplus Unit. I am very confident that there is nothing wrong with my car stereo unit since the Bluetooth still working fine with my wife´s phone. I haven´t upgraded my Jaguar´s firmware lately…so that shouldn´t be the source of my problem.
Despite of all this, the Bluetooth of my Oneplus unit works perfectly fine with any other Bluetooth devices . In fact I am able to enjoy full connection playing music with my External Speaker (UE BOOM 2) and my Xiaomi roidmi 2s –used in my other car that lacks of Bluetooth technology -.
I´ve tried everything. A couple of days ago I even performed a factory reset using the last version of firmware (4.1.0). Of Course I reset system settings, wiped cache and all data (music, pics…etc)…but still experiencing the same issue. I am desperate.
Any instruction will be very much appreciated.
Thank you in advance.
Kind regards,

So there was another thread on these boards, cant find it for right now... but in my experience the problems were only present on OOS rom's.
Perhaps not the best solution, but have you tried a CAF or Lineage OS based rom? All my problems went away after I made the switch
Good luck

Gomezie said:
So there was another thread on these boards, cant find it for right now... but in my experience the problems were only present on OOS rom's.
Perhaps not the best solution, but have you tried a CAF or Lineage OS based rom? All my problems went away after I made the switch
Good luck
Click to expand...
Click to collapse
Thank you Gomezie, I´ve read all the threads but I dont seem to find the solution.
I stick to stock os. Never changed my stock rom.
The funny thing is that OP stated in its last changelog that they have fixed bluetooth problems....
Kind regards,

Hi, my one plus 3 has the same problem. Done all the required resets and clearing of cache and it still would randomly connect and disconnect. Problem only surface after the recent 4.1.0 update.
My kids phone and wife's phone all have no issues.
My op3 connects with all other Bluetooth devices without any problems.
Mine is a f-pace .

Same problem in Mazda 6
Hi, I've been experiencing similar problem in Mazda 6 after software update. Everything was working perfect in previous versions. I my case problem is with using Spotify. Phone connects to the headunit, just after engine starts with no isuess, but the music won't start to play. Only way to start playback is to disconnect the phone manually and reconnect every single time. Re-pairing the phone with car doesn't help.

I sent an email to customer service a couple days ago. i haven't got any reply yet. I will let you know.
Regards.

Brugalete said:
I sent an email to customer service a couple days ago. i haven't got any reply yet. I will let you know.
Regards.
Click to expand...
Click to collapse
I finally did receive a reply from OP customer service: The only solution they offer me is trying a downgrade to OS Oxygen version 3.2.8. This is the link suggested by the technical agent to do so:
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
I haven´t done it yet since I am not eager to this idea.
On the other hand, in the meantime, OP rolled out new OTA 4.1.1. I made the upgrade to the latest firmware version. It seemed to work at first. However right now I am having the same problems with bluetooth disconnecting the whole time.
Any other experiences?? Have anyone solved this issue with new OTA???
Kind regards,

Bluetooth and 4.1.1
It's worse now on 4.1.1. definitely not the car, Samsung works ok

Hi,
I've experienced the same problems starting on OpenBeta 12 and continuing through to OOS 4.1.1. I've posted in the Open Beta 12 thread on the Oneplus forums, and have been contaced by Oneplus regarding the issue. For the Open Beta I have provided log files for them, but due to work and private life getting in the way have not been able to do the same for OOS 4.1.0 or OOS 4.1.1. Also, I did not clean flash, but dirty flash - because I'm really lazy and stuff. It needs too much time, to be honest
Maybe if everyone who has the problem here contacts the guys at OP or the OP forums, respectively, providing logs etc. the problem can be solved faster.
I did some googling around and found a few articles that hinted in the direction of Android 7.1.1 being the culprit, which would mean that Google needs to fix it. In these articles, it said Nexus devices, and a fix coming up...don't know...
Best regards,
Chris

My phone audio always works fine but the media audio on both my nissan and ford sync system works randomly or not at all on both stock and Lineage based roms. My wife's iPhone 6s works perfectly every time on both cars. Fortunately for me it's not a big deal since both cars have usb inputs and I keep all my music on thumb drives...My old Galaxy S6 Edge works fine on both cars too so I am not sure why the OP3 is so spotty.
---------- Post added at 09:24 AM ---------- Previous post was at 09:23 AM ----------
kennonk said:
My phone audio always works fine but the media audio on both my nissan and ford sync system works randomly or not at all on both stock and Lineage based roms. My wife's iPhone 6s works perfectly every time on both cars. Fortunately for me it's not a big deal since both cars have usb inputs and I keep all my music on thumb drives...My old Galaxy S6 Edge works fine on both cars too so I am not sure why the OP3 is so spotty.
Click to expand...
Click to collapse
I should also mention I ordered my OP3 on release day and this has been true since the beginning.

OP3 not working error unable to mount storage data
I have tried rooting my OP3 but I landed up getting my phone into a mess. I think my OS is not working properly and my phone is getting stuck at one place while rebooting and when trying to use recovery mode it is getting stuck at twrp page. I am unable to connect my phone to my pc. Can u please help me getting it resolved

FahadMemon said:
I have tried rooting my OP3 but I landed up getting my phone into a mess. I think my OS is not working properly and my phone is getting stuck at one place while rebooting and when trying to use recovery mode it is getting stuck at twrp page. I am unable to connect my phone to my pc. Can u please help me getting it resolved
Click to expand...
Click to collapse
Ask your question in the proper place. This is a thread regarding bluetooth connectivity.

Bluetooth problems after Jan update?

A number of people on the Reddit googlepixel forum are reporting new bluetooth problems, like dropped connections and unable to connect, after upgrading to the January update.
I was planning to update my Pixel 3 XL tomorrow, but this issue is making me pause.
Are any xda members seeing new Bluetooth issues?

No problem here.

I have been using BT in my car for multiple phone calls calls and streaming Pandora since yesterday morning. No issues at all. I have not used Android Auto since the update though. Even before the update I found the interface a bit clunky even though it was working OK.

Funny, I just posted on Android Central about how the update fixed my BT problem. Previously, every time I got into my car, it gave a connection request(PIN and contacts authorization etc.) even though its been synced many times before. After the update, the past couple days no issues when plugging my phone in and Android Auto starts up right away and messages access is already there.

no problems with rooted stock rom on jan update

I use BT for my watch and headphones and no problems before or after Jan update. Perhaps tweaking the version of BT in developer settings could help.