yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Sultanxda:
This is an infamous bug that has plagued the OPO since forever. I thought my ROM wasn't affected (since I'm using OxygenOS camera libraries), but I guess it is. You're the first person to ever report this with my ROM.

How often does this happen?
[ONE Original Android Development] Spider-Vice:
It could be a camera app issue in this case as well, are you using Snapdragon Camera?
[ONE Original Android Development] linuxxp:
Almost always. Today 9 of 10 photos.

Yes, I use snapdragon camera app.
[ONE Original Android Development] Spider-Vice:
Strange, because I have never encountered this issue, even with a picture I took just now with flash.
[ONE Original Android Development] Sultanxda:
Did you change any settings in Snapdragon Camera that could have caused this? Also, could you try enabling Red-eye Reduction and see if it fixes it?
[ONE Original Android Development] Juli112:
I have some bluetooth audio (music) issues since the 17/10 build with my mercedes audio system.
[ONE Original Android Development] linuxxp:
Snapdragon Camera app is with default settings. I changed only flash mode settings.

Now I make a few photos with flash but they haven't this issue. Maybe problem persist only in sunny photos. Tomorrow I will make some tests.
[ONE Original Android Development] Deadclysm:
The quality of the photo is awesome though! I just hope the double exposure thing could be fixed.
[ONE Original Android Development] AbhishekS:
Does anyone use Instagram?

Instagram isn't saving the pics in my phone anymore. It just shares the pic on the server, but doesn't save a copy of it in the phone.

The option to 'Save original pictures' is on since ages on my phone. This happens only on SultanXDA's ROM, and that too has started happening since the last few builds, I guess since the 17-Oct build or the one before that.

---------- Post added at 02:06 AM ---------- Previous post was at 02:06 AM ----------

And it persists in the latest build too.

I have tried everything. Clearing cache, reinstalling app, etc.
[ONE Original Android Development] Deadclysm:
Not true. It's not ROM related but the one of the latest Instagram version 'causes that. I guess works as intended.

Please note that I'm not using this ROM at the moment, I'm actually using "Minimal OS" at the moment and it's the exact same behaving.
[ONE Original Android Development] AbhishekS:
I tried old versions of Instagram and they don't save pictures either. On the other hand, I tried the stock COS12.1 ROM with the latest Insta version and everything works fine.
[ONE Original Android Development] BitEE:
No guys, instagram pics don't get saved on a friend's nexus 5 running stock marshmallow. It's not a rom issue.
[ONE Original Android Development] AbhishekS:
Are you sure the option to Save Original Pictures is enabled?

I can save the images on COS12.1 but not on this ROM. :S
[ONE Original Android Development] Sultanxda:
I never touched Bluetooth, and I don't have a Mercedes to test with (I drive a twenty-year-old Volvo). The only Bluetooth peripheral at my house is my dad's car, but it's old and doesn't support music over Bluetooth, so I have no way of testing this.

EDIT: Nevermind, Bluetooth is handled by the WiFi driver which I have played with quite a bit.

