Related
I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Dan76 said:
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Click to expand...
Click to collapse
I sometimes have issues reconnecting to my bluetooth headset (fixed by repairing) but no issues when it is connected. And I have a moto 360 always connected that has no disconnection problems. I would go with a factory reset!
Dan76 said:
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Click to expand...
Click to collapse
I know this is several weeks old, but yes I have this issue, and have done everything imaginable to get rid of it, to no avail.
My phone pretty reliably connects to my 360 (or, currently, Pebble), but is almost useless in my car. Fine for phone calls, but audio works 1 time out of 5 at best, otherwise it just does thta jumpy skip thing.
I initially thought it was because of Android Wear -- connecting to the watch was using too much bandwidth and interfering with the ability to talk stream audio -- but a) it's ONLY aproblem in my car (and my wife's car, so it's not JUST my car), never to, like, a standalone bluetooth speaker, and b) I completely wiped my phone and didn't install Android Wear or pear with a watch at all, and the problem resurfaced. A clean wipe almost always results in reliable bluetooth for 2 or 3 days, and then it gets jumpy, which HAS to be a clue (some state or buffer being corrupted / filled?) but I haven't been able to figure out what it's clueing me into.
This thread dives into the potential Android Wear connection, but no real solution.
If anyone who HAS experienced this figures out a solution, I'd really love to hear it.
Not sure if this applies. However, I experienced this EXACT problem when streaming music over bluetooth. This problem only happened AFTER I made or received a call. Reboot is the only cure. This is with 6.0 stock with Feb update. I tried 2 phones with the same problem. Both were new out of the box. This FW is obviously defective. I'm not sure why others aren't reporting this issue. My search for a phone continues....
insanedc said:
Not sure if this applies. However, I experienced this EXACT problem when streaming music over bluetooth. This problem only happened AFTER I made or received a call. Reboot is the only cure. This is with 6.0 stock with Feb update. I tried 2 phones with the same problem. Both were new out of the box. This FW is obviously defective. I'm not sure why others aren't reporting this issue. My search for a phone continues....
Click to expand...
Click to collapse
I can usually toggle off Bluetooth then back on and it's okay, but sometimes it does require a restart. SUPER frustrating when you're driving! I'm glad I'm not the only one, I just wish we'd get more info on this and maybe someday a patch.
I'm on my second phone now. The first one, the Bluetooth completely failed to operate anymore. I couldn't turn it on. I tried everything. So, I was able to get it exchanged at bb. Before it failed, I noticed that the signal strength was a lot lower than my old turbo. On my new mzf, I'm finding the same issue with the range. Has any one else has a signal issue?
Yes, I have exactly this issue. I suspect it is a MM software issue; there seems to be a problem with MM and bluetooth beyond just the MZF. I'm going to try to flash the stock recovery files and see if that helps.
i returned mine for bt issues. audio playback suddenly was stuttering on all devices.
Sent from my XT1650 using Tapatalk
After this last update, it seems my BT is working better. I'm gonna do a couple distance tests that were problems before this weekend.
Well, it looks like my BT is working better now. I'm assuming something changed from the last update, but now when I step into another room, the BT speaker doesn't get crackly like it used to.
I just go a new Nexus 6P. I am having Bluetooth issues. My Coda button which worked fine on my Note 3, 5 and 7 will not work unless it is the only bt device connected. Also any BT device connected suffers occasional dropouts even when only 2 to 3 feet from the phone.
I thought maybe it could be WEDA rom so I spent all night unrooting, wiping and doing a complete reset to stock. I did allow it to update to 7.0 nougat after first boot.
Anyone else experience BT issues? Any fixes available? Would I have been better off staying on MM 6.1?
Thank You very much for any advice you could offer. If I can't get this fixed this weekend I will need to return it to BB.
Having an issue with the Bluetooth on this phone. When streaming music to a stock head unit (no navigation) on a 2015 Mitsubishi Lancer, the songs speed up for about a half second, every 30-40 seconds. It's not skipping, pausing or anything like that, it's actually speeding up the temp and pitch.
An S7 Edge doesn't do this with the same head unit, but the user was not happy with the S7E.
I haven't tested with other devices (but I will shortly), because she only listens to music in the car.
Anybody else see this issue? Thanks!
Same issue here. Happens in my car, with my shower speaker, and with my portable speaker
(UE Boom 2). It is incredibly frustrating and has been an issue with my phone for a while. Really miss my note7.
raduque said:
Having an issue with the Bluetooth on this phone. When streaming music to a stock head unit (no navigation) on a 2015 Mitsubishi Lancer, the songs speed up for about a half second, every 30-40 seconds. It's not skipping, pausing or anything like that, it's actually speeding up the temp and pitch.
An S7 Edge doesn't do this with the same head unit, but the user was not happy with the S7E.
I haven't tested with other devices (but I will shortly), because she only listens to music in the car.
Anybody else see this issue? Thanks!
Click to expand...
Click to collapse
have you done a factory reset?
I know my bluetooth earbuds did this sometimes. It happened after trying to skip a song.. If youre not rooted, try a factory reset or see if your phone has an update? If you are rooted. Id wipe youre phone through TWRP and reflash your rom to see if that helps.
OK, so the phone isn't rooted (and never will be) and a factory reset is completely off the table. I do believe that it is either fixed or worked around, I switched the music player to PowerAMP 3.0 Beta latest build and it seems to be completely gone.
i also have this same issue when bluetoothing to my car. i still havnt found a fix/workaround for it. had this issue with stock ROM/and now the custom ROM so hopefully a update will fix it.
I've had this issue in 2 of 3 places that I've paired up.
1) Dodge Durango - Music from any app is basically unlistenable. I get about 10 seconds of music, then a bunch of stuttering, then about 10 seconds of music.....
2) Samsung Soundbar - Same description as above, but only when more than 5 feet from the soundbar. BT should be at least 30feet good in an open room, right? Yeah, not for me.
3) Jawbone Jambox - Everythign works fine here from everywhere in my condo. Separate, rooms, no problem. Weird.
So yeah.. Not sure if it's a BT buffer thing, but I certainly can't find any settings that might make any difference.
SUCKS
Same problem here. 2017 F250 Sync 3. Before I rooted it would randomly drop the bluetooth connection. Seems a little worse now that I am rooted running the stock Rom. Thinking maybe I should try an ASOP rom?
I do not have this issue or dropped connections. I do, however, get a 3-4 lag between the sound and the mouth movement on screen. It only happens with my LG V20 and my previous phone LG Nexus 5X. Before that I had a Huawei Nexus 6P that worked perfect.
mrcoolgli said:
Same problem here. 2017 F250 Sync 3. Before I rooted it would randomly drop the bluetooth connection. Seems a little worse now that I am rooted running the stock Rom. Thinking maybe I should try an ASOP rom?
Click to expand...
Click to collapse
I have a 2016 F150 with Sync 3 verizon 2.2 with Android Auto and I never had bluetooth issues until I rooted my V20 with Verizon. I also was having bluetooth issues with my Android Wear watch after rooting, it would randomly disconnect and never connect again until rebooting the phone. What fixed it for me was flashing the modStock kernel, I am currently on the WETA rom and everything is perfect.
xbmoyx said:
I have a 2016 F150 with Sync 3 verizon 2.2 with Android Auto and I never had bluetooth issues until I rooted my V20 with Verizon. I also was having bluetooth issues with my Android Wear watch after rooting, it would randomly disconnect and never connect again until rebooting the phone. What fixed it for me was flashing the modStock kernel, I am currently on the WETA rom and everything is perfect.
Click to expand...
Click to collapse
So I wiped my phone and loaded the MegaROM. It's much better. Not perfect. So I believe most of the issue are likely software. Again stock the phone had significant issues. My old V10 rooted never missed a beat on this truck.
Bluetooth can always have random problems pop up unexpectedly. Aside from the occasional glitch here and there, I havent had any major bluetooth issues on t mobile stock Rom or on WETA (which I'm currently on)
My V20 never connects to my car bluetooth automatically, and doing it manually every time is driving me insane. I'll try rooting and flashing some ROMs tonight to see if that solves the issue.