yashsingh1/xdaforums huggingface dataset:
[ONE General] DARLAIVE:
Hello,

I need to know if you have the same problem as me:

Unable to activate the WiFi when you disable the notifications panel?

For I find no one having the same problem as me and it's one month that I must have this. This morning I deleted everything and reinstalled everything and the same.
[ONE General] giaur:
But look... they changed colors to colder but you did not notice any difference. Hardware can't be different so much - totally changed white bslance, but no change on some devices. Isn't it sound weird? Also note, my intent is not to give offence for you or for anybody, it's just my thoughts.

But now we need to stop this offtopic discussion, its not neccesary, really.
[ONE General] aznracer62:
There's nowhere in his response did he say something was wrong with you, relax. It seemed like he was implying that it is surprising that each phone gives different results to different eyes. Perception has a major influence. Everyone has different visual perception and different sensitivity to the color spectrum.

If he notices a greenish tint but you don't, then good for you. Good job, high five. Much OnePlus. WOW. I haven't noticed any difference in color for the past month. The last time I noticed a color difference was maybe about a month ago where it had a slightly greenish/blue tint.
[ONE General] Sash!:
weird high consumption by CyanogenMod System

Hopefully someone will be able to help:

I've recently decided to switch from CM11s to CM12.1 nightlies. CM11s was great overall, almost no issues and the last run was around 1500 hours, which is not bad for a smartphone :) I was usually getting 4 hours SOT, 2 hrs calls per cycle with 3+ days standby time - absolutely fantastic balance. Only tweaks I've used were Greenify and a few disabled services.

Since I am on 12.1, I notice weird high consumption by Android System (CyanogenMod System).

https://www.dropbox.com/s/yxnlik4ho2aaid7/Screenshot_2015-07-13-21-19-49.png?dl

I don't do anything different, with KitKat Android System and Kernel were both around 8-10%.

Is someone else noticing the same? The phone is having a good level of Deep Sleep - around 90%, I've set Google Play Services not to wake or keep the device awake. Or do you think this is a bug with the app? The regular Battery monitor also reports Android System as the most consuming, even above screen time.

BetterBatteryStats also reports *system* as the most power consuming process - 50%+.

ANy thoughts are much appreciated! Thanks!
[ONE General] fmc000:
OK, now you're exaggerating and your attitude is frankly quite annoying.

I was one of the people who NEVER had the yellowish tint and, believe it or not, many of us bacon owners never suffered from this problem. But I guess that you have made up your mind already and nothing will convince you.
[ONE General] Dzhedaj:
Finally the lockscreen proximity sensor check is working properly, so the phone won't keep unlocking itself in the pocket.
[ONE General] aznracer62:
Again, like my last post, everybody has a different sensitivity to the color spectrum. How is the ability to SEE being a result of being convinced. You quoted it yourself in his sentence, he mentions that some people are UNABLE to see the yellow tint so he is acknowledging that the issue does not affect everyone. I, like many others, did not see the yellow tint. If he saw it, then he saw it. A quick google and youtube search, you can find many threads and videos on the yellow tint. I apologize if I'm understanding you differently as English may not be your first language but I don't see any exaggeration or attitude.
[ONE General] giaur:
No need to convince me, my only thougts are reasons why some people are able to see color differences and some others don't. Don't get it as any personal attack. I think all is about point of view, previous screen calibration was more warm, current is colder, all the rest is only personal interpretation.

Again, I suggest to stop this discussion here, it turns into unnecesary spam.

But regarding to greenish, it was not intended for sure, because screen starts to be green not immediately, but after first screen lock/unlock. Immediately aftet boot, colors seem to be fine.

---------- Post added at 10:06 PM ---------- Previous post was at 09:27 PM ----------

P.S.

They just assigned bug report to Steve Kondik.
[ONE General] ch-vox:
Random reboot

I'm following this thread (+jira) everyday, and for 2 or 3 days no one complains anymore about random reboots.

Has CM12.1 nightly been fixed about this particular issue that made me quit to AOSPA-L temporarily ? I can't see any specific commit related to random reboot.
[ONE General] Brian325:
I haven't had any reboots but I always use a custom kernel.

Sent from Hot Bacon®
[ONE General] tiny4579:
Stock and seems stable since I went back from sultan on 7/10.
[ONE General] lordsinasina:
Why did you come back from Sulatn's [emoji3] ?
[ONE General] ch-vox:
Effectively, this seemed to be one of the workaround, but I'd like to use stock CM12.1 without being annoyed by random reboots. I was monitoring my OPO with Reboots monitor apk and I was suffering from silent soft reboot once or twice a day... as many people dit few days ago, but I can't read it any post about it anymore.

