yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] kallest1100:
Really su I need for some Apps, and because, unfortunately, even does not clap behind flashen, I cannot begin the Apps any more.

boeffla Kernel I must not have, but he is practical to save from accumulator achievement.
[ONE Android Development] jgcaap:
Flash SuperSU zip . I have SuperSU access...
[ONE Android Development] jgcaap:
Decided to stop the build to try out a change in order to see if it fixes some of the camera bugs... 2 hours and 30 min and is up.
[ONE Android Development] fgnm:
Unfortunately this is the only thing I was able to find: http://review.cyanogenmod.org/#/q/topic:find7-lollipop-cam

I'm sure that they have done many other commits on android_kernel_oneplus_msm8974 and android_device_oneplus_bacon

on same topic because I remember I read many other interesting code about this, but now disappeared (or I'm not able to remember exactly the name).. Unfortunately none of these commits were merged on github
[ONE Android Development] JeromeLeung:
Been using your ROMs for the better part of a year. Had my original bamboo swap cover OPO stolen a while back so I bought a new OPO and the first thing I did was flash your ROM :p Thanks for everything!

6TC875848J990452H
[ONE Android Development] jgcaap:
http://review.cyanogenmod.org/#/c/108484/

Check Michael Bestas reply to my question... This wasn't for oneplus one.
[ONE Android Development] jgcaap:
You are amazing!!! thank you so much man. :) I was worried i didn't had enought until i receive the unemployment fund, i think it'll help out great.! Thanks!
[ONE Android Development] fgnm:
Right , that's why I say that they've done other things :p disappeared all commits about camera blobs I remember exactly 'import find7 camera blobs' BTW I think I couldn't help you more :(

EDIT:

Anyway I've tested a bit this new driver and camera performance are significantly better. RAW instead (at least with my algo) are not so good since driver still has some bug (If don't ask too much please try to enable the reading of current camera state from driver, so real time current focus status or whitebalance, already available on stock hal). I was wrong instead on full manual focus it works well too :)
[ONE Android Development] kallest1100:
If I have made already 2 times, does not clap.

Then I have no Root.
[ONE Android Development] jgcaap:
Who else has here problems with root?
[ONE Android Development] AcmE85:
I had missing root once when I was switching from stock cm13 to your build via dirty flash

(test build with color os blobs with additional kernel flash).

After flashing the following build (05/03), root was back and working and is working fine on each build since then,

including today's.

edit: I'm on TWRP 2.8.6.0.6 materialised and ext4 filesystem

[MENTION=6215602]fgnm[/MENTION]

Are you talking about your bacon camera?

Raw and manual focus working on this rom?
[ONE Android Development] Miksel12:
I always flash SU seperate because it never worked without flashing seperate.
[ONE Android Development] fgnm:
Just RAW, as dev words camera here still needs some work
[ONE Android Development] ari2asem:
i am also having problems with error executing updater binary in zip /tmp/mr_update.zip . i firstly updated the firmware to 01022016-version without any problem or error. i pass the TZ-zone check during the installation of this in multirom (comparing TZ version TZ.BF.2.0.2.0.0123 to TZ.BF.2.0.2.0.0123 , but i get this error executing updater script in update.zip

i am trying to install this ROM via multirom as secondary rom. my primary rom is SlimSaber by fusionjack (build date 16 aug 2015), with stock kernel of SlimSaber-rom. i am also using TWRP 2.8.6.0.

oh, yeah.....all my partitions are ext4-file system, i dont use any f2fs....could this be the reason for my error?
[ONE Android Development] jgcaap:
Flash the firmware which is on the server, reboot recovery and flash rom ;)
[ONE Android Development] ari2asem:
if u mean this server http://download.jgcaap.xyz/files/oneplusone/firmware/, then i did it already. but if u mean another server then i need the adres of the server.

or should i first install the kernel??
[ONE Android Development] kimikim0:
the new build 5/5 include the merge lockscreen fix ?
[ONE Android Development] JeromeLeung:
That's the right firmware. Which recovery are you using? There was a known bug with TWRP 2.8.7.0 where it wasn't able to update firmware.
[ONE Android Development] AcmE85:
No, I just downloaded and flashed it.
[ONE Android Development] ari2asem:
i use twrp 2.8.6. i am aware of the bug in twrp 2.8.7, twrp 287 cann't update the firmware. i knew this. i used twrp 286 to update the firmware without any error. so the firmware is not the cause of my execution-error in multirom. even updateing the multirom to version 33b didn't help
[ONE Android Development] psycholyzern:
Can I know why you guys didnt use twrp 3?