EDIT2: Nevermind again, Bluetooth is not handled by the WiFi driver, so my original statement stands (I've never modified Bluetooth).
[ONE Original Android Development] takkischitt:
I drive a Mercedes. What is the issue you're having with the audio and I'll see if it's happening for me?
[ONE Original Android Development] raul.lopez1958:
[MENTION=4800121]Sultanxda[/MENTION] Good evening,

a question ... who are the owners fingerprint reader and laser autofocus OnePlus two?

Because as I have understood OnePlus can not release them to developments cyanogenmod.

Cheers
[ONE Original Android Development] idonttakedrugs:
Can i dirty flash from 17th to 25th? I've never dirty flashed before but im fed up with always wiping the phone when theres an update. I understand there could be bugs and that after but how often is that? everyone dirty flashes on stock roms when a OTA comes dont they?
[ONE Original Android Development] scedeov:
yo guys. Is it worth to update my phone from 17/10 to 25/10? I ask this 'cause I'm not experiencing any of the issues shown in the changelog and I'm happy with the WiFi performance. Should I dirty flash the newest version or should I wait until the changes made are more significant? I've always had this question, for me it takes so much time to download a new version every time (my internet is sucks) so I need guidance :(
[ONE Original Android Development] ygoralmeida:
idonttakedrugs

Yeah, i did this right now and working fine. had no problem to update from 17/10 to 25/10 build ... OTA downloaded and flashed over and still working.

Only had to re-flash the xposed proper framework.

You should try
[ONE Original Android Development] dorian1326:
Just updated via OTA to 10/25 rom and got a random reboot after a few hours. [MENTION=4800121]Sultanxda[/MENTION] here is the log: https://drive.google.com/open?id=0B042GWqpSnZUMTBwSmotNXZaZkE Hope it helps!
[ONE Original Android Development] eduardobarth:
[MENTION=4800121]Sultanxda[/MENTION], I have something like a bug to report. I'm not fluent with english, so I recorded my screen in order to help you understand what I'm trying to report.

https://youtu.be/YitU3ZGFfgg

Well, I have changed the contrast from default (5) to 4. It can be seen in the first seconds of the video. At 13 seconds, the image is showing the saturation I got right after changing the setting. After I made the first shot, despite subtle, it's easy to see that the contrast has automatically changed. If you can't notice that on the video running, pause it at 13, then jump to 17secs. The difference gets more clearer.

I don't know why it happens, nor if there's a specific condition in order to reproduce that, but it's recorded. Hope it helps someway.

[MENTION=309187]edit[/MENTION]: Sorry for the orange window, but I'm not used with screen recorder apps, just downloaded the first one that showed up at Play Store!
[ONE Original Android Development] Sultanxda:
Are you using a different kernel? Your WiFi basically exploded... Disconnected 35 times over a course of 8 minutes :eek:

The contrast didn't change; the exposure changed. You tapped on a certain area of the screen to focus it for the first picture, so you manually changed the exposure.

There is no bug.
[ONE Original Android Development] eduardobarth:
It's just that to achieve the same image of the first shot, I need to change the contrast to something else than 4 and get back to 4. It I don't, no matter where I focus, I'm not able to get the same image of the first shot. Perhaps it can be a problem only with me, just wanted to share. Thanks!
[ONE Original Android Development] warlynx:
When I clean flash this ROM, it gets stuck at boot logo. I don't know why. My firmware is updated (even tried downgrading the firmware) but still doesn't work.
[ONE Original Android Development] renaltosonylevi:
What recovery are you using?
[ONE Original Android Development] warlynx:
i'm using twrp 2.8.6.0
[ONE Original Android Development] renaltosonylevi:
Recovery should be no issue. Try flashing the latest official cm12.1 nightly first to straighten out your firmware. Then whipe and flash the ROM only. Then again you could have a bad download.

Gapps and supersu can be flashed later. When in doubt do it one step at a time.
[ONE Original Android Development] rockingondrums:
Dirty flashing is a bit of a misnomer... Or I guess slang. Read the 2nd and 3rd paragraph of this: www.cyanogenmod.org/blog/all-about-l-part-2

Generally, it shouldn't be necessary to wipe unless specifically stated.

Backing up is never a bad idea, however.
[ONE Original Android Development] warlynx:
I already have done all that.and it's still stuck at boot. This happens on Euphoria CAF also. So i guess it's a problem related to CAF builds? It works fine on cm12.1 nightly and other roms though.
[ONE Original Android Development] DeeFolt:
Thanks for the great rom. However, iam experiencing i do not know if its major bug or what but i have a xiaomi Piston 3 earphones and i can't seem to have them work with your rom. from the first build i flashed the buttons are not working then updated to the latest build button works but the Vol+ and Vol- have the same function "they both reduce the volume". haven't tried the mic yet but hopefully it will work. kindly fix this. Thanks
[ONE Original Android Development] jaymact:
does this rom has traffic monitor in status bar?
[ONE Original Android Development] mjulio:
Do you use PowerNap?. Happened the same to me, powernap was the issue

Enviado desde mi OnePlus One
[ONE Original Android Development] j1po:
No traffic monitor in statusbar
[ONE Original Android Development] Murphy7523:
Thank you for the 10/25 Rom. For the first time this OPO is running well. The modem is not running fast; but it is not skipping and fouling either. Camera is great. Cheers.
[ONE Original Android Development] kuulbhaskar:
you can use xposed module like network speed indicator for up down traffic status !!
[ONE Original Android Development] resporival:
On YouTube full screen, battery indicator and network speed indicaor not disappearing..
[ONE Original Android Development] mlord:
Wifi Analyzer not working on this ROM.

Looks like a nice and solid ROM.

Love the Camera and features!

But one important app not working on it: WiFi Analyzer.

https://play.google.com/store/apps/details?id=com.farproc.wifi.analyzer

It runs, but never finds any Wifi APs, not even the one the phone is connected to.

EDIT:

Others (below) confirmed that the app does indeed work fine, so I wiped cache/dalvik, uninstalled the app, then reinstalled it, and now it works here too.

Android is strange that such measures are often needed, but that's just the way it goes.

Thanks.
[ONE Original Android Development] move_some:
Just installed and tested the APP.

Works for me.
[ONE Original Android Development] danportu:
Wifianalyzer works for me too
[ONE Original Android Development] KiD3991:
[MENTION=4800121]Sultanxda[/MENTION] Finally using this. Not bad I'd say. Was still pondering. Kinda hard for me to get used to this phone. Wanted to use hardware buttons but I am too used to AOSP style navigation(been using since Nexus4?) button. Battery life so far is not bad, nothing to complain really, still figuring I can further modify this device. Such as s2s and more. And I am guessing on OPO, the tap screen to wake, the screen is powered on 24/7 which is a power consuming option, unlike M8 that uses the gyrometer to sense if the device is being moved. Sound quality is superb though. And trying to compare performance mode and balanced. Both seem to consume more or less the same power but performance is snappy.
[ONE Original Android Development] mlord:
Thanks. I will fiddle with it some more now -- completely wipe/reinstall and try other stuff.

Thanks.
[ONE Original Android Development] jiznon:
There is definitely some sort of Wifi issue persisting through to STABLE 1025. Every now and then my Wifi will drop to a crawl - ~0.16Mbps. Just disabled Bluetooth and the speed immediately shot up to ~36.00Mbps.

Keeping Bluetooth disabled isn't an option as I own a Android Wear device. Any suggestions? Can I help out somehow?

Thanks.
[ONE Original Android Development] mlord:
If you control the AP, then see if it has a setting for "Bluetooth Coexistance" and try that.
[ONE Original Android Development] tigobrata:
[MENTION=4800121]Sultanxda[/MENTION] i have a real problem here, can you by any change make a kernel image with usb debugging enabled?
[ONE Original Android Development] jiznon:
Thanks for the suggestion. The AP is a Comcast provided Cisco XB3 that doesn't seem to have such a setting. Do you this that's the issue? I have an old WRT I could set up between it.
[ONE Original Android Development] mlord:
Dunno if that's worthwhile. Instead, maybe you can change the channel the AP is using. With a bit of luck it'll clash less with the bluetooth on another channel.
[ONE Original Android Development] bundysoat:
Sorry, I love this ROM buddies, but the camera modes in Slow obturation mode, not works. Only works CM camera and the modded CM camera.

Can you implemented in next versions the modifications to will use the mods of all apps of cameras that as high as 2 seconds of obturation or more?.
[ONE Original Android Development] jiznon:
Thank you, I'll play around with that.

**EDIT: Just did some research - didn't realize Bluetooth was a 2.4GHz freq. Make senses now, but odd that I've only just noticed it the past few weeks.

Did some testing:

Connected to 2.4GHz, bluetooth ON: abysmal speeds.

Connected to 2.4GHz, bluetooth OFF: normal speeds.

Connected to 5GHz, blueooth ON: normal speeds.

Connected to 5GHz, bluetooth OFF: normal speeds.

I suppose its not the ROM. Apologies for getting this thread off topic.
[ONE Original Android Development] PhysX1024:
Im thinking to instal this ROM... but I have a question first...

This ROM has problems with WhatsApp voice note, it record with quality...or is the same CM 12.1S it record like with mono 16k...and sound very bad....still has the problem?
[ONE Original Android Development] thenessus:
I had the same worries as you (I had nexus 4 and nexus 5). Unlike those devices, DT2W has zero (or at least 0.01%) battery life impact.
[ONE Original Android Development] zBear:
I had the same thoughts about this feature, so I tried to disable this option for a few days and then I enabled it back

no difference was noted
[ONE Original Android Development] seco007:
I tried to install this OS and I ran into some issues. I booted into recovery TWRP 2.8.6.0, wiped /data and /system (as per instructions ), then installed ROM and the TK GAPS, when my phone reboots its stuck in an endless loop, andriod screen plus the OPO plus logo, 3 second loop, then repeats....any help would be greatly appreciated. And yes I have read through countless pages in this thread...most issues are had when OS is already running not before...
[ONE Original Android Development] mikecantreed:
Clean flash the latest official CM nightly first then clean flash this ROM.
[ONE Original Android Development] rockingondrums:
[MENTION=6005499]jiznon[/MENTION] Not off topic, I've noticed some very slow speeds recently as well. Also using the rip off Comcast rental. You might have helped me. Of course, I was looking at modems and routers on amazon, but this will be better since I'm waiting on a 6P charge. It's amazing how much more broadband modems cost. Last time I bought a modem, 56k was the hot thing. Now that's how you go OT.
[ONE Original Android Development] danportu:
About wifi and bluetooth issues..

https://jira.cyanogenmod.org/browse/BACON-1073

But if sultan could check it...
[ONE Original Android Development] ming3r:
Slow speeds you say?

I've got the archer c6 that was 65 bucks on amazon with ac speeds. Not much of a difference from n but I didn't use wireless much other than my phone.
[ONE Original Android Development] jiznon:
That screenshot adds nothing to the conversation unless you can confirm to us that you:

1) Had bluetooth enabled.

2) Were connected to a 2.4GHz wifi network.