---------- Post added at 01:08 AM ---------- Previous post was at 01:07 AM ----------

thank you [MENTION=3500210]tiny4579[/MENTION]
[ONE General] Brian325:
I feel most issues with CM is the kernel. Seems to work much better with cleaned up kernels like AK and Boeffla

Sent from Hot Bacon®
[ONE General] tiny4579:
To hopefully catch remaining issues.
[ONE General] j8048188:
On jul1 build i had tons of reboots. On jul7, no reboots. Stock kernel. Slim mini gapps.
[ONE General] highdiver_2000:
Almost all Android 5.1 are suffering from mobile radio battery drain.

Join the fun here.

https://code.google.com/p/android/issues/detail?id=165558

---------- Post added at 09:33 AM ---------- Previous post was at 09:31 AM ----------

There is no fix for this.
[ONE General] tiny4579:
Color issue may be fixed on the next build. http://review.cyanogenmod.org/#/c/103169/

Can't confirm it since I didn't test 7/13 and am downloading 7/14 now.
[ONE General] BoboBrazil:
Not fixed
[ONE General] KaZo58:
fix came a bit late :D it's for 7/15
[ONE General] hogze94:
There was alot of kernel commits on the 8th, check that out. Recently ( i think 13?) there's alot of debugging commits within the kernel, probably to help diagnose this issue.

The bug is filed here: https://jira.cyanogenmod.org/browse/NIGHTLIES-1327
[ONE General] KaZo58:
7/14 wiped all my wifi keys. (!)
[ONE General] cephaus:
my phone has been running INSANELY hot. talking consistently at above 60 degree Celsius.
[ONE General] fmc000:
Which nightly? I'm running 0712 and don't have this problem (and never had it with any previous releases, BTW).
[ONE General] prinz3nroll3:
Random reboot still exist, nightly from 13 july.

Back to AK kernel.
[ONE General] :
Everything fine for me with 7/14
[ONE General] Sash!:
Is someone else experiencing missing weather info in the notification drawer? For some reason, after I switch it on, there is nothing displayed. Any ideas how can I turn it back on?
[ONE General] :
No random reboots for ages with up-to-date nightlies.

Stock cm nightly, cm kernel, no xposed, ..., >100 user apps

Opo from July 2014
[ONE General] Hitschman:
Just did a full wipe and installed nightly from 14 july. Had first reboot this morning.

After weeks on the nightlies and still multiple reboots a day, I will unfortunately have to go back to stable.
[ONE General] pijas82:
Full wipe without factory reset?

Sent from my A0001
[ONE General] Sash!:
Please ignore this post - it is a typical PICNIC (Problem In Chair, Not In Computer) - I happen to have restored the clock app via titanium and it was a different version from an older rom. Reflashed the nightly, all works perfectly now.
[ONE General] Hitschman:
Factory Reset

I did a factory reset. Data, Cache and Dalvik.
[ONE General] Dzhedaj:
Funny, the green tint was mentioned to appear with 0713 nightly, I didn't have it.

However after installing 0714 nightly - it's obviously there.
[ONE General] fmc000:
Stock kernel? Live display on or off?
[ONE General] benj!:
0714 is pretty green, but otherwise running nicely. I can live with green :P
[ONE General] tiny4579:
Hopefully the commits going in by Steve resolve the issue. According to the original commit, this code wasn't supposed to functionally change anything with live display but obviously it has.

[MENTION=5411589]giaur[/MENTION], have you tried building with the latest commits to see if your green tint is gone?
[ONE General] Dzhedaj:
As a matter of fact, with stock kernel it's there since yesterday, I forgot was using AK kernel which merged these commits only today.

I have live display off BTW, as I find it useless.
[ONE General] giaur:
No, not yet. Actually I'm waiting for bug report to be closed or mentioned to be resolved. I don't have enough time for testing and reverting from backup now. But if anybody managed to test latest commits, please let us now.
[ONE General] rbrugman:
Location Services

Is anyone else having a problem with GPS/location services not working? I haven't been able to get them working on the 5/15 or 7/12 builds. Everything else is functioning properly. Where are the places that I should check to make sure I didn't accidently disable it?

Thanks!
[ONE General] MaffyRain:
I'm on 7/12(dirty flashed) and GPS works well. Same for location.
[ONE General] piaci:
status bar clock

anyone else having the issue of hiding clock from status bar then suddenly reappears? under settings it indicates to be hidden.