I never had problem with it. I'm using tugapower's twrp.

https://www.androidfilehost.com/?fid=24533103863137089
[ONE Android Development] Purerawenergy:
Dude, just flash this RECOVERY and you'll be fine as quoted above.

https://www.dropbox.com/sh/rfg1l0yk4emaeov/AACEBVTGww0KkIiPSwMbqCoLa?dl=0

---------- Post added at 05:04 AM ---------- Previous post was at 04:14 AM ----------

Listen guys, I can't afford to make donations on my measly monthly salary but I definitely can't afford NOT having [MENTION=2040569]jgcaap[/MENTION]'s roms on my device. Please show your appreciation and donate a little something to help him out and keep your karma good. Thanks and thank you Jorge, it's been a great ride with you so from lollipop and I can't wait until 7.0 arrives. lol

Here's a little something to tide you over until better times my friend.

2M696926GP449250W
[ONE Android Development] aqilsoomro:
I am using kernel auditor with stock kernel, do I have to flash UKM.Newkernel.zip with every dirty flash? Or doing it once is enough it would stick to each subsequent dirty flash??
[ONE Android Development] Setting.Out:
Ukm is for synapse only, it has no use with kernel adiutor.
[ONE Android Development] artturipa:
Thanks for this ROM Jorge, just made a little donation for you! Keep up the good work man, my two years old OPO is still like a new one :D:good: 00M21872A97248908
[ONE Android Development] jgcaap:
very big thanks man :)

You guys are life saviors!
[ONE Android Development] nchantmnt:
Sorry i didnt get it: if i want coloros test Version without notification bug i need to flash 21/4 then boot and then dirtyflash coloros.ZIP right?

Or do the newer zips have this issue no matter what?

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] Setting.Out:
For me, I dirty flash over the 22nd build I have backed up.. Though keep in mind these are first builds with the camera blobs and are being improved..

Anyone needing a daily driver please stay on earlier builds (pre 23/4) until we test it as "stable".. ;)
[ONE Android Development] tacohell:
+1. I also do the same (flash supersu when flashing the rom and I also install the app from the store) as it never works otherwise.
[ONE Android Development] nachomagic:
Same for me, always flash supersu manually

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] Purerawenergy:
I keep SuperSU 2.67 in my download folder just in case but aren't you all opening SuperSU and getting the prompt to install the script to survive flashes? That's the first app I open after flashing and install that script rather than updating through Play Store and have ZERO problems.

And I'm saving my money now for the OP3. I want the 64 gig, 6 gigs of ram, which will probably cost what the OPO cost, since the 32 gig, 4 gig RAM is roughly $310.

I know that Zuk 2 looks awesome (@Setting.Out) but this one is a beast!

http://www.xda-developers.com/onepl...o-versions-base-version-to-cost-cny-1999-310/
[ONE Android Development] teXew:
Today i clean flash build 05(i try 04 and build 23.04 too). On all bulds i couldn't pull Quick Settings tray down. Any soulution?.

IMG: https://www.dropbox.com/s/d3w5awp38g39b9g/Screenshot_20160506-180130.png?dl=0

btw i cant find coloros camera app in build 05 :) tnx
[ONE Android Development] jgcaap:
Clean flash 21st April , boot, go to recovery and dirtyflash to latest to solve the quicksettings bug.
[ONE Android Development] jgcaap:
need a vs. with the new rom coloros.zip please. Let me know about camera quality if improved.
[ONE Android Development] coloured_chalk:
I will create versus photos tomorrow for you (and for community)
[ONE Android Development] payne_307:
Planning to try your ROM. Question to you or any member of the forum is -

1.) Do I need to clean flash 21st build first and then dirty flash the Color OS zip or if I clean flash only the Color OS zip it wouldn't make a difference?

2.) For future updates do I have to flash the kernel from the Colos OS zip, as I assume the kernel on the regular builds will be different than the Color OS build?

Thanks
[ONE Android Development] jgcaap:
Just this time you need to flash 21st and later the rom you want to update to because of cm.

About the camera you have coloros which us already present on the latest rom, on the test folder you have again color os but with different setting.