---------- Post added at 06:13 PM ---------- Previous post was at 06:07 PM ----------

Thanks! Added a comment to that with my findings.
[ONE Original Android Development] seco007:
I just did the following:

Reboot to recovery TWRP 2.8.6.0:

- Wipe / data and / system..nothing else

- Install latest nightly (Oct 25, 2015)

- Without rebooting..install this ROM ...

- Then GAPS

endless loop.....android screen with OPO logo...every 8 seconds...restart...

back to recovery ...

wipe (see above....)

install latest nightly and then this rom.....

NO GAPS...

endless loop again...

the only way to "get into my OS is to restore to previous SEPTEMBER 12, 2015 back up with cm-12.0-YNG1TAS2I3-bacon-signed

...

Any help?

I have no idea why it is looping!!!!

NOTE: I get no messages while doing any of the steps above....so I cant catch my mistake...
[ONE Original Android Development] david72262:
Wipe after the nightly
[ONE Original Android Development] dorian1326:
Nope! I use your stock kernel. If it helps, I was sending a coupe MMS while multitasking with another online messaging app I believe. I remember I switched back to the MMS window and it just got stuck for 2 seconds and then rebooted. I also flashed your "disable CPU underclock" zip this time and supersu.
[ONE Original Android Development] seco007:
So I did the following:

1) Wipe

2) Nightly

3) Wipe like david said (see above) by the wipe = /data and / system

4)flash this rom....

5) loop.....loop.....

Any other ideas......what causes a loop? is it not "finding" the OS.????
[ONE Original Android Development] SubNoizey:
[MENTION=4800121]Sultanxda[/MENTION]

This has been my phone for some time now, the build on the 11th with your network change seemed to slightly fix it as it would stick on all the time and then you reverted it and it's happening again. Every other phone in my house is fine, it's just my two OPO's with your build on it.

I'm within 500m range of two cell towers so I don't understand why it continues to drop.

Is there any testing or anything I can supply to help you maybe identify if this is a bug?

Edit: So i entered *#0011# into my dialer and it's now connecting at -95 dBm 46 asu to -98 dBm 44 asu. This is so confusing! The signal is now extremely stable and isn't dropping out.
[ONE Original Android Development] mjulio:
Check the download is correct...

Enviado desde mi OnePlus One
[ONE Original Android Development] stevekind:
Things you could also try:

1) Redownload ROM, maybe using a different browser. Compare checksums.

2) Also wipe caches (dalvik cache + cache)

3) Take a logcat of ur bootloop and post it here; maybe someone here is able to help. You can follow this thread, if not shure how to do it: http://xdaforums.com/showthread.php?t=2274119

Good luck!
[ONE Original Android Development] seco007:
[MENTION=2318303]stevekind[/MENTION]

1) I downloaded the past ROM found here:

https://www.androidfilehost.com/?fid=24052804347839445

2)wiped cache and dalvik

3)I have no idea how to post logcat...I read through the link but focused my attention on installing a working ROM, I tried the nightly that was recomended here (First page of OP):

If you get an error when trying to install (TZ version error), then download and flash the latest official CM12.1 nightly. Then, without rebooting from recovery, flash my ROM. This process is necessary to update various firmware (including TrustZone), as the updated firmware is needed by my ROM. After flashing my ROM, flash a Google apps package, and then reboot.

4) Flashed GAPPS...

5) booting normal..works fine BUT I couldn't make this particular ROM work...I really wanted to try out the CODE AURORA FORUM (CAF) 3.4.0

6) I don't know what firmware is causing my system to crash...I don't know if I should attempt a FULL SYSTEM swipe...( I have a back up created via TWRP that works well...my failsafe's failsafe and I don't want to delete it...even though I believe it is saved on a different partition.
[ONE Original Android Development] 69gm:
I don't think you followed the instructions correctly. From the OP:

Follow the instructions VERBATIM and see if you still have problems...
[ONE Original Android Development] stevekind:
Just to be shure:

ad 1) This is Sultan's ROM 10/17 (outdated version; latest is 10/25). This is not the official CM nightly. Still, sometimes downloads get broken.

ad 2) I meant wipe system, data, dalvik cache and cache all together