also, changing battery notification light to a different color crashes settings.
[ONE General] fmc000:
No

Yes and not only that: in my case when the display goes off the notification light turns on (in white) without reason. A soft reboot fixes it.
[ONE General] piaci:
actually that is how it ends. settings crashes and the led is still on with the new color, until open again custom color and cancel.
[ONE General] DarkBlack22:
I'm also having the same prob
[ONE General] rloup:
Same by me!
[ONE General] herclis:
Hey guys,

I'm so fed up with the constant issues.

Any recommendations for 5.1 ROM that just... works?

Thanks!
[ONE General] prinz3nroll3:
Pick a stable nightly and dont upgrade every day.
[ONE General] crisis_trustee:
Will be included some Apps from Android M Developer Preview and Apps from Android M Developer Preview 2 into CM12.1?
[ONE General] uluxus:
Flashed 0714, received no notifications over night and couldn't use network this morning, had to reboot.
[ONE General] deezid:
Can confirm. Greenish screen here as well with newer nightlies. Will downgrade to an earlier version. :(
[ONE General] giaur:
So, vote and make comment on jira

https://jira.cyanogenmod.org/browse/NIGHTLIES-1555
[ONE General] W99DEY:
I haven't had any soft reboots for 6 week, then it was the odd build
[ONE General] ch-vox:
Thanks

I've read every single commit but none were putting the finger specificaly on the random reboot thing. that being said, I've tried latest nightly for 12 hours, and I've found better feelings about UI smoothness.

I also follow JIRA thread since its beginning, but unfortunately there's still bad report about reboot since yesterday

I did not experienced any random reboot while testing 0714 today. BUT one new point to me is that my screen became unresponsive all of a sudden, while in my pocket. I had to hard reboot my device to retreive a normal situation.

back to AOSPA-L for now, I'll check for CM later... :D
[ONE General] Brian325:
7/15 flashed with boeffla beta 10 and color is good
[ONE General] HaloTechnology:
is 7/15 are stable enough to flash ?
[ONE General] musashiken:
Greenish tint on 07/15 nightly. Everything stock.

Edit: Looks like Steve is on it. Gonna flash a custom kernel in the meantime.'

Edit 2: Nope, I'm back to 07/12 Nightly. Seems like flashing a custom kernel doesn't remove the green tint for me.
[ONE General] giaur:
Thanks for info, so issue is not kernel related.
[ONE General] Renosh:
I'm assuming it depends on if the custom kernel has been updated with the offending commits. Using older kernels like Boeffla should fix it
[ONE General] giaur:
You may be right, however not updaed kernels often cause some other problems, like fcs or even bootloops. I hope this issue is going to be fixed any time soon in stock kernel (if kernel related)
[ONE General] musashiken:
Well I only tried Boeffla beta 10 and the screen still looks greenish. Are you referring to maybe beta 8 or 9?

Someone mentioned he used beta 10 and the color was fine, but that's not for my case.

Also a reflash of 07/12 did not remove the green tint at first, I had to wipe cache and dalvik and the color went back to normal.
[ONE General] benj!:
Still green for me on today's nightly. I'm kinda used to it now though; it makes me feel like the hulk or something
[ONE General] AcmE85:
I managed it a bit by reducing green to 94 % and red to 98 %.
[ONE General] giaur:
Yes you can, but still colors are not the same as before this bug
[ONE General] Matteo_666:
Im curious about the various Finger print patches for our Bacon. Do i need an app to use them for lock screen?
[ONE General] fmc000:
http://review.cyanogenmod.org/103327 and http://review.cyanogenmod.org/103328
[ONE General] giaur:
They are not for bacon, they apply to devices with fingerpring sensor.

---------- Post added at 12:30 PM ---------- Previous post was at 11:35 AM ----------

Maybe Steve Kondik is Incredible Hulk's fan
[ONE General] che586:
help

hi...

do i have to flash any firmware b4 flashing this rom if m coming from cm11s.?

coz m nt able to update via cyandelta...it is giving some error
[ONE General] giaur:
What kind of problems?
[ONE General] devilsshadow:
Surprised to see nobody is using PA Pico gapps. I would assume any so called expert in the arcane arts of Android flashing would want the most barebones and bloat free gapps available. And it doesn't get any more barebones that gplay services + playstore.

http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html?m=1

And no this isn't an advert, I just thought I'd point people in the right direction. I've been using these gaps ever since the early days of KitKat and they've never disappointed.

Sent from my OnePlus One
[ONE General] tiny4579:
I think the only part of the process where the flashing process needs to read the existing system is the addon.d backup restore which for most people is gapps. Manually flashing gapps after each build seems to be going fine so far.

For me the bigger problem is I use addon.d to keep the betterbatterystats system app after each nightly.
[ONE General] :
hello,

please, how can I find the last nightly for a device in jenkins?

thanks
[ONE General] fmc000:
OK, I will stop updating for a while then ;)