You don't need to flash kernel already included.
[ONE Android Development] kimikim0:
hey boss, just wondering the latest build include lockscreen fix ? saw in changelog say it include but still there the bug , tq
[ONE Android Development] stryker09:
Besides the 180 flip on FF camera, latest test seems better.
[ONE Android Development] fards:
Interesting, i presumed you weren't using colouros blobs in the normal build as the 50mp isn't working for me.
[ONE Android Development] GasLoop:
[MENTION=2040569]jgcaap[/MENTION] still waiting for your comment on xprivacy :D
[ONE Android Development] ari2asem:
the problem with ERROR EXECUTING UPDATER SCRIPT solved by updateing twrp multirom from 2.8.6 to 3.0.2 version. i used the original twrp multirom
[ONE Android Development] jgcaap:
One step at a time. There are still bugs to fix. There is already two members of exodus helping me out on finding proper fixes. Already comment about this :)
[ONE Android Development] jgcaap:
What would you like to know?
[ONE Android Development] jgcaap:
Sorry... What you Want to know?
[ONE Android Development] AcmE85:
I can't tell if the camera is better with the recent coloros build, it is definitely not worse.

Color accuracy is really good, with enough contrast and vibrant colors.

I did a comparison with a friend's Sony z3 compact on Friday and the opo photos were more true to life.

Even my friend agreed that he prefers the opo camera results.

Though I have to say that the z3 produced a bit sharper images with a little more detail on distant objects (13 vs 20mp I guess).
[ONE Android Development] Yaznas:
Should i just flash the latest n is it stable enough for a daily driver?
[ONE Android Development] Gawd:
Can anyone just install this App and let me know the readings (a screenshot would be appreciated) --> https://play.google.com/store/apps/details?id=com.acorilhas.opochargingcurrent

I'm just trying to figure out if the problem is with my adapter/cable/ROM/Kernel or is it just normal. But, I feel slow charging. I'm running CM13 by jgcaap (This ROM is so smooth, thanks jgcaap) with Boeffla kernel v5.1-beta20 (makes it more fluid, thanks Lord Boeffla)

I'm also attaching my screenshot. I'm currently using a Samsung charger and Samsung Cable, because the original adapter from OnePlus just started behaving abnormally(like it would charge really slowly, would take 10h+), I still don't know why. I tried all pairs, OnePlus Adapter + OnePlus Cable, OnePlus Adapter + Samsung Cable, Samsung adapter + Samsung cable and Samsung Adapter + OnePlus Cable. The Samsung combination turned out to be the best. And this happened like 7 months ago. This Samsung combination was just working alright, but now it's kinda slow charging. I'm also attaching a picture of Samsung Adapter (its 5V @ 2A) and cable. So please help me figure out the problem.

Thank you for reading and spending your time on this. Any suggestion would be appreciated.
[ONE Android Development] coloured_chalk:
Sorry, doubled.

Link on post for photo comparison:

http://xdaforums.com/showpost.php?p=66739583&postcount=14860
[ONE Android Development] bubaxda:
Hi, I've only dirty flashed May the 6th build and the slow shutter option seems to work bad, tried 2 seconds and took a darken photo and I was expecting the opposite. Would be nice to get back the 64 seconds option like it used to be.

Would you like me to try the coloros. zip on top of it and report?
[ONE Android Development] coloured_chalk:
Camera comparison

Here it is. cc [MENTION=2040569]jgcaap[/MENTION]

Russian post as well, if you can understand RU: http://4pda.ru/forum/index.php?s=&showtopic=605247&view=findpost&p=49440784. Same information in 4pda and there.

I created diff for following roms and apps:

cameranextmodded on build 21 april

snapcam on build 21 april

snapcam on build 6 may

snapcam on build colorostest (from "test" directory on your download server)

I maked photos in same day, same objects and semi-same conditions. Today was cloudy a bit.

Source

All sources are on yandex disk (RU analog of dropbox): https://yadi.sk/d/I5eE0JcirYj97

You can see on cloud storage: photo sources, exif for second photo (toy outdoors), comparison images, camera params for every build (list in beginning of post)

Here comes the body!

Photo comparison

(I didn't scaled photos - just cropped 'em. I recommend to download source comparison files on yandex disk, since imgur may compress images... and compare for yourself, focusing on some points with zoom):

Link on imgur album: http://imgur.com/a/lM89X

