Database Users

[Q] Oxygen, ICS, CM7 and Official

Not being able to post on the Development sections cramps on my style a bit, but I have a couple of questions:
* First of all, I am still on Oxygen, do you guys think there's any good reason to switch? I like Oxygen a lot and apart from a couple of issues (see below) I've been very happy with it... Will dzo ever show up again and merge the new drivers into his release?
* Have the camera and GPU driver from the official 2.3 been ported to any other ROM?
* I've been seeing a lot of ICS related ROMS in Development as of late, is there a fully functional ICS ROM yet? What's stopping us, since it seems almost every other device is making some progress with it (i.e: having hardware acceleration enabled, radios working, etc.)?
Problems with Oxygen:
* Light Sensor behaves strangely: for example, with auto brightness enabled, turning on or off the light in my room makes no change in screen brightness. If I put the device close or directly under a lightbulb it will only then begin to change. I can confirm this with some sensor testing apps. Is there any way to calibrate the light sensor?
* Microphone acts strange: I have never seen anyone report this, but when I connect headphones, then try to use for example voice dialing or voice commands it will not work (wait forever) or simply give an error. If I disconnect the headphones after I tried to use voice it will never work again unless I reboot. If I connect headphones, never use voice, and then disconnect them and use voice it will work as it should
* Signal Strength very irregular: I live in a area with difficult reception, but signal strength is insane, sometimes is goes from 0 to full bars like no big deal
* Camera's FPS very jumpy (new drivers will fix this?)
* No access to internal storage: I knew this going in, but still...
* Flash videos sometimes green and overlapping the screen. This happens with both the YouTube app and any video player that can play FLV. It only happens from time to time and I can't reproduce it.
I went straight from stock (TMN Portugal) to Oxygen, never messed around with any other ROM (I tried CM7 for half an hour or so) but these little things start to bother me, plus it breaks my heart to know that the camera and GPU could be much smoother just by using different drivers. It also scares me that Huawei disabled the standard method of installing Recovery and rooting, so I'd prefer not to upgrade to the official ROM right away. So, is it worth to change ROM at this point? Can you help me with any of my problems with Oxygen?

Hi!
I tryed "all" ROMs I found here in XDA, Oxygen for me is not enough, it just lacks of "options" I love the Cyanogen Settings, you can do a lot of customizations there. Im on custom ROMs for 5 months now, never had a problem with the phone itself. Strange rebooting, camera stopped working and drainage of the battery does NOT count in here. I would suggest you try CM for more than a half hour since - in my opinion - it is the best. I hate the original Froyo, because it lacks of customization. So MIUI is not an option for me, it is just to simple. I was thinking I know all about flashing, but yesterday I just bricked my u8800, simply because I did not notice the + on the end of the official 2.3 update and installed update for u8800+.
My suggestion is, to follow guides here on XDA (they are excellent) and try all the ROMs, and see which one suits you best.

I'm also very happy with Oxygen, I'm still on r1 and have no major issues at all, so thank you very much dzo!
But I hope for the future that dzo will continue to update this rom so we can get better drivers for camera and other small fixes. It looks like the official rom will never be an stable option for us...
Mach III