---------- Post added at 12:00 PM ---------- Previous post was at 11:57 AM ----------

Well, it looks that many of us don't need to be pointed "at the right direction" actually. Slim zero gapps work just fine and they contain, surprise, just play services and play store. And they are updated at Yesterday, not at March like the link you posted.
[ONE General] giaur:
So, I flashed modified twrp 2.6. Let's see how it goes, waiting for next nightly.

P.S. I really like euroskank gapps. They are minimal and they contain face unlock, trusted voice unlock (can't test because my country is not supported). With slim mini I need to get standard (too bloated for me) to get face unlock support.
[ONE General] fmc000:
I suspect that the real problem for the CM guys is that that also the /system/etc/hosts contents get lost if you're not using the stock recovery and this is probably what's stopping them to publish the nightly.
[ONE General] giaur:
Minor issue though
[ONE General] fmc000:
I use normally [MENTION=3814731]katinatez[/MENTION] modified recovery because of the ability to backup the modem and persist partitions, so I'm waiting for news from him.
[ONE General] Spannaa:
I'm not sure you can if it's not listed on the build page.
[ONE General] the Doctor:
If coming from CM11s, I would do a complete wipe and start clean using the 4/18 build available at the download site. See OP for links.
[ONE General] che586:
thanks

thanks....i flashed the firmware b4....may b thats y its giving error while updating.....
[ONE General] :
When I flash nightly from Apr 21 the build.prop (and possibly other files) are corrupted.

Can any confirm the MD5SUM?

f06bd3c5dbc31b1fb3a0a5be5f774043 cm-12.1-20150421-NIGHTLY-bacon.zip
[ONE General] giaur:
Looks the same:

f06bd3c5dbc31b1fb3a0a5be5f774043
[ONE General] :
thanks.

is the same md5 but when i install the build.prop seems a binary file :(

it occurs also with Apr. 20 (see screenshot)

don't occurs with Apr. 18 version
[ONE General] giaur:
It shouldn't be, mine is ok. Flashed via twrp 2.8.5.1 (modified 2.8.6 not tested yet). It seems to contain build.prop strings mixed with some mess. Or your editor issue?
[ONE General] devilsshadow:
Must be why there are two distinct reports of problems with slim gapps in the previous two pages alone. But hey, if something works for you then surely it has to work for everybody, to hell with alternatives and choice.

/s
[ONE General] shoman94:
Anyone have a custom kernel installed that boots 4/21? The slow charging on the stock kernel is unbearable.
[ONE General] Miikli:
This explains everything! ?
[ONE General] DarkBlack22:
Stock kernel or AK kernel? Overall performance and battery
[ONE General] Spannaa:
It depends on your usage and what tweaks you apply to AK.

There's only one way to find out which is better for you ;)
[ONE General] bundysoat:
I have to do something special to install the ROM Nightlies prep school with MultiROM ???? I detected in the Recovery, but does not start .... and if I make the "current boot inject" does nothing .... not actually choose ROM screen does not come out.
[ONE General] criminalzen:
I suggest you ask the question in the multirom thread.
[ONE General] Coraz:
Since I was having root permissions issues with an app, I tought to flash SuperSU from zip, but now seems like I don't have root at all, SuperSU isn't even opening and I can't unistall it since it seems like it is regarded as system app. Will this issue be resolved if I flash the next OTA, or I must do a wipe and clean flash again?
[ONE General] giaur:
Possible fix for Incredible Hulk syndrome: http://review.cyanogenmod.org/#/c/103372/

Let's wait for new build

---------- Post added at 10:55 PM ---------- Previous post was at 10:52 PM ----------

Try to reflash rom. If it does not help, wipe system and flash rom and gapps. And forget SuperSU, it's not needed and not supported.
[ONE General] tiny4579:
There are a couple commits in review for this. I'm quite confident these commits when merged will fix it.
[ONE General] novren:
I think that tomorrow I will perform a factory reset and back to 0614 I go, best nightly until now.
[ONE General] ViViDboarder:
Are other people still getting "System Not Responding" from time to time? I've been updating every so often but keep getting it.
[ONE General] jaydizzle333:
Try reflashing the newest tk gapps
[ONE General] tiny4579:
Looks like Incredible Hulk Syndrome patches will be in the next nightly, and not tonight's that just finished.
[ONE General] wild1z:
I see no green. Am I missing something? Latest nightly. stock. No mods. Am I not seeing the green? I have no money... So I have that going for me. ;)
[ONE General] HaloTechnology:
It could be fixed in 07/16 ? anyone can confirm ?
[ONE General] razorloves:
2 posts back http://xdaforums.com/showpost.php?p=61886456&postcount=3799
[ONE General] HaloTechnology:
Sorry I didnt get it before but now i get it
[ONE General] giaur:
To all who noticed greenish previously: is it still there after flashing today nightly?

---------- Post added at 07:36 AM ---------- Previous post was at 07:24 AM ----------

We don't really know which commits will fix that, it also could be this: http://review.cyanogenmod.org/#/c/103372/ and it's merged.
[ONE General] razorloves:
as tiny already said, the fix was merged after the 16th nightly was built, so it will be in the 17th nightly.

read steve's comments here http://review.cyanogenmod.org/#/c/103327/
[ONE General] giaur:
It's not clear for me that his commets are related to greenish, but you may be right, so let's wait for next nightly and we'll see.
[ONE General] benj!:
Green seems fixed for me today
[ONE General] Tromzy:
My screen became greenish too on yesterday's build. I'm downloading today's nightly, hoping it is fixed. :)

edit : it seems fixed !

edit2 : actually, maybe not.
[ONE General] Coraz:
Am I the only one experiencing relatively high battery drain when on screen? Even though off screen consumption is perfect, I got 4% less in 5 hours, whilst downloading...

Sent from my OnePlus One
[ONE General] deezid:
Quite bizarre, isn't it?

It seems to change color after a while towards green...

Went back to 7-10 build ;)
[ONE General] giaur:
Lock & unlock screen first, immediately after boot there is no greenish.
[ONE General] rloup:
I don't know if it is a bug or something in my oneplus one (I've try to search, but found nothing) : In settings > wlan there's a point to set wlan from automatic to 5 ghz or 2,4 ghz. So far, so good, but if I disable wlan by flightmod and will enable nothing works. The button in setting > wlan is grey, I am not able to enable wlan. It only helps if I make a hardreset. Is there any help?

