yashsingh1/xdaforums huggingface dataset:
[ONE General] tofuboi01:
Has the ambient display wakelock been fixed in the recent nightlies?
[ONE General] Ok_Kaleidoscope5109:
Still, I think its worth discussing what changes you make when you post these builds. I have done my own personal builds too, and the ones I post up online are fully unadultered based on a full repo sync from the CM repos. The only change would be the lack of modem. If there's any cherry picks, I would post that in a separate thread and clearly let people know that.

Anyhow, the nightlies are working again, so I'd urge people to stick to those.
[ONE General] AcmE85:
Judging from the latest commits it should be fixed in tomorrow's nightly.
[ONE General] giaur:
I want to warn you: next nightly will introduce green ****ty screen color. They totally messed default screen color calibration. Dirty green crap instead of clean white as before.

Now I'm trying to soften that by changing rgb values, but without much success
[ONE General] :
I have the exact same problem with a 100% stock rom only (not a single app) after a fresh install, so yes, this is a ROM problem
[ONE General] faiz5200:
Wifi disconnect

Hi, why my wifi keep disconnect after 10-15min deep sleep? Every time I wake the phone, I didn't see the wifi icon but after a few second, wifi is connected back. This happen to all 5.1 rom. Already tried to go cm12s, wifi work fine. Is this common 5.1 bug?

Thanks.
[ONE General] emam damon:
hey guys.i have a problem.can you change the lockscreen wallpaper on 0712 nightly?
[ONE General] tiny4579:
Michael Mestas was complaining about it as well, assume it affects anything using this kernel. I wonder if its the dtb changes since the live display updates weren't merged.

Color is fine on 7/12 nightly at least. I think this will be fixed before tonight. I hope.
[ONE General] giaur:
I tried AK kernel and green tint is still there. So maybe it's not kernel related, but rather by their new "Live display driver"? I have already added comment for new LiveDisplay driver, but for now I'm very annoyed. Are they blind or what? I managed to get barely acceptable color using rgb white balance, but I'm still not satisfied with the result, it's not the same as it was before.

I don't think it will be fixed tommorow, because still there is no any commit in review for that.

P.S. If anybody want to test this new feature, I can share my build. Or simply wait for nex nightly (tommorow).
[ONE General] tiny4579:
I only see kernel commits that would impact it. See if ak merged any of those.

This was the suspicious commit.

http://review.cyanogenmod.org/#/c/102973/

I can't test until after work though.

Edit: After further review, it appears that all the color calibration code is part of the kernel and AK didn't add it to his latest kernel yet assuming the source on github is up to date.

I wonder if the calibrations by Steve were saved and that's why your color is still off. Try clearing app data for settings and settings provider and rebooting. It should reset the values without needing a clean wipe.
[ONE General] detted:
Quote:

Originally Posted by fmc000

Not a ROM problem, mine sleeps like a baby. Try to find which app is preventing your device from sleep (plenty of answers in this thread, actually, use the search function).

I have the exact same problem with a 100% stock rom only (not a single app) after a fresh install, so yes, this is a ROM problem

-----5-

Not a ROM related. Now on 07-04 and all before it. The battery has been descent. Yes sleep like a baby.
[ONE General] DarkBlack22:
Settings > Themes > lock wallpapers

Gimmi Dat :thumbup::thumbup::thumbup:
[ONE General] JamesRC:
I too have major battery drain. Just because you don't have the same problem doesn't mean it doesn't exist - we have different configurations and probably all have different definitions of battery life!

My battery drains 5-10% overnight, 5 in airplane mode, 10 otherwise. I think that's poor, much worse than cm11/cm12.
[ONE General] detted:
----------------

not at all. however the cause and effect is not established. If it is the rom, it would pervade to all 1+1.
[ONE General] giaur:
Hmm after clearing data it seems to be not so green, but color calibration seems to be still slightly different. Still more green.

---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------

So:

- ok after phone restart

- screen lock and unlock: green tint again

It's bug indeed. Can you confirm? I'm on stock kernel again

---------- Post added at 04:43 PM ---------- Previous post was at 03:59 PM ----------

This is new LiveDisplay driver bug, now I'm sure. DT is ok, but only after boot. Lock - unlock screen and calibration is totally messed (green color). It's enough to lock and unlock screen and difference is very noticeable. The same happens on guest account (so basically, the same as data wiped).

