yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] ZaneZam:
recently happend to me too after a dirty flash to CM12s

and if re-flashing supersu 2.46 doesn't help i might have another solution: had that problem and found out that the app itself did'nt work properly (apps which had root before couldn't get root anymore and with

new apps there was no root request) so i went into supersu app settings and used "new install" to clean up app completely followed by re-install from the playstore. that fixed it for me, maybe a solution for others too.

actually they are already released and lord boeffla is already working on a kernel, but this time its more work and he had some build problems in addition
[ONE Original Android Development] abhibnl:
Zanezam, could you please have a look at my last post with the ss of that weird wakelock and suggest what may have caused that?

Sent from OnePlus One
[ONE Original Android Development] ZaneZam:
well never saw that but i carefully say it's not kernel releated or at least not directly.

dunno much about that service (because i never had issues with it *g*) but i would

guess it has something to do with sensors :) (no hard guess *g*), if i had that for a start

i would try to change settings related to sensors and see if that changes anything.

sry but not much from my side here ;)
[ONE Original Android Development] Orphee:
Hi, I didn't try CM12S original kernel, but I found the problem it is the DHCP IP acquisition... Phone tries to connect but always fail.

I entered a static IP in the phone, and I connected in 1 second on my home WIFI...

Can't tell why, I tried to disable wifi security on the box, nothing worked, only static IP in the phone do the trick...
[ONE Original Android Development] abhibnl:
It's actually kernel related since the ss i posted is of kernel wakelocks. It's killing my battery lyf. 6h49mins awake now [emoji20] [emoji20] [emoji20]

Sent from OnePlus One
[ONE Original Android Development] andip71:
For CM12 (not-s version) you need to flash the CM12 kernel, not the CM12s one.

AFAIK, there are no sources available. So the answer is currently no.
[ONE Original Android Development] andip71:
OxygenOS

Hi all,

after many hours of trying to even get a stock OxygenOs kernel to boot, I am giving up for the time being.

It seems, the published kernel source is either incomplete/erroneous or I am doing something significantly wrong.

I asked OnePlus for clarification, let's see what they answer.

https://forums.oneplus.net/threads/oxygenos-kernel-source.296969/page-4#post-10910921

Andi
[ONE Original Android Development] magnamentis:
you should perhaps educate yourself a bit more about these things. userspace issues can of course when interacting with kernel related components trigger kernel wakelocks which by no means means that the root of the issue must be kernel related. in fact it rarely is.

further whenever we face issues which others don't report we should assume at first that it might be something on our side, caused by something incompatible or misbehaving in our own configuration.
[ONE Original Android Development] Mkkt Bkkt:
Thanks buddy, I hope all problems get fixed soon.

---------- Post added at 09:28 AM ---------- Previous post was at 09:27 AM ----------

Okay thanks anyway.
[ONE Original Android Development] andip71:
Not looking very good, read up.

Andi
[ONE Original Android Development] Mkkt Bkkt:
Yes sorry I didn't read your last answer since I'm using my phone.
[ONE Original Android Development] abhibnl:
Wtf? They even messed releasing kernel sources? I hope they'll get back to you soon.

What i wanted to know is the cause of this wakelock. I'm not blaming kernel for it at all. That's why i specifically mentioned that this is d frst tym i'm seeing this wakelock. My apps, configuartion everything is same. Only difference from yesterday is cm12s. I was hoping to get a reply or any source to help me better understand what may be the cause since its related to sensors. And again, my kernel and rom configuration for boeffla is d same like previous cm12 roms. Now for the education purposes, do u have any idea what may have caused this wakelock?

Sent from OnePlus One
[ONE Original Android Development] ZaneZam:
my answer was related to the Oxygen OS so forget my repy on that :angel: too many os's araound u have to read carefully these days :)
[ONE Original Android Development] magnamentis:
we can try to narrow things down but would need quite some information. logs? firmware versions? rom+version installed? mods like xposed or similar? in the past few months sensor issues were often related to firmware changes or roms not in sync with latest cm commits etc.