(I can't attach those files on xda - Err Entity too large, but imgur plays well here)

Exif difference

for second photo, on "snapcam 21 april" and "snapcam 6 may": https://www.diffchecker.com/kzw8kvuu

As you can see, we don't have some tags on 6 may build: F Number, Light Value, Aperture.

Camera parameters difference

every is on snapcam (it dumps parameters in logcat):

21 april vs 6 may:https://www.diffchecker.com/izanywuh

21 april vs colorostest: https://www.diffchecker.com/qboiqmw1

6 may vs colorostest: https://www.diffchecker.com/icylo32k

I can see strange proprietary parameters like oppo-app=0, oppo-eis-enable=0, video-hsr=off (hsr param is only on coloros),but I can say nothing for this. May be this information will be interesting for tech people, like ROM maintainer. Source files are on yandex disk.

SUMMARY

The best quality was on cameranextmodded on 21 april and snapcam on 6 may. YES, I can see the difference even in snapcam (IMHO, it's still captures crappy photos and ported Colos OS camera and Cameranextmodded are still the best options [as well as Camera-FV5 for RAW capture] ).

So - yes, quality seems to be improved. But some bugs like missing exif tags... :(

This is all guys! :highfive:
[ONE Android Development] jgcaap:
Great contribution. I didnt had time for this, it seems that on image quality the colorostest (lets call this test 2) seems to be producing the best results when compared to coloros from 6th May on stable folder.

Very well lets see how we'll go from here on.

Big thanks :)
[ONE Android Development] payne_307:
Thanks a lot for the useful post. But I think you missed the most effective app for Colos OS blobs, which is the Oppo Camera. I wouldn't even attempt taking a picture using snap camera since no matter the blobs or the conditions, it manages to get the worst focus, worst depth of field and worst color accuracy. Though you have mentioned Oppo camera in in your summary, it would have had been good to include the pictures taken via Oppo camera as well. I somehow see Color OS test producing better pics than May 6th build as well.

[MENTION=2040569]jgcaap[/MENTION] - What do you recommend ? Color OS test or May 6th build. Though I want good camera quality I also would want to have a stable daily driver and the ability to upgrade via dirty flash.
[ONE Android Development] jgcaap:
Fixing lockscreen bug. Thanks to the help of : [MENTION=4817632]varund7726[/MENTION]
[ONE Android Development] jgcaap:
Well there is a new camera combination coming :) try both
[ONE Android Development] payne_307:
Ok. I will wait for new build to be up. In the meanwhile I will extract the dialer, vpice wakeup, camera next and gallery from COS13. I will be adding these when I flash your zip :p
[ONE Android Development] AcmE85:
Another thing that needs work is HDR.

Colors are pretty exaggerated.

No pressure though, just wanted to let you know.
[ONE Android Development] khnaveed:
Two annoying me most.

1) Phone Dialer needs to be tuned, whenever there is a call and another call comes, and if you put first call on hold/end to receive the second call, the phone always reboots. ! I am observing this behaviour since previous builds up to this build 6/5/2016.

2) Cannot make videos from the front camera.
[ONE Android Development] jgcaap:
on which version ?
[ONE Android Development] AcmE85:
Both. Right now I am on the coloros build.

Unfortunately I can't upload any pics as my connection is poor outside right now.
[ONE Android Development] jgcaap:
anyone was able to try the oxygen os camera blobs?
[ONE Android Development] pa1281:
Would it be fixed in the next build?
[ONE Android Development] lifelesslegend:
I'm on Sultan's CM13 build currently and here are the pictures I got: https://drive.google.com/folderview?id=0B2lLG0MNZMxdQU1SN1dGR0N2cXc

Not the best images as photography isn't my strong point.

I used CameraNextMod CM13, BOOTMGR ColorOS camera and the Snapdragon camera that comes with Sultan's CM13 rom. They are all labelled and each camera app has Ben tested with HDR on and Auto mode.
[ONE Android Development] payne_307:
Oxygen OS camera blobs produce the worst HDR pictures. Highly oversaturated. That's the primary reason for me to choose Color OS blobs. Can someone confirm if the HDR mode on this ROM using Color OS blobs is producing the same issue that is highly saturated colors? That might be a top priority vs 50 MP pictures or slow shutter etc
[ONE Android Development] MRJ1957:
Several builds ago accidently wiped one of my OP1's before flashing..... Lost all notifications. Looked for a setting or switch to turn on.... Wiped system and caches flashed firmware,rom and Gapps, nothing. Same wipe, flashed nightly CM13, then without reboot flashed ROM and GApps (Slim Mini) . . .Nothing. Searched (Googled and Local)..... found nothing. Just a flashaholic...... any help?
[ONE Android Development] AcmE85:
With and without HDR on the coloros build.

Has been the same on the previous builds with coloros blobs though:

Too saturated and often overexposed areas are not dimmed correctly

to make more details visible.

The color reproduction without HDR is spot on in this image!
[ONE Android Development] jgcaap:
There is alot of stuff we can do.

For my top priority to to remove the anoying line in the middle which some of us in some light conditions have..

Imagin this situation, cause this happened with me. You are taking a picture to record on your album with your gf or even with your coleagues or even family, and you guys come up with a line in the middle.