I suggest for all to don't install next nightly until it's fixed, if you don't want to finish with green display.
[ONE General] emam damon:
I know how to change lockscreen wallpaper. My point was I can't change lockscreen wallpaper, can you?
[ONE General] fmc000:
Thanks for the heads-up, much appreciated!
[ONE General] giaur:
From the other side, if you are brave, you can also install new nightly and confirm/not confirm this issue (make sure you have backup). But it seems they totally messed something with new LiveDisplay.

I'm going to create bug report, but I can't report bugs to nightly that does not exists yet :)
[ONE General] tiny4579:
It was merged after 7/12 nightly. Seems OK on the 7/12 nightly. Anyone able to confirm?
[ONE General] giaur:
7/12 should be ok, because my build from yestrday (10:20 CEST) is ok. And 7/12 nightly contains only 2 commits more:

http://review.cyanogenmod.org/102873

http://review.cyanogenmod.org/102874

and they are not related to display
[ONE General] fmc000:
7/12 rocks.

---------- Post added at 05:49 PM ---------- Previous post was at 05:41 PM ----------

It's not a question of being brave or not, in my job I am available (by phone) 24/7 - 365 days/year and the OPO is my only phone, so testing something I pretty much already know it's broken is out of question for me.

Well, I suspect that the comment you left in the SK commit is more that adequate and that it can be considered a very clear bug report! ;)
[ONE General] Pituky:
Brave.? Need my phone 24/7 to provide support, using Cyanodelta Im installing the updates every day... Rom 12.7 the best so far, better than the last official one.

Cyanodelta is great.

In case of any catastrophic failure it is quick to install some other rom.

Mine sleepsshhhhh like a bear in winter.

I will report any issue....
[ONE General] tiny4579:
If not then we get a jira nightlies ticket opened after the 7/13 nightly is out.
[ONE General] seco007:
So I tried this, and i also decided to do an FULL DATA SWIPE (figured why not start clean and fresh) and now I dont know how to use the ADB PUSH to send the NIGHTLIES files to my OPO. Any ideas....I downloaded the OPO V.6 toolkit from XDA...

http://inthiaano.com/oneplus-one-toolbox/

but when I click on ADB OPTIONS I get a command screen with:

[IMG="CMD"][/IMG]

How do I do this!!!! Pls any help is greatly appreciated

All I need is the actual commands to send the file...any one know...I have the nightlies here on my desktop:

C:\Users\Johndoe\Desktop\July 2015\Nightlies

---------- Post added at 07:47 PM ---------- Previous post was at 07:33 PM ----------

I forgot to add,..I have an OTG cable that works.. and i can boot to TWRP 2.8.6..so if there is a way to transfer files that way via TWRP recovery mode which I am also googling FYI)..I would appreciate it
[ONE General] shoaib30:
its quite simple. im not sure about the toolkit ur using. assuming ur on windows, open command prompt and cd to the location u have adb installed. u will have to find that. once there just type

adb push <local> <remote>

for example if your file is in C:/ drive and u want to copy it to the sdcard

adb push C:\file.txt /sdcard

to make it easier just copy the file to push into the same folder where adb.exe is so u just need to specify the name of the file to push eg:

adb push file.txt /sdcard

look up on google for more info theres alot of it available.

-------EDIT------

saw your edit about OTG. u just have to copy the files onto the drive and connect the pendrive (fat32 format) via OTG, do it before booting into TWRP, press mount u should be able to see USB OTG mounted there. go ahead to install and u should see a tab that says sdcard, click there and u can choose the location of the file. select OTG and find the file and flash directly.

incase u still want to copy the files to the phone. then in twrp press advance u have file manager there. u can find the files on the drive and copy them to the phone.

hope it helps
[ONE General] criminalzen:
cm 12.1 official original developent thread...

I am wondering where the original development thread is for cm 12.1 on bacon?
[ONE General] the Doctor:
There isn't one. The device is maintained by Cyanogen directly, not on XDA.
[ONE General] seco007:
[MENTION=4677798]shoaib30[/MENTION]:

So i tried googling it and found this VIDEO with the exact instructions and commands on how to use ADB files......

https://www.youtube.com/watch?v=NaK5OxUeDKM

I went through it and at minute 9.11 I realize that I CANNOT SEE MY DEVICE..so I think " Drivers must be not working......"

BUT I can hear the computer recognize it...and I hear the CHIME....ding!!! device found......