it's not easy from the outside to find out but how many days did you observe the behaviour. it happens over and over again that something can cause an issue and after a reboot or re-flashing rom, gapps, kernel combo it stops. further you could look at things like gestures, or settings like accidental wakeup etc. but as i said, there are plenty of possibilities and last but not least a clean install would usually solve such issues if nothing else helps. is it intermittent or permanent which relates to the question how much time you spent observing this.
[ONE Original Android Development] Mkkt Bkkt:
Sorry , true too many Os's these days ^^
[ONE Original Android Development] HaTrED_:
[MENTION=947981]Lord Boeffla[/MENTION]

Saw this in another thread and - i think (?) - it might be usefull: http://review.cyanogenmod.org/#/c/94768/

New Wifi drivers. Hope they will solve all that wifi draining issues and so on... :fingers-crossed:
[ONE Original Android Development] DjDiabolik:
Yeah.. i know... at this point when my opo it's in charging using the SL (slide to 0) i can watch using 500mA at nomimal/maximal value. I need to know if this value it's the same for all or if someone obtain a different value because when i use the SL i obtain a very long time for charcing my opo.

I don't know if i can explain my exact question....
[ONE Original Android Development] abhibnl:
Hmm! That would be great. I hope our findings would be helpful for other users as well. Okay so the details:

Rom: Cm12s, released tuesday in india, clean flashed.

Kernel: do i really need to tell? [emoji13]

Xposed installed, 5 modules activated.

Firmware: Stock cm12s with oxygen os modem.

Gestures: All off, Prevent Accidental Wakeup disabled.

This condition which i remember correctly:

Phone was working all day with proper deep sleep, deep sleep was proper for tuesday, wednesday as well. The only thing i did different last night was, turn auto rotation on, watch youtube videos, clear recents, lock phone n went to bed. But auto rotation was on the whole night and i keep it off all d tym. As of now, i suspect that could be the issue but even after turning it off in d morning, phone was still awake. Hope this info would help.

Sent from OnePlus One
[ONE Original Android Development] andip71:
Well, it is important to know, in stock logic there are different charge rates.

One if screen is on, which is apparently capped to 900 mA.

One if screen is off, which is around 1600 or 1800 mA (cannot remember anymore).

But, I am reaching close to 900 mA when screen is on, not only 500.

See screenshot I just took.

But also to mention - charging is never a fix rate, it follows a curve, i.e. starts slowly, then going to maximum and going down again towards the end.

Why you cannot achieve something higher than 500, I unfortunately cannot tell :(

Andi
[ONE Original Android Development] andip71:
Interesting news for you.

I just found, they now officially reverted partial updates now on the 12.1 kernels.

https://github.com/CyanogenMod/andr...mmit/4912fcce74ccc928f94137c04e1d6ccdf4b6d0d2

Andi
[ONE Original Android Development] andip71:
I saw they were very brave and merged it into the official CM12.1 branch already.

I am about to compile a new 12.1 kernel.

But this time I wait with the backport to Cm12, CM12s, CM11s, Cm11 a while. To see first if this driver is now working better then the one before.

Andi
[ONE Original Android Development] magnamentis:
Rom: Cm12s, released tuesday in india, clean flashed.

very new rom, not much user input and experience available though, especially not for such specific issues. with new software it sometimes make sense to install step by step. rom without mods, see how it works ,then kernel, see again how it behaves and then mods and other special software like xposed framework. i recommend that which since you installed already a lot that would mean to go with a clean install. if you install all in one on first attempt and something goes wrong how you wanna ever find out what is the culprit. can do that of course but a least you should make nandroids of each major installation step then, so to roll back and see.

NO LOL :cool:

uninstall first all modules see what happens and if not better uninstall the framwrork, while i would still the incremental clean install path, no matter what. i strongly believe that albeit it's a lot of work ( depending ) it's after all less work then to mess back and forth with all the various possible culprits, while even when dealing with the right one, sometimes residues play havoc.

go with original to begin with, (see first paragraph why)

enable accidental to see what happens

there is room for testing here. same like accidental and the likes, switch rotation off, and observe for at least two nights , better more with and without airplane mode, location on/off and the likes, but again it will be quicker to fresh install in increments and the fastest way is clean install in increments while making a nandroid backup of each stage, means rom without app = nandroid + user apps = nandroid + kernel = nandroid + xposed without modules = nandroid + modules one after another
[ONE Original Android Development] ZaneZam:
very good idea my friend appreciate this :)
[ONE Original Android Development] andip71:
Haha, you are just afraid to compile another 5 kernels.

