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
HI Guys,
i Updated my Phone via factory image to Android 5.1 all worked well during the update.
I spotted that with the stock 5.1 my phone got hot when active and the battery went down very fast (and by active i mean just doing normal stuff).
So i decided to go to cm12.1, installation also worked well, but had the same problems here.
Then i went back to stock 5.1 but still the same problems, my phone is getting hot and battery life is getting low when i use it.
When not in use its ok, it baerelly uses battery then.
I searched in forum and google also, but couldnt find anything rly helpfull, i think of going back to 5.0.1
TL: DR
Since Update to 5.1 Phones runes hot and the battery is going low very fast when in use.
Does anyone know this issue and has some advice to solve them?
Gretz from Germany
Hi,
My wife's gti9505's has an issue with the battery that I cannot seem to fix. One second it's at 75% then all of a sudden it's a 5%, then it goes to 50% and some times it reboots. I don't know if this might be related but she mostly feels this happens when she uses the uber app. She has the latest official android version (5.1..), I've tried installing a new rom with 6.0 but the problem persisted. I've bought her a new battery but the problem persisted. At this point I'm thinking that this MUST be a hardware problem. Any other solutions I may try?
The reboot problem might be a power button issue.
A few months ago, I flashed a 6.0.1 cyanogenmod rom(by Alberto96) onto my jfltexx(international) S4. Excellent Rom I must say, but since that flashing, my phone had been dying at 30%, (when I switch on the screen if its 30% or below it'd freeze then switch off). Thinking the ROM was the issue, I then reverted back to stock Samsung 5.0.1, but the issue persisted. I'm not a fan of the stock rom and would like to go back to CM or lineage, any idea what could be causing it?
I've eliminated the fact that it's a faulty battery because this is a new battery, and all my other spares that switch off at 30% work just fine on other devices.
Really hope you can help me resolve this.
Regards
Bout 3 weeks ago i flashed Havoc on my phone and everything went great, rooted with magisk just perfect.
I am now out of quarantine and realised location WONT work even though it's open.
Any help?
Anyone similar issues?
I didnt have problems with stock rom so it's not the antenna itself!
ROM: https://forum.xda-developers.com/lg-g6/development/rom-havocos-v2-1-t3893668
Gapps: "SUPER" package from https://opengapps.org/
I also have Magisk Installed. (rooted)
Bump. I still have this problem
Bump
Download app such as 'GPS Test' from the app store and check if gives you any numbers, whether it is detecting and connecting to satellites etc. Also, go into location settings and make sure either 'High accuracy' or 'Device sensors only' mode is selected. In software based issues such as custom rom sometimes battery saving (networks only) setting on its own doesn't work properly. If you still can't figure this out, best thing to do will be to install stock rom once again and for sure rule out that phone has not developed any hardware issues since you installed the custom rom. I had similar issue with a G6 once and I went through many many troubleshooting steps to fix it and in the end I left it alone but was pretty sure it was hardware failure because the GPS couldn't latch onto more than 2-3 satellites at a time. I remembered later that I had dropped the phone which probably messed up or loosened the GPS antennae connections.