and I noticed that when I am on TWRP RECOVERY I have these drivers:

[IMG="drivers recovery"][/IMG]

While the phone is trying to boot into OS and I get the OPO logo....I get these drivers :

[IMG="other drivers"][/IMG]

So which is the right one,....and yes I tried installing the drivers that came with OPO tool kit but my computer (WIN 7 x64) says "Drivers not found"

So then I read your edit on OTG cable + pendrive...but the end of the OTG cable CANNOT FIT!!!! how is this?? aren't all USB 2.0 pen drives the same...I am literally trying to push it in.....so I can transfer the file son pen drive via cable....am I missing something.....Thanks for your help..I am really trying to "google my way " out of this one aswell...

I feel really stupid trying it but here is proof that I am...

[IMG="pen drive"][/IMG]

---------- Post added at 08:55 PM ---------- Previous post was at 08:29 PM ----------

Three driver updates later I still cant find my device.....

[/URL][/IMG]
[ONE General] digitalpig82:
I was facing the same problem. Finally, I used this video and the drivers from the description and it worked.

How-To: Install Google ADB and Fastboot Drivers (…: https://youtu.be/kpUiIfAUNVU
[ONE General] seco007:
the only problem is I have no Operating system..so I cant just go into my phone and ENABLE ANDROID DEBUGGER or DEVELOPER OPTIONS,,,,

If I had any OS I would do this.....But I do appreciate the help..I do..its just I have been at this for 3 hours now
[ONE General] tijuanacartel:
You should be able to access adb from recovery.
[ONE General] seco007:
how??? I tried CMD....(see previous posts), tried OTG + Pen drive (see one page back)....tried ADB SIDELOADER (I was not able to enable android Debugging or USB mode, I had no operating system....so....how do I access adb via recovery????

---------- Post added at 10:37 PM ---------- Previous post was at 09:49 PM ----------

Update:

Seeing as I could never get my ADB DEVICE working via CMD windows...I downloaded an older version of the OPO toolbox here:

http://inthiaano.com/oneplus-one-toolbox/

Version 5 (CM11S XNPH44S)

So I would have a working OS...I did this cause I know that this older version "pushes" CM 11 to your phone....then I wiped system /data/ dalvik / cache and flashed the newest nightlie, tk gaaps and kept stock kernel. Now I am just tweaking and updating.....

Thanks to all who helped....I love this forum!!! hopefully my experience can help others...

On that note, I only have one question, does any one know XDA developers stopped including an OS file with their latest tool kit (see a couple of lines above)..it seems that even though it makes the download larger it is very useful to get people like myself out of trouble in case we screw up. I was just wondering if anyone knew....just curious....

Thanks all!
[ONE General] tijuanacartel:
an update to my previous issue re bluetooth voice dial... seems this is only supported on US or UK locale. setting to those locale brings it back.
[ONE General] tiny4579:
7/13 is out. inb4 someone says, I flashed 7/13 and now everything is too green!

No I didn't flash it myself. I noticed it still wasn't fixed based on the changelog.
[ONE General] batwingnz:
I'm intrigued, just how green is this green? Any willing guinea pigs?
[ONE General] criminalzen:
what a group of cowards...... besides I notice no diff in color..... :P
[ONE General] hogze94:
While not really discussion, you can file bugs and request new features here: https://jira.cyanogenmod.org/
[ONE General] criminalzen:
thanks , I was aware of those. I came to the oneplus a couple of weeks ago after breaking my nexus 4 in a minor motorcycle accident. I was used to the official cm orig dev threads.. i.e. no discussion, no xposed, no extra kernels, you get my drift.. nothing against the cm discussion threads. The xda threads for the oneplus are different than the nexus development threads... I am just trying to find my place in a new world ... heh ....
[ONE General] :
13th flashed and everything is fine!

no greenish screen, white as before!

Gesendet von meinem A0001 mit Tapatalk
[ONE General] AcmE85:
Screen calibration definitely changed and is more green now.
[ONE General] fmc000:
Wow, different opinions I see. Guys who updated to 0713: would you mind sharing what hardware do you have, OPO version, panel make, whatever...?
[ONE General] giaur:
As I suspected, some people don't even able to see any difference. Color reception is not the same for everyone :) Also note: white as before just after boot. But it's enough to screen lock & unlock and you will notice ugly greenish. This is definitely a bug and not intended. Should be reported to cm jira.

I'm one of those who is really sensitive for things like this. Greenish is unacceptable for me, this bug should be fixed.

---------- Post added at 07:27 AM ---------- Previous post was at 07:23 AM ----------

I think it's about their sight, not their hardware. I remember totally pee - yellow calibration in old CM11s, and some people can't see any difference with current one.

---------- Post added at 07:35 AM ---------- Previous post was at 07:27 AM ----------

P.S.

https://jira.cyanogenmod.org/browse/NIGHTLIES-1555

Votes please :)
[ONE General] batwingnz:
I remember the yellow, but I can't see green on the latest. Looks fine. My fiancee with infinitely better judgement of such things (graphic designer) also can't see green.
[ONE General] giaur:
Not any sense to show it for other people, to notice that you need to have something to compare with or remember previous calibration. Also it depends from theme you applied, possibly this effect is hard to see with some dark themes.
[ONE General] AcmE85:
Yes. I'm really prone to see slightest differences in color. I even reduced the green value to 98% prior to today's nightly because it was a bit too green.
[ONE General] batwingnz:
Cool. I'm comparing white with white and yeah I do usually notice a difference. And yes it is sensible to show it to someone else who uses this phone. My experience does not negate yours. Looks white next to my pc monitor and other cellphones in the house :)
[ONE General] giaur:
If anybody can see greenish, please comment my jira report and vote up to force them to look at it.
[ONE General] benj!:
13/07 definitely looks green to me.
[ONE General] hib1000:
Voted!
[ONE General] fmc000:
I read on another thread that the latest CM nightly fixes the compass problem. Anyone can confirm this, please?
[ONE General] DarkBlack22:
Downloading the latest cm12 version. Will report back after flashing
[ONE General] dubazar:
More greenish than yesterday. Voted too
[ONE General] tiny4579:
I noticed a blob update last night that includes a sensor update. Maybe that's what did it. I'm waiting due to the color calibration screw up.
[ONE General] dubazar:
Could someone provide me what kind of issue is related to the compass? I'm on latest nighly with greenish screen and my compass sensor seems to work but only when the phone is used horizontally.
[ONE General] fmc000:
You already answered yourself (and confirmed that the compass is NOT fixed, BTW).
[ONE General] giaur:
Isn't it hardware issue? Btw, my compass works all the time, device vertically, horizontally, no matter. Or I don't understand what's the problem
[ONE General] gondsman:
No, it's not a hardware issue, as switching to COS12 makes it work correctly again. The best way to understand why it's completely broken is to try to use google sky map or (better) SkEye or Peakfinder from the play store. You'll figure out immediately what's wrong with it.
[ONE General] DarkBlack22:
Hi guys is your Bacon always running warm? Cause mine's quite warm when using it and warmer when charging.
[ONE General] fmc000:
That's strange, this means that COS framework is different from CM's. Is COS based on 5.0.2 or 5.1.1?
[ONE General] AcmE85:
It's still on 5.0.2.
[ONE General] fmc000:
That explains everything. The bug was in fact introduced with CM12.1 . FWIW, Onmi and Oxygen are fine with regard to this.
[ONE General] DarkBlack22:
Anyone of you facing heat problems? My Bacon runs warm easily and when it's charging it gets warmer.

EDIT: Sry for the repost I've forgotten that I've posted about it ?
[ONE General] chvybeatsford:
On 7-12 .. And also happened on few before. Randomly I won't get text or calls for unknown amount of time. This morn my wakeup call never came. Seems calls go straight to voice mail.

What I noticed doing testing last night seems only when on WiFi. I can text my self and when I receive that (sec later) I'll get a bunch from others at once.

No exposed or anything other than nightly installed on slim mini gaps..
[ONE General] giaur:
I don't care. Cm nightlies don't exists for me until greenish fixed. 12/07 nightly is latest available for me until then.

My latest build is equal to 07/12 nightly + remove some security crap like selinux and block write to otg. The best and bug free so far.
[ONE General] spyd4r:
honestly the compass has never worked for me, driving on google maps it's always off directionly by around 30 degrees or more.. doing the dumb calibrating does nothing.
[ONE General] fmc000:
just out of curiosity, do you remove the OTG restriction with the usual xml trick?
[ONE General] giaur:
Yes, but before compilation so it's already included in zip.
[ONE General] karangupta:
If there's green due to the software it would also be reflected in a screenshot and can be diffrenciated using a phone with an older version of the nightly! So if someone is actually seeing some green, post your screenshot with a white background(maybe Google homepage) and let's verify it.
[ONE General] davidfi01:
Screen does not completely sleep

Since 07/12 build, I have noticed that my screen only sleeps when I use the power button to turn it off. If a notification comes in, or I don't use the power button to turn it off, it only dims, but does not go off completely. Any ideas or has anyone else been having this problem?

I have adjusted the timeout values and the dimming time is affected, but no screen off.

Thanks,

D
[ONE General] BoboBrazil:
Screen definitely has a tint to it now compared to the previous nightly. Hope they revert it in tonight's nightly.
[ONE General] giaur:
Sorry, it depends. It can be noticeable on screenshot but also it can be not noticeable.
[ONE General] fmc000:
Just tried: cannot reproduce with an incoming SMS: the screen turns off as expected. Tested with the phone in stand-by and also with the device already active: I have the correct behavior in both cases.
[ONE General] tiny4579:
Do you have ambient display enabled in settings under display and lights? The dimming sounds like ambient display.
[ONE General] DARLAIVE:
Hello,

Do you have the same problem:

Unable to activate the WiFi once you disable the notifications panel?
[ONE General] :
white with the usual yellow band at the bottom. There is nothing greenish on my phone.
[ONE General] giaur:
You are unable to see it or you are not affected. Most likely, the first option.
[ONE General] Stories:
Yup, I noticed this too. Very very green.
[ONE General] :
yeah my doctor says I cant see green when there is none to see, Its a problem that 100% of the population have. It is a very strange thing, like your question.
[ONE General] giaur:
You can say anything you want, but so far appox 90% of people who tried latest nihtly, reported greenish I obviously can't be sure, but I suspect the rest are unable to see difference, due to custom theme, or maybe color reception, not focusing on things like that etc.

Exactly the same situation was on CM11s with incredible yellowish and some poeple was unable to see it.
[ONE General] davidfi01:
Trying that now. Switched it on then off - will see if it helps. Have they been messing with the sensor code?

D
[ONE General] :
clean installation made an hour ago and everything looks fine to me and Im usually the first one to see weird tints on LCD/amoled/IPS/etc screens.

That is all I have to say about this.

Edit: Phone was made in october 2014 if this could help
[ONE General] sabrefresco:
I've had the screen not turning off issue from the nightlies since the end of June. Ambient display was off, and I tried turning it on and then off again just to make sure that wasn't the problem. Didn't help. The only thing that did work was setting Sleep to 15s. Obviously, the screen also turns off after 15s when the device is unlocked so that's fun. I am using the AK and Xposed. Currently on 0712.
[ONE General] :
well I finally found a nightly that runs fine(very smooth, no FC, no error message of any kind) but the WiFi is extremly slow for some reason, and it looks like the battery drain is terrible.

Back to 4.4, again...
[ONE General] Renosh:
I can confirm the color is different on latest CM12.1 nightly. Has a greenish tint to it, makes the colors look slightly different but its not so bad that I'd call it a must fix problem.
[ONE General] giaur:
So, I was right :) Yep, you are one of those who don't focus on screen colors. But for me it's not acceptable, this sholud be fixed . I can see bunch of greenish there, maybe my sight is more sensitive or what... I don't know. But difference is huge for me, I would not call it "slightly different"
[ONE General] fards:
Or it could be not everyone is affected by it.

I never had yellow on cm11 and I'm not seeing green today.

Nothing to do with perception.
[ONE General] giaur:
Impossible in my opinion. The DID notice new color calibration in their changelog, so colors was changed for sure. If you are saying you did not notice any difference, you probably was unable to see any difference.

When reading opinions like yours, I'm starting to think, that colors perception varies very much, I'm unable to find any other reason. But I'm surprised by scale of perception differences - the same difference is very huge for me, barely noticeable for some other person and not existing for 3rd person. So weird, hmm.

In any case, further discussion about that is not needed :)
[ONE General] fards:
sorry but what you have said is pure conceit.

what youve said is

if you dont agree with what i say then there must be something wrong with you, that is wrong on every possible level.

as we all know there have been changes in hardware on these devices. they aren't all the same and therefore wont all see the same thing.

the compass is another fine example, for me it was working ok with sultans build, today it wasn't, but his started working, neither of us are imagining that, so the logical conclusion is a difference in hardware.