How happy would you be with it?

I wouldn't. Color OS blobs seem to be the right direction. The saturation is something which can be configured on the Camera app, also i'm understanding slowly how the wrapper works and it seems to be usefull to insert configurations of camera.

In other words, I believe we are on the right direction, but remember, this is a very slow job as I have to test, think and also ask for help as i don't know everything. Raja and Alex from exodus are at this moment working together to help on something to improve our quality. If we are able to pull it off, it'll be amazing for everyone. If not... Then i'll problably revert on blobs.

Only time will tell, until then enjoy the ride as I do this for fun and share with you guys . :)
[ONE Android Development] payne_307:
Exactly. Don't doubt your decision. This is the right direction. Will be laden with landmines but we are all with you. To all the people questioning this choice of blobs, I ask to name one CM based ROM for OPO which uses Color OS blobs? Jorge has done which no Dev in 2 years has done. And we have seen how well Color OS blobs perform on AOSP Omni based ROMs. So it's a wise decision. Give him time to iron out the issues. And I think over exposure and over saturation on color OS blobs is a bit nitpicking. It's just fine. It's 95-98% realistic and true to the subject captured. Need something better? Get a S7 or Nexus 6P. This is the best OPO can deliver overall (I say overall as some other blobs may shine in some but completely be stupid in other areas)
[ONE Android Development] ofer5813:
Hello all I'm on 27/04 th build and still having that soft reboot bug when switching between calls what I need to do?
[ONE Android Development] jgcaap:
update to the newest one..
[ONE Android Development] ofer5813:
Thx for the quick reply Jorge but the camera bug still present no?
[ONE Android Development] jgcaap:
what camera bug?
[ONE Android Development] ofer5813:
Idk anybody who updated to 04/05. Th build said there camera was broken?
[ONE Android Development] iRhyiku:
Camera works fine here on 05/06
[ONE Android Development] Cameldrugs:
still having the notification panel bug, even after I've installed the 21/04 build
[ONE Android Development] nchantmnt:
I've made this mistake as well ;)

You have to flash 21/4 & gapps, then boot and set up your Rom,

then reboot to recovery and dirtyflash newer build.

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] third40:
did a clean flash on 21/4 then dirty flashed latest.. camera crashes.. all others work.. but if i install a cam from play store it works!! default cam crashes.. :confused:
[ONE Android Development] :
So I'm derping or something, but I can't figure out how to install this ROM.

I'm coming from Sultan's.

I clean-flashed the 21st nightly, GApps, booted. Completed initial setup.

Booted to recovery, dirty-flashed the latest nightly, GApps, SuperSU, Xposed, V4A, my font zips, and a zip to change the DPI. Wiped cache + dalvik.

Booted into the system and I keep getting com.android.phone and Nfc Service FC messages. Can't progress beyond this stage.

I tried both v79 of Xposed (that's been working perfectly for me so far) as well as the v81 linked in this thread and its update script, and for V4A I'm using guitardedhero's zips. It's definitely either one of those - I believe Xposed is to blame.

So ... yeah. Anyone wanna help out a noob?
[ONE Android Development] Angelcho:
for the phone app I've solved a fc issue when I gave it all the permissions it asked for... and as for camera, are you sure you didn't flash anything that mods the camera HAL or anything connected to it. Since the latest couple of builds any camera mod breaks the camera driver and reflashing the rom fixes it. Can you provide a link to the zip of v4a you use?
[ONE Android Development] ofer5813:
So is there a camera crashes on latest build or not?
[ONE Android Development] AcmE85:
No. If you don't flash a custom kernel or camera mod,

the camera runs fine.
[ONE Android Development] GasLoop:
You said xprivacy would provide the privacy I'd want. So I'm eager to know why it shouldn't :)

Btw I used your rom for like five minutes as I wasn't able to pull down the notification bar. Do you know why?
[ONE Android Development] Bradl79:
its a known CM issue not specific rom issues, u have to clean flash 21/04 build and then dirty flash any of the newer ones and its fixed, also i think it breaks the camera, b/c mine is broken anytime i dirty flash, it may b/c i use opengapps idk, never got an answer.

edit: on the camera, i read back last page, i use Lightning Kernel and i guess that appears to break the camera
[ONE Android Development] Wisiwyg:
Camera works great on stock install. I also have the ColorOS Camera port (http://xdaforums.com/oneplus-one/themes-apps/coloros-camera-port-t3034148) installed alongside and they both work.
[ONE Android Development] Ejvyas:
So even if I'm coming from old March jgcaap I still have to install 4/21 before upgrading to latest?