Hello guys..
I had the CM7 ROM installed earlier which had issues with the Wifi connectivity but not regular, used to happen once in a while..
After the new Kernel got released on 28th by Haschcode.. i decided to take the plunge the CM9 way with gedeROM.. trust me it has been brilliant.. After the installation I m able to connect initially to wifi.. subsequently when i try connecting to the Wifi it has not been connecting..
I tried EneryROM which also has been giving same issues.. Need your help on this guys..
Also for information sake.. before installing the ROMs.. I wipe the cache, factory reset, Dalvik.. then flash the ROM
Would want to know if any of you guys are experiencing similar issues and if you had been able to get around it..Please find the screenshots attached..
I havent tryed energy but I did try gedeRom never could get it to connect period end of story not that it isnt a sweet rom and the developer has put very excellent effort into it others have had good results. I really dont have a clue why this differs from person to person or rom to rom but I do recall once being able to correct this under advanced connection or by simply not letting or letting google keep a backup of my device. Being in development stage there are little quirks that spring up that dont hold true for all users everyones methodology varies. I couldnt get the new miui to even boot some say to flash at a full charge can fix that problem.The new AOKP has been working very well for me but others have had issues dont know how much is directly related to rom/kernel/ user error at flash. Hashcode has done a briliant job with his kernel and the developers of these roms have too patience is a virtue at this point until some bugs are smashed. For me if I have alot of trouble I simply just move on till a later date then try again the wifi thing kinda is a deal breaker on a kindle without another way to connect to the net.
Edit: at one point there was a mac address problem with the new kernel I believe that was resolved but it gave every device the same mac address which I understand causes some routers to rebel.
kishorev said:
Hello guys..
I had the CM7 ROM installed earlier which had issues with the Wifi connectivity but not regular, used to happen once in a while..
After the new Kernel got released on 28th by Haschcode.. i decided to take the plunge the CM9 way with gedeROM.. trust me it has been brilliant.. After the installation I m able to connect initially to wifi.. subsequently when i try connecting to the Wifi it has not been connecting..
I tried EneryROM which also has been giving same issues.. Need your help on this guys..
Also for information sake.. before installing the ROMs.. I wipe the cache, factory reset, Dalvik.. then flash the ROM
Would want to know if any of you guys are experiencing similar issues and if you had been able to get around it..Please find the screenshots attached..
Click to expand...
Click to collapse
You might try just flashing the latest kernel (#8) to see if that helps.
Aesrys said:
You might try just flashing the latest kernel (#8) to see if that helps.
Click to expand...
Click to collapse
I m running on new kernel only.. donno y it is behaving like that..
But thepooch.. what u said is 100% true..the ROMs are nothing short of brilliance.. infact the icons r much sharper and the system is pretty smooth in CM9.. shd thank Hashcode and the other ROM makers..
I have an SMC router.. planning to test on a friends netgear this week lets see..
I am on AOKP Milestone 5, and WiFi is working fine for me. I just tried disconnecting and reconnecting again; no problem.
A really fine ROM, and yes; Hashcode is a god.
VaksenDK said:
I am on AOKP Milestone 5, and WiFi is working fine for me. I just tried disconnecting and reconnecting again; no problem.
A really fine ROM, and yes; Hashcode is a god.
Click to expand...
Click to collapse
@Vaksen.. I had flashed AOKP yesterday... same problem guess need to check out on a different router..
Anyways on a different note.. Hashcode is definitely God so are the others who create the ROMs for us!!!
WiFi issues
kishorev said:
After the new Kernel got released on 28th by Haschcode.. i decided to take the plunge the CM9 way with gedeROM.. trust me it has been brilliant.. After the installation I m able to connect initially to wifi.. subsequently when i try connecting to the Wifi it has not been connecting..
I tried EneryROM which also has been giving same issues.. Need your help on this guys..
Click to expand...
Click to collapse
3.0 Kernel released on 28th is changing Kindle's WiFi MAC address - you should check MAC filtering policy on your WiFi router. Settings/about/status is the way to find your "new" MAC address. Developers found solution for keeping original MAC address, it will be included in next kernel/rom versions - so do not erase Kindle's original MAC address from router's MAC filter list - you will need it soon.
chupchae said:
3.0 Kernel released on 28th is changing Kindle's WiFi MAC address - you should check MAC filtering policy on your WiFi router. Settings/about/status is the way to find your "new" MAC address. Developers found solution for keeping original MAC address, it will be included in next kernel/rom versions - so do not erase Kindle's original MAC address from router's MAC filter list - you will need it soon.
Click to expand...
Click to collapse
Thanx.. but i too know that.. my question is I dont have the MAC filtering activated.. so why is it failing then?
Have you tryed AOKP? No issues there
Thepooch said:
Have you tryed AOKP? No issues there
Click to expand...
Click to collapse
Yep.. no respite.. same problem
Ewwh that sucks There's got to be some kind of workaround have you tried advanced connections? Your router is very picky
Its a total shot in the dark but maybe you could try the Hellfire cleaner before you do a fresh flash not the nullifier I'm not totally sure about that one yet. Maybe there is some fragments left behind from your previous flashes that are bottlenecking you? What kind of wireless connection is yours?
I was having similar issues. I think Hashcode's kernels hate certain routers. What kind of router do you have?
My fix was setting my router to run with a static connection instead of with DHCP.
Can you please post a logcat in Hashcode's kernel thread? The issue will get resolved faster.
Sent from my Galaxy Nexus using XDA
Your fix might be here read the op for kernel adjustments and wifi fix http://forum.xda-developers.com/showthread.php?t=1591869
Router reset with ICS Hashcode 3.0
I have very similar issues you are all reporting. I can use CM7 on my Fire and the wireless works perfect almost all of the time. I gets a little screwy at time, and I just reboot the device and it works fine again for days. When I use any ICS with Hashcode it works GREAT for about 2 days. After that mark, any time i connect with the wireless to my dlink B/G/N router, it will actually reset the router (not settings, just off/on) over and over again. Does anyone know if this issue is being addressed? I am not much of a networking person to know what the Fire could be doing to cause my router to do this, so I am really at a loss.
Long time lurker on the forums, but my first post. I apologize if this is the incorrect place to post, but I wanted to share my findings in the hopes that it'll help someone else having the same problem
Problem: After upgrading to CM10.1 (Android 4.2.1) on my Verizon GNex [Toro], I was having problems keeping a wifi connection.
It seems that Google has acknowledged there is a bug in the OS (Issue 40065 - can't post the link since I'm a posting n00b on XDA). The issue was logged for Nexus 4 and 7, but I believe it's the same problem.
I downloaded the Wifi Fix tool from the Play Store. As per the Help file, I went into my router settings and changed Preamble Mode to "Long Preamble". After the router rebooted, my Galaxy Nexus seems to be keeping the connection much better. Not sure that it's 100% fixed, but at this point I'll take any improvement over what I was experiencing before.
Like I said at the top, hope this helps others who may be having the same problem.
tchaikin said:
Long time lurker on the forums, but my first post. I apologize if this is the incorrect place to post, but I wanted to share my findings in the hopes that it'll help someone else having the same problem
Problem: After upgrading to CM10.1 (Android 4.2.1) on my Verizon GNex [Toro], I was having problems keeping a wifi connection.
It seems that Google has acknowledged there is a bug in the OS (Issue 40065 - can't post the link since I'm a posting n00b on XDA). The issue was logged for Nexus 4 and 7, but I believe it's the same problem.
I downloaded the Wifi Fix tool from the Play Store. As per the Help file, I went into my router settings and changed Preamble Mode to "Long Preamble". After the router rebooted, my Galaxy Nexus seems to be keeping the connection much better. Not sure that it's 100% fixed, but at this point I'll take any improvement over what I was experiencing before.
Like I said at the top, hope this helps others who may be having the same problem.
Click to expand...
Click to collapse
http://code.google.com/p/android/issues/detail?id=40065
Rebooting the router only works temporarily if you experience this issue. It will end up having a weak connection awhile after. I live with it.
It wasn't the rebooting that did it - it was going to Advanced Wireless Settings on the router, and changing the Preamble Mode to Long Preamble. Am hoping that it doesn't degrade after time like you said, but will post an update tomorrow whether it is still working well.
I live with it as well. Plus, i do not see anything about preamble settings on my router.
Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?
http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2
What I really wanto to know if this issue is posted in the official google bugs tracker
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?
stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844
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.