(Sorry for my bad English , I'm an old, 70+, German)
[ONE General] CupaXL:
Not needed because same functionality is integrated in CM, right?

Not supported in the sense of one will get no support when having problems or not supported in the sense of it does not work at all?

I ask because I am not sure about the sense of my setup...

I installed the 7-12 nightly and [MENTION=6109902]mohit310[/MENTION] slim zero gapps with viper4android. SElinux was still set to restricted but after I installed SuperSU, as stated in [MENTION=6109902]mohit310[/MENTION] 's installation instructions, gave viper4android root permissions and rebooted it was set to permissive and now everything seems to work.

Does SuperSU interfere with the integrated function, or is it okay to use SuperSU with the current CM12.1 nightlies?
[ONE General] abyssq:
I'm using a cm12.1 rom, but there is a very annoying problem.

When I lock my screen, instead of doing the CRT animation or the lollipop fade hue, it flashes the lock screen and then fades out. Does anyone know how to fix this? It's driving me crazy!!! :crying:
[ONE General] :
Drainfest with CM12.1.

With any of the nightlies, I get almost 3 times LESS battery power than with CM11s. And this is after a factory reset between each tries and with only the stock rom/kernel + minigapps + Titanium backup + Gmail + Maps. Notheing else.

---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------

Im curious, why would you look at your screen after locking the phone ???
[ONE General] Coraz:
So we have to wait for a more stable release to decrease battery consumption or is it a Lollipop issue? Sorry for the silly question but I'm not really informed.

Sent from my OnePlus One
[ONE General] abyssq:
Why not? It's just annoying. I'm missing the nice new lollipop screen off animation. Is there a solution for this bug or I have to live with it?
[ONE General] giaur:
Yes.

I'm not sure what do you mean, but to get selinux permissive you either need install kernel compiled as permissive, compile yourself or use selinux mode changer. As far as I know, it's not related to SuperSu

Yes, it can interfere, actually not recommended.
[ONE General] tiny4579:
Drain has always seemed a bit higher than kitkat, but the more recent nightlies have had some of the worst idle drain I've ever seen in this phone. If its not just me, maybe we can isolate when and open a jira.