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.

Nougat BT issues [FIXED]

As right now there is a transition to Nougat on many phones (AOSP 7.1 and CM 14.1 are released, many custom ROMs are released on Nougat platform...) be aware that there is confirmed bug in Nougat BT stack: no connection / disconnections even if HU is paired with your phone.
While it is not only MTC* specific (http://bgr.com/2016/09/29/iphone-7-bluetooth-problem-bmw-ford-kia/) I can confirm it is present (I installed CM 14.1 e.g. Nougat based ROM and BT connection is not working - it pairs, it connects and disconnects in a second saying "no phone").
Existing fixes and workarounds posted here on this forum (like changing init.qcom.bt.sh file etc.) are useless.
Google confirmed bug and it is expected that fix be with next AOSP release (expected in early December) but until we see it we cannot be sure it will fix connection issues with our HUs.
Anyhow, if anyone whish to try and experiment (I dont, I wait for fix by Google first) you may try what was used to fix very similar issues on MM a year ago: changing setprop ro.bluetooth.hfp.ver 1.7 to ver 1.6 (pay attention that Nougat does not have that proprerty set at all, so the file init.qcom.bt.sh is not at same location nor the same content in N as it was on MM - but you may try with build.prop if you like to experiment).
Search the net by keywords I hinted above for links and post your results if you experiment. It may be helpful for others.
EDIT: Issue is fixed in 7.1.1 build (and CM 14.1 nightly also)!

I am suffering from the same annoying bug.
Hope that bug will be solved ASAP in the next AOSP.

Same boat.
Sent from my A0001 using XDA-Developers mobile app

me too

for me last cm14.1 version (01/12/16) from cyanogenmod site is fixed and BT is works perfect (oneplus 3)

Fixed
Latest 7.1.1 fixed bug (work also with latest CM 14.1 nightly build)

Yestarday i updated my Nexus 6p to Android 7.1.1 OTA.
After that i am having problem with my Bluetooth Car stereo Connectivity, it's connect for a second and then disconnect, It's seems to be only with my android 4.4 RK3188 car head unit, i tried a several other Bluetooth devices and i success to connect, don't know why only with my car it's not working although it works until yesterday before the 7.1.1 OTA update...

fectivi said:
Yestarday i updated my Nexus 6p to Android 7.1.1 OTA.
After that i am having problem with my Bluetooth Car stereo Connectivity, it's connect for a second and then disconnect, It's seems to be only with my android 4.4 RK3188 car head unit, i tried a several other Bluetooth devices and i success to connect, don't know why only with my car it's not working although it works until yesterday before the 7.1.1 OTA update...
Click to expand...
Click to collapse
It looks like Nexus specific issue. It may be problem with release of 7.1.1 they used for OTA.
For instance, CyanogenMod nightly fixed exactky that issue for me. Still now WiFi Hotspot is not working, but CM just fixed that bug and I hope it will be fine with next nightly. That is why I like CM! they listen, they recognise and they fix a bug in a single day. Google is on opposite side. Exactly why I don't use Nexus and I install CM based ROM first day I get new phone

Title is a little mis-leading MR P.K..
Hate to rain on your parade, but as you have been so quick to jump into other peoples threads and hand out the B.S..
You start a thread then tell people to go and do thier own research and attempt a fix you yourself have not verified will work.. tut, tut.. is this not the mark of a good software developer..
Anyway.. on the new Huawei P9 and have stayed on A.6 as for now everything is working fine for me on the big M's Rom..
Love the way you bag Google development.. of course CM is going to Cherry pick the fixs as they are a small nimble team focused on fixing and pulling apart what has been released..
They haven't released Forward versions of Android under thier own steam as yet as they just follow what has been put out..
You still got to take your hat off to Google for going toe to toe with Apple and windows to bring to the massss what we take for granted.. and might I add.. putting up billions to grab the Motorola patients so that Android continues to be free..
Looking forward to your Bluetooth stack fix's P.K so I can upgrade to A.7 ?
Sent from my EVA-L09 using Tapatalk

PK..
Light Reading off topic.
​Cyanogen to shut down services by year's end
https://www.cnet.com/news/cyanogen-to-shut-down-services-by-years-end/
Sent from my EVA-L09 using Tapatalk

Issue fixed for Nexus 6P
Hey guys,
Just a note for the ones that have Nexus 6P (no rooted) and guess Pixels phones that the BT issues are fixed when you upgrade to Nougat 7.1.2
If you have a Nexus phone (like me) just enroll to the Beta program and upgrade to 7.1.2 Just tested and BT issues with my HU is fixed.
Cheers!!!!

how do you enroll to the Beta program? Never mind. Figured it out (https://www.google.com/android/beta) and up grading my Nexus non-rooted 6P to 7.1.2 (beta program enrolled pushed OTA 7.1.2) fixed the bluetooth issue with my phone (media worked voice calls would keep dropping the bluetooth connection) to my headunit (pumpkin RK3066 MTCB-JY-v2.86 running Malaysk ROM RK3066 800X480 version 44)

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.

Touch screen issues and Wifi connectivity fixed?

Hi folks,
I just got my brand new Pixel 2 XL and have two issues and wanted to know if they were fixed in the official 8.1 OTA (not beta). I have touch issues on the screen at the margins of the screen in the left corner. I am also plagued by some Wifi connectivity issues where no data is flowing even though the reception is great. I am on 8.1 with January security patch. I am just not sure if those problems were already addressed in past updates or if they will be fixed in future updates. Need this information for potential RMA.
Thanks,
Marco

Touch issues have been fixed in 8.1 per many...

galaxys said:
Touch issues have been fixed in 8.1 per many...
Click to expand...
Click to collapse
Hmm. That's worrisome then. I still have them. Thanks.

mgymnop said:
Hi folks,
I just got my brand new Pixel 2 XL and have two issues and wanted to know if they were fixed in the official 8.1 OTA (not beta). I have touch issues on the screen at the margins of the screen in the left corner. I am also plagued by some Wifi connectivity issues where no data is flowing even though the reception is great. I am on 8.1 with January security patch. I am just not sure if those problems were already addressed in past updates or if they will be fixed in future updates. Need this information for potential RMA.
Thanks,
Marco
Click to expand...
Click to collapse
Interesting wifi issue I may have the same.
Latley it's been better. On 8.1
Sent from my Pixel 2 XL using Tapatalk

I'm also having some wifi issues if I'm using whatsapp.web and my phone is connected to my wifi and then locks itself, I sometimes get "phone is not connected to wifi" or sometimes I have to open my phone to get messages from other apps, like snapchat, kik, whatsapp.
Very strange.

Whatsapp web not scanning on custom rom(s)

I recently unlocked bootloader, and installed pixel dust rom. Whatsapp web used to work fine on stock android 10, but it was not scanning on Pixel Dust. I later flashed dirty unicorn ROM, and the issue is still there. Has anyone else faced this? Is there a workaround?

Khizar Amin said:
I recently unlocked bootloader, and installed pixel dust rom. Whatsapp web used to work fine on stock android 10, but it was not scanning on Pixel Dust. I later flashed dirty unicorn ROM, and the issue is still there. Has anyone else faced this? Is there a workaround?
Click to expand...
Click to collapse
You are doing something wrong... I can use whatsapp web without any issues on PixelDust ROM. See screenshots.
Nitin

nitin.chobhe said:
You are doing something wrong... I can use whatsapp web without any issues on PixelDust ROM. See screenshots.
Nitin
Click to expand...
Click to collapse
Me as well, no issues with scanning the picture to enable WhatsApp Web, I use WhatsApp daily to communicate with my son overseas and I set it up all the time when switching ROMs. I just did the PD 10 today and scanned WhatasApp a few minutes ago.