Well, then I should think about it :D :D :D

Andi
[ONE Original Android Development] ZaneZam:
plz hold your horses, meanwhile it's far beyond 5 kernels :D
[ONE Original Android Development] andip71:
CM12.1

Hi all,

updated kernel for CM12.1 as the CM team officially put new wifi drivers in.

Version

4.0-beta6

15.04.2015

Update: Updated with latest 4 official CM kernel commits as of 16.04.15

This includes updated wifi drivers to LA.BF.1.1.1_rb1.18

Andi
[ONE Original Android Development] TheShoxter:
Yes, Cyanogen OS is the new name for 12s. In other words I am on 12s and lost root when i flashed the 12s kernel. It is Calkulin's stock 12s rom.
[ONE Original Android Development] andip71:
Then flash supersu again in recovery.

I did not lose it, don't know what went wrong.

Andi
[ONE Original Android Development] MMWolverine:
Thanks, [MENTION=947981]Lord Boeffla[/MENTION], for your fantastic builds! I spent most time with ak, but since he won't support COS12, namely fix the sunlight enhancement issue, I switched and I'm here to stay. :D

3.0-beta2 working great on stock and 4.0-beta6 on CyanideL 5.1 (running in MultiROM).

Kudos also to [MENTION=3279788]ZaneZam[/MENTION] for unofficial builds, I'll be testing them hard in the upcoming days/weeks. :good:
[ONE Original Android Development] Texan1:
Hehe, brilliant, finally been officially recognised as a bug/issue!! Thanks for passing that info on and I look forward to never having to disable HW overlay again!! :D

(of course didn't need to with the great Lord Boeffla kernel :good:)
[ONE Original Android Development] andip71:
Ok guys, some info:

a) Boeffla-config app

I just pushed an update to version 2.1.74.

Please note, this version CAN have bugs although it was tested now for more than a week.

The thing is, I finally took the step and left the Eclipse development environment which is not more supported by Google. It is now replaced by Android Studio. Funnily, the app got approx. 150 kB smaller after compiling it with Android Studio.

In any way, this is internal a super-major-big update !

But also the stupid bug with CM12.x destroying content of homescreen shortcuts is now "workarounded". So, shortcuts should now also work after a reboot on CM12.x.

b) WIFI drivers

I could not resist and already compiled for my internal purpose a CM12s and CM11s test version with the very latest wifi drivers backported again (r18). I will have a look myself and monitor what people on CM12.1 say, where these drivers are in since last night. Then I decide whether I make it available for everyone or not.

Cheers

Andi
[ONE Original Android Development] vazovskiiii:
Which kernel i can use on cos12?
[ONE Original Android Development] davebugyi:
The 3.0b2
[ONE Original Android Development] DjDiabolik:
I have wathed your screenshot... i'm very confused abot that and because my opo when use the SL the value reported inside ( ) it's "only" 500 in my case :) I always thought that it's the nomimal/maximum value used during the charcing operation but at this point i thinks it's wrong........
[ONE Original Android Development] andip71:
SL stands for "stock logic", which means you have the slider set to 0 for the charger type. But we clarified this already.

The other values are:

- the mA that the charge logic would like to request from the charger

- the mA that are actually requested from the charger to ensure a stable current situation

Andi
[ONE Original Android Development] andip71:
... wiring in a small advertisement for my Twitter account :D

There you can stay tuned about new kernels, updates etc.

Latest info here:

https://twitter.com/andip71/status/589104883820793856

Andi
[ONE Original Android Development] andip71:
Updates for all 5 active kernels !!!

Hi all,

I will disappear for a full week to a business trip very soon.

As a small present, I updated all 5 active OPO kernels for you (so you have something to play with, hehe).

Updates are for: CM12.1, CM12, CM12s, CM11 and CM11s.

Tested by me: CM12.1 and CM12s (rest you will test :D)

So here we go:

CM12.1 -- Version

4.0-beta7

17.04.2015

Update: Updated with latest 46 (!!!) official CM kernel commits as of 17.04.15

This includes fixes to latest wifi drivers LA.BF.1.1.1_rb1.18

Ramdisk updated to version of 17.04.15

CM12 -- Version

3.3-beta1

17.04.2015

Wifi drivers LA.BF.1.1.1_rb1.18 (fixed version) backported from CM12.1 kernel branch