SM-N900W8 & CM11 M12 bugs and issues :(

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

A clue to fixing GPS

Hi all,
I recently upgraded from 4.4.2 stock rom to 6.0.1 stock rom and everything worked fine except the GPS. I tried a few different fixes like changing the gps.conf, and a few different apps and could see there was some signal but it could never seem to get a lock. Sometimes it seemed to get a lock for a split second then drop it again.
I ended up going back to my 4.4.2 and GPS works fine again. So the simple conclusion is this is firmware based. I'm no expert but would be willing to help if someone wants to investigate this further. There has to be some GPS related files from the KK firmware that can be exported to MM to make it work
Keliuss

GPS has always been kinda weak and slow due to the module itself. Did you experience the auto brightness bug as well?

kom-pakt said:
GPS has always been kinda weak and slow due to the module itself. Did you experience the auto brightness bug as well?
Click to expand...
Click to collapse
Auto-brightness was working fine for me. Just the GPS issue noted.

OP2 Screen rotation periodically stops working

Hi folks
I received my OP2 in July 2016, and this issue has been a mild periodic annoyance. As I approach the end of my warranty, I want to be 100% confident that this issue is software rather than hardware... (so rather than a fix, my highest priority is confirming that I do not have a hardware defect)
The issue is that the screen rotation will stop working for most, but not all apps (OnePlus Camera is the sole exception, it seems). It will rotate normally for a couple weeks and then I'll notice in some app, usually YouTube or Facebook first, that the screen orientation won't rotate anymore. Once I notice it in any app, no other app rotates either except the stock camera. I have been experiencing this symptom on-and-off for most of the time I've had the device, spanning multiple OOS releases (currently 3.5.8 and still happening).
A reboot fixes the condition, then it works fine for a week or two and comes back. OnePlus support suggested a factory reset, which I've done pursuing this issue before, and it didn't help (it immediately helped, obviously, but the issue did return on the same schedule as before).
I had my OP2 rooted, but still using the stock ROM otherwise, for several months (to be able to use Adblock). I reverted to 100% stock configuration pursuing this issue, it happened the same before/during/after the time it was rooted.
I have checked out the accelerometer with the app "Test Your Android" and watched the graph in the "gravity sensor" test. When the phone is in its non-rotating state and I rotate the phone, the graph lines cross but the app stays in portrait. This makes me think the phone knows it has rotated. I reboot the phone, redo the same test, and the graph looks similar except the app now rotates as well (ironic, really).
Is there a background service for "screen orientation" similar to how Play Services provides GPS information to other apps? If so, am I right in suspecting that the service responsible for answering the question, "what way is the device oriented currently?" is either not answering, or answering incorrectly?
I would prefer not to go to a third party ROM just to test this as I'm very happy with the current config of my device, other than this issue popping up from time to time. Any input is appreciated.
Thanks!

OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.

utkarsh102 said:
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
Click to expand...
Click to collapse
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.

k1shy said:
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
Click to expand...
Click to collapse
In case you want suggestions, try these:
Bliss
Halogen
Validus
Lineage 13

Well, I have the same issue on my OP2 intermittently and it does not matter which rom I am using. In addition to OOS, I have had this issue on Marshmallow Cyanogenmod / Nougat Lineage based roms. Sooner or later it always returns. It seems to happen after longer uptime periods. E.g. with OOS3 I had an uptime stretch of 40+ days (without a reboot), so during this time I experienced the autorotation issue multiple times. It seems to get fixed by itself, but then comes back again. A reboot fixes it usually for longer period of time. As I am now on a custom rom, which is updated quite often, at least once of twice a week, the uptime stretches are not that long and I do not experience this issue often. I have noticed that the step counting sensors also stop working intermittently.
On rooted lineage based rom you can manually restart the sensors with following terminal commands:
su
stop sensors
start sensors
Don't know if this works on OOS. I made a tasker task shortcut for this on my homescreen.

Interesting...I have had the problem on-and-off I'd say, sometimes it follows this ~2 week pattern, sometimes it'll go longer than a month with no issues that I've noticed. Of course, it's also fairly rare that I watch videos on my phone and this is the main time that I realize it won't rotate.
Of course, with the current trend being to make all videos square with unnecessary obnoxious text in the letterbox black space, I suppose I'll never need to rotate my phone again </sarcasm>.
Prior to utkarsh102's suggestions I had already flashed AOSPExtended so I'm going to try rolling with this for a short time, if any issues surface (unrelated to my rotation issue) I'll try another ROM. Given that I'm trying to diagnose this issue before my warranty runs out (yeah, shoulda done it sooner, I know) I'll need to have a usable solution that can run stable for weeks uninterrupted to catch this again, if it's going to happen again.
FYI OnePlus support was entirely unhelpful about this issue. They completely disregarded the fact that it is intermittent and was not currently happening when I reported it to them. They were not able to suggest any diagnostic effort I could take to narrow down the issue further. Viewing the accelerometer readings was my own idea, not theirs. That suggestion absolutely should have come from them.
I do know I'm/we're not isolated in having this issue as there are other forum posts on various sites complaining of it.
I'll keep this thread updated with my findings, in the meantime anyone who has experienced this issue please chime in. It would be helpful to present to OnePlus, though I get the impression they won't care as they seem to have classified the 2 as a legacy product at this point. It's not like we're trying to get parts for a dot-matrix printer here.
Edit, October 2017, to provide an update without bumping the thread:
I've been using AOSPExtended on a constant basis since my last update to this thread and while I have experienced a variety of other issues, this particular one with the screen rotation has not affected me. My uptime has never been super long, but long enough at times that I should have seen this issue if it were going to happen following the same pattern as before.

GPS stopped working

Hi guys,
I've got an A2017G running A2017UV2.1.0B12 (So European running American firmware).
It's been working great for years, but recently the GPS antenna stopped fixing satellites. Previously the GPS was a bit slow, but I'm confident it was working to some extent. Now it's unusable.
It does see lots lots of satellites when I run the GPS status app, but does not lock to any even after resetting the AGPS data, recalibrating the gyro and accelerometer... I've tried installigh stock A2019G firmware and the problem was not resolved. I have made some hardware changes over time (battery and vibration motor), but I'm not sure the problem started after one of them. Yesterday I opened the phone and tried to identify the GPS antenna contacts, but wasn't sure which ones I had to look at. They all seemed to make good contact and I even tried forcing a contact with alluminium foil. Nothing. GPS Status reports the GPS sensor is working, not sure if that's reliable data. Does anyone know where the GPS antenna is?
I'm wondering if this is a hardware issue or maybe something went wrong with the firmware radios (not sure I fully replaced everything replaceable when I installed European software).
Any ideas? Thanks!