ad 3) To read is to learn; never a waste if time. Anyway, are you getting any errors, or is all flashing fine?

ad 5) exactly what is booting normal? The Nightly? What nightly did you use?

ad 6) your personal files (incl. fotos and nandroids) are saved in /data/media; it is NOT getting wiped while wiping /data. Still a backup in a safe place (PC etc.) is never a bad idea.
[ONE Original Android Development] seco007:
1) One

[/IMG]

2)Two

[/IMG]

3)No issues so far....nightly clean install

[/IMG]

4)Sultan Rom (notice two versions..tried both)

[/IMG]

5)GAPPS

[/IMG]

6)No issues with GAPPS (no red warning signs)

[/IMG]

7)Final Step...no issues so far....

[/IMG]

LOOP........I cannot seem to get past the ANDROID screen startup.....
[ONE Original Android Development] phillibl:
Try a full wipe for a clean install.
[ONE Original Android Development] seco007:
Thanks, tried it a couple of hours ago..wipe is /data , / cache / dalvik / and /system....I started doing that BEFORE every OS install....no luck...see my posts above (four posts above...or five...)
[ONE Original Android Development] phillibl:
Sorry I didn't see that. Try a couple more things separately and see if they work. Do not use the built in root for these. Also, download the latest gapps yours is very outdated.

1. Clean flash only CM12.1 and boot

2. Clean flash only Sultan's rom and boot

3. Clean flash Sultan's rom and the latest gapps and boot
[ONE Original Android Development] seco007:
1) you mean the latest nightly yes?? not the stock CM 12.1...just want to make sure...not this stock one?

https://www.androidfilehost.com/?fid=24052804347802352

2) I didn't boot after Sultan's rom cause in the OP its says WITHOUT REBOOTING FROM RECOVERY (sorry about the caps...had to make it stand out)...I clean flashed the latest nightly THEN without rebooting I installed Sultans rom....

3)I just saw the latest GAPPS , yeah mine should be updated...I will try this...
[ONE Original Android Development] phillibl:
Regarding #2 those are the steps if there is a 'tz' or trust zone error. Try just clean flashing Sultan's rom with no CM, gapps or root.
[ONE Original Android Development] seco007:
that was the very first thing I tried.....no luck...thanks for helping....I will try what you suggested above.
[ONE Original Android Development] renaltosonylevi:
At the final step are you installing supersu. Just wondering if you tried a marshmallow build and inadvertently updated your supersu script to 2.52. If that is the case reflash twrp.zip using twrp. BTW I use 2.8.6.0.6 and never had any issues.

Normally I always manually flash supersu 2.46 for lollipop.
[ONE Original Android Development] Sultanxda:
Headset button mappings have never been touched. Maybe your headset is breaking; I have the same issue with a headset I have, and the problem existed when I tested my headset using 3 different devices (so my headset is the one that is broken).

Could you reboot to TWRP and grab a last_kmsg (/proc/last_kmsg)?

No, I cannot implement this.

Bluetooth and WiFi are processed by the same chip on the device.

DT2W for the OPO is processed by the touchscreen hardware, not by software, hence why it doesn't kill the battery.

It'll probably be fixed in the next build.

Have you successfully used any of the CAF ROMs?
[ONE Original Android Development] DeeFolt:
I didn't have a problem with Mokee Rom and i think its not an issue with my headset for it is new.

EDIT: It's fine now. Flashed AK Kernel CAF, wiped cache and tried the buttons all works perfect.
[ONE Original Android Development] fgaurano:
Are you installing Xposed?
[ONE Original Android Development] seco007:
?? What is that? I am trying to install Sultan's rom...the one at the first age of this thread....

Unofficial CyanogenMod 12.1 with CAF 3.4.0 kernel [Oct. 25, 2015]
[ONE Original Android Development] DeeFolt:
Hey, i saw you in OPFC forum?
[ONE Original Android Development] g-oleg:
2 seco007

Check that ur /cache has ext4 fs.

Отправлено с моего A0001 через Tapatalk
[ONE Original Android Development] fgaurano:
Is that you? Hahaha.

Oh, I thought you installed it. I can't really explain what it is, but you can learn more here.
[ONE Original Android Development] sToRm1nG:
Can you try to manually flash the firmware?

You need to have Android Platform Tools (adb and fastboot).

Download this file: CM12.1 .3.0.c6-00241 Firmware.zip

Extract it, put your OnePlus One into fastboot mode and run FlashFirmware.bat.

This should flash the latest CM12.1 nightly firmware.
[ONE Original Android Development] DeeFolt:
Its meeehhh! Ye.