CM12s -- Version

3.0-beta3

17.04.2015

Wifi drivers LA.BF.1.1.1_rb1.18 (fixed version) backported from CM12.1 kernel branch

Minor internal improvement

CM11+CM11s -- Version

2.7-beta1

17.04.2015

Wifi drivers LA.BF.1.1.1_rb1.18 (fixed version) backported from CM12.1 kernel branch

Enjoy !

Andi
[ONE Original Android Development] bloof:
[MENTION=3279788]ZaneZam[/MENTION]

Sorry if this is a repeat, couldn't find answer.

What's the status of your governors/HP for CM12S? Is it all stable now? Can i set them in beta 3?

Cheers.

And thanks for the new kernels Lord Boeffla
[ONE Original Android Development] ZaneZam:
yes u can all good in all recent builds I tested (at least for me) btw. the problem was only on 12.1 ;)
[ONE Original Android Development] acuicultor:
There's a dedicated thread to do that in general section

http://xdaforums.com/showthread.php?t=2998145
[ONE Original Android Development] schmitzekater:
Hey guys, any idea how I could get the swiping feature in the AOSP keyboard working in German? In English it's working, I am using it right now.

Any help is highly appreciated.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] funkstylez:
:drool:

Thank you Lord Boeffla! Excited to play around with the new kernel! Downloading now and hope you have a good trip!:highfive:
[ONE Original Android Development] bloof:
CM12S boeffla 3 beta 3

Anybody else having crazy wakelock (100% awake) from "dreammanagerservice"?

I know it is related to screen settings, but not sure which one.
[ONE Original Android Development] magnamentis:
why are you posting this in the kernel thread. wakelocks are caused by userspace tasks thus you have to find the culprit and post the problem in the appropriate forum/thread. good luck.

sorry almost forgot, no, never seen this issue but perhaps there are others who encountered that.
[ONE Original Android Development] bloof:
Because boeffla played around with the sunlight enhancement settings, so to know if anybody else had the same wakelock. If not then i look elsewhere.
[ONE Original Android Development] DjDiabolik:
In my head i start now to understand somethings about this :) At this point when i set the value to 1000mA my opo force required 1.A from the charger right ? But the charge does not occur at a constant mA but it's been using a value but it's been used a value dependent to current battery status..... it's correct ?
[ONE Original Android Development] Renosh:
Quick Google search of that wakelock and its related to Daydream. Try turning that off. Next time search before posting
[ONE Original Android Development] fmc000:
Flashed latest beta over the first CM12.1 nightly - all good so far, too early to speak about battery life of course.
[ONE Original Android Development] bloof:
Also ambient light settings and possibly other screen light settings, i played around with them to test kernel.

I never use Daydream.

Turned all of them off and wakelock is gone, so don't know for sure which one, and probably not kernel related if nobody else gets the wakelock.
[ONE Original Android Development] lou2s:
Not sure if this is kernel related.

As you can see in the screenshot, on the quick panel the wifi is off, but when I check the battery usage, it says my wifi has been on since morning. (shown on the layer under quick panel)

In wifi advanced setting I have "scanning always available" off all the time.

Anyone see this behaviour? Thanks.

Running stock cm12s and boeffla cm12s kernel 3.0 beta3.
[ONE Original Android Development] DrNinjaa:
Turn on the airplane mode and then turn it off after a boot.... that helped me to correct the wifi issue... hope it helps u
[ONE Original Android Development] andip71:
I did not "play around".

I was, for speed reasons to come up with a compatible kernel fast, not using the office source base in beta1.

But in beta2 and later I do, and that fixed the sunlight enhancement issue.
[ONE Original Android Development] andip71:
Yes.
[ONE Original Android Development] lou2s:
I tried that and for the past hour the wifi was finally not on. Thanks!
[ONE Original Android Development] Itay2108:
Extreme overnight drain

So I flashed the CM12 3.0 stable on CM12s.

the SOT was amazing and I got 3.5 hrs from 25%, but when I went to sleep and put it in airplane mode- the phone drained 20% overnight. (4-5% on stock cm12s kernel)

is the wrong kernel version the reason for the drain?
[ONE Original Android Development] ZaneZam:
for cm12s u have to use 3.0 beta 3 there is no stable for cm12s yet. and no its not your fault we have really quite confusing situation atm. with all the new roms. [emoji44] [emoji4]

edit : I forgot, u can look on www.boeffla-kernel.de and the version table there to get an idea, then its quite clear which version u have to use.
[ONE Original Android Development] Itay2108:
I know, currently the OPO is completely discharged but I'll flash it and report soon!

btw I love your work :)
[ONE Original Android Development] bloof:
Never meant to mean you were just "playing" with the kernel, meant you were "dealing with the issue" of the sunlight enhancement. English is not my first language, just used the wrong wording.

I fully know you came out with a kernel for CM12S in record time! You know we all really appreciate your work.

On beta 3 deepsleep is >96% of screen off time with drain at 0.5%/hour overnight, only with greenify on.

Touchscreen and wakeup of phone are great.
[ONE Original Android Development] Itay2108:
Problem gone after flashing 3.0 β 3
[ONE Original Android Development] lou2s:
The problem came back, do we need to do this everyday? :crying:

[Probably not kernel related but wifi driver? ]
[ONE Original Android Development] DrNinjaa:
Its a common problem with lollipop... actually, i am using the latest beta kernel by lord (the uber one by [MENTION=3279788]ZaneZam[/MENTION]) and I don't face this issue anymore. Its ROM related my friend.
[ONE Original Android Development] lou2s:
For the pass 5 hours I hv the wifi off but it's still shown as on in the battery chart... Using Lord's beta 3 for cm12s already. Sad...
[ONE Original Android Development] Renosh:
It's been like that for me for months now. I gave up trying to fix it and my scanning always available is off. I'm assuming it's just a display error on the battery graph
[ONE Original Android Development] EasyGoingXD:
Credits for those pics goes to [MENTION=4307845]alexbk66[/MENTION]

Damn deeeeeep sleeeeeep to the 6th of may ^^
[ONE Original Android Development] andip71:
It is, no need to be worried.

There were already more calculation errors in the battery statistics previously.

Andi
[ONE Original Android Development] :
Hi men ! I've flashed the latest AK kernel build on my OnePlus One this morning while updating my rom version, but it bricked it two times. So I return on my old favorite kernel :D There is no problem with Cm12.1 official nightlies last build here ? Thanks for your awesome work in all the cases btw, that's always great to have this kernel.

Okay, bricked too, it seems to have a problem with the today build. :P
[ONE Original Android Development] ak:
If you want to use the today build you have to use a kernel with all latest updates from cm12.1 branch.

Sent from my A0001
[ONE Original Android Development] Setting.Out:
Any difference in the test beta4 and the release beta4 for CM11?
[ONE Original Android Development] andip71:
Only the presets to show up in Boeffla-Config have been added. Rest is the same.

Andi
[ONE Original Android Development] magnamentis:
welcome

nice to see someone with such a great reputation making a kernel for our device. as i can see in the OP you are tending more towards stability and reliability than the fancy stuff which

could mean that i finally found my home kernel wise for this device. currently i had to go back to cm-kernel because i just cannot re-tweak too many settings upon each nightly update on 6 devices. time is getting essential there. i'm not sure if you are privy with [MENTION=4684315]flar2[/MENTION] his work. just wanna say that if your policy is somehow similar this is what i was looking for.

thanks for your contribution and you will find my $-contribution to you within short time should this works for me as expected :)
[ONE Original Android Development] NickosD:
booted fine with latest pa. thx!
[ONE Original Android Development] spanish33:
[MENTION=947981]Lord Boeffla[/MENTION] thank you for the cm11 version working good
[ONE Original Android Development] f100cleveland:
No issues at all since yesterday on cm11 version. Great work Andi!!
[ONE Original Android Development] Goggle81:
Thanks my Lord for CM11 kernel.

This was the birthday present I wanted ;)
[ONE Original Android Development] andip71:
Well, then Happy Birthday :)

Andi
[ONE Original Android Development] magnamentis:
solution

APP = ROMToolbox > performance > sdbooster > benchmark there you can play and test which is the best value for your device and config
[ONE Original Android Development] otisman:
App undated no prob here aloha Lord
[ONE Original Android Development] Setting.Out:
Phew, I've tried nearly every option, tweaked values and ran tests without even one flaw, this CM build is a rock! Very fast, and smoother than others I've tried with similar setups... This was tested on Sabermod Carbon...