yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Ofthecats:
Loving your kernel.

I ran into a problem. For some reason after restoring my oxygen ROM from backup, my baseband is missing and no APNs are listed in settings, and no service.

I was wondering how I could restore the boeffla efs that is in the sdcard folder? Considering it is a tar file not a zip.

Thanks
[ONE Original Android Development] andip71:
Only on command line. Never needed it.

Would need to dig that out first, but am at my pc not before Monday again.

Andi
[ONE Original Android Development] andip71:
But would advise first you try to install cms factory image. I doubt efs is really the issue..

Andi
[ONE Original Android Development] pchtc:
Sorry to have offended you, it's not personal. As I stated I will try future versions.

My battery drain is in fact back to normal since back on the oxygen stock kernel.

Oxygen only has 1 stock kernel at the moment, 1.00, I did provide this information in my post, there is no additional info I could have provided.

Other people have stated the same issue.

Dirty flash not needed. Just restore the boot, and lib/modules and sun link the wlan.KO.

I would be glad to test any new kernels, look forward to seeing new versions.
[ONE Original Android Development] andip71:
No, I am not offended. Just not convinced without more info (as kernel draining battery can only occur when a big issue is in the kernel).

At least someone said it started with a specific version for him. So I would need to understand from which version onwards it happened (and nobody reported, that is what is a bit sad...).

I have some plans for changes, but still would need that info. Anyone able to try...?

Andi
[ONE Original Android Development] :
I think the problem started around beta6, about when touch screen fix was implemented (I did not experience any problems with touch btw).

Drain started to get really bad and for the first time since I owned my One, it reached <15% battery - that's the first time in a year.

I thought it might be related to my usage (which was still quite normal tho) so I tried flashing up first and waited for beta7+8.

Neither fixed the drain. So I tried flashing down to 7, 6, 3 (yeah, I skipped 4&5 - no reason in particular) but nothing fixed the drain.

Now on beta1 and it's normal drain again.
[ONE Original Android Development] andip71:
What about beta2? Sorry, but then I have the full picture by you.

Anyone else having an opinion?

Thanks

Andi
[ONE Original Android Development] popimp315:
I think I would have yo agree with him. I hardly check my tapatalk to stay up to date which I should but I agree I think it started back with the new touch drivers because like this guy, I didn't have any touch issues with my phone. I also noticed my undervolt ran a lot cooler then than it does now. I'm on the latest and it seems to run a little warmer. The kernel is amazing though and I really enjoy the work you put in. I myself may end up leaving oxygen. I love stock but like you have stated, it is pretty incomplete.
[ONE Original Android Development] :
[MENTION=947981]Lord Boeffla[/MENTION]: I'll flash it now and report tomorrow.

I also really like the kernel, and Oxygen is fine for me. Thanks for your work! Let you know soon.

BTW, I recall Google Play Services battery usage seemed high. Probably coincidence tho.
[ONE Original Android Development] andip71:
Exactly. For Oxygen I also had to flash a special version of the play services made by Calkulin.

And this is why I asked people for wake locks and once I see that, we know more. Without it, there are just many words in the air.

Andi
[ONE Original Android Development] :
[MENTION=947981]Lord Boeffla[/MENTION]: Since flashing beta2, Google Play Services has reported 45 mimutes of keep awake.

Is this fixable by updating Services with said version?
[ONE Original Android Development] andip71:
Just to make it clear: this has to do nothing with the kernel at all.

It is an issue between the rom and play services.

And yes, Calkulin services should fix it.

It is the same on almost any cn roms too. The topic is discussed a lot everywhere, with explanation of why it happens on some roms.

Andi
[ONE Original Android Development] pchtc:
i dont have much input as i am new to the one plus one

i wason nexus5 from release day in OCT2013 until last week when i got the OPO

the only boeflla kernels i have tried are .7 and .8

other than that the stock oxygen kernel

oxygen does not appear to be CM based

i tried cm12s and cm nightlies and found them unstable

oxygen is more stock

paired with xposed and gravity box, it gives everything cm has to offer but is stable

this is also how i ran my nexus5

unlike some others

i do not seem to have any issue with play services drain

on .7 and .8 i had no additional usage of any specific item

drain was just faster acros the board

i had no additional wake locks

i have been back on stock for over 24 hours and battery usage is normal again

would you suggest i try beta 1 as another user reported that is was working well?

id like to contribute however possible and will try if you see it being of value
[ONE Original Android Development] popimp315:
Which version are you suggesting. I can flash tonight and then give feedback from tomorrow. Run it all day. I will also have to look into caulkin's fix as well. That is where a lot of my drain comes.
[ONE Original Android Development] andip71:
I always recommend the last version only. So beta8.

Unless I do a beta9 till then.

But unlikely as I rather consider stopping development of the oxygen os kernel due to oneplus team not being responsive and apparently not releasing new kernel code (although they have to according to GPL).

That really makes me p**** off.

Andi
[ONE Original Android Development] Ofthecats:
Me too
[ONE Original Android Development] :
Agreed.. It's been way too long and not even a system update, let alone source code.

Disappointing.

All the more praise for you tho Andi, with your reverse engeneering :)

Strangely, Calkulin's version of Google Play Services did not fix the battery drain for me.. :/
[ONE Original Android Development] M3drvr:
Instead if flashing the modified play services you can also install servicely and just stop the system update service. Every time play services gets updated it brings back the system update wakelock. But if you do it via servicely no worries.
[ONE Original Android Development] popimp315:
I am in fact running servicely. What exactly is the update called? Google play services has like 10 things up lol.

Also boeflla, I dont think you should stop development. A lot of people actually use this kernel and I for one enjoy it. I have since flashed back to beta two and it is cool as can be again. I will also give feedback from my days use.

Edit: system update doesn't seem to be listed in the many different Google services running.
[ONE Original Android Development] andip71:
3.0 stable and 3.1-beta1

Hi all,

I decided to not stop development in the Oxygen area, but to do a slimmified restart.

So, I therefore release version 3.0 stable now, which marks the end of the 3.x Boeffla-Kernel for Oxygen.

At the same time, I present you version 3.1-beta1 already. This is what I would highly recommend to be used now!!!

Version

3.1-beta1

08.06.2015

Completely rebuilt from scratch again

All functionalities of latest stable version 3.0 contained

No Linux upstream anymore as per close-to-stock objective

Changed wifi drivers to version 3.8.20.24

Version

3.0 stable

08.06.2015

zzmoove governor updated to version 1.0-beta7a - bugfix release (credits to ZaneZam)

Fixes for zzmoove relax profile (credits to ZaneZam)

Enjoy

Andi
[ONE Original Android Development] Ofthecats:
whats the idea behind starting from scratch and/or keeping close to stock?
[ONE Original Android Development] andip71:
I start from scratch from time to time, to make sure the code is clean and without leftovers of moving things forward and backwards again.

Also I finally decided to drop Linux upstream in all my kernels (OPO, also CM soon and S5) as it is proven again in the past months, it has absolutely no material advantages but cause other things to break and create a sh**tload of work for me every time. So it is useless, and no upstream is also closer to stock.

Andi
[ONE Original Android Development] Ofthecats:
sounds good. keep up the good work oh fearless leader :)

will try the new kernels soon. just fixed a corrupted efs partition.

---------- Post added at 05:32 AM ---------- Previous post was at 05:27 AM ----------

http://xdaforums.com/showpost.php?p=60964718&postcount=605

modified framework fixes root of the issue. it was made by dev of TGM kernel, and since flashing it my problems have disappeared.
[ONE Original Android Development] :
Awesome, thanks Andi! I'll update right away.

And please, do not stop developing. This kernel is what makes Oxygen viable for me and I appreciate all the work you're doing despite not having it as a daily driver.

I'm not familiar enough with kernel development from source to even try.. So I really enjoy your work!
[ONE Original Android Development] M3drvr:
You'll have to use paid version, or free pro version. Then you can see it under individual services.;)
[ONE Original Android Development] pchtc:
flashed 3.1 a few hours ago

will report back tomorrow night after full days usage

so far, its looking good

still not seeing any deep sleep

but a lot more 300

i'm pretty hopeful about this release
[ONE Original Android Development] andip71:
If you have no deep sleep, again: find the app that keeps your phone awake, it is not the kernel preventing deep sleep.

Use Betterbatterystats app...

Andi
[ONE Original Android Development] :
Stable kernel works like a charm. No hickups/wakelocks/.. Perfect so far! :)

*flashing 3.1 now
[ONE Original Android Development] pchtc:
Oh i understand that part. What I was saying is that it performs better than stock kernel so far. Also Much better than .8 and .7 I'm actually seeing it at 300 a lot.

My wake locks seem to be from play services but they have not released the hacked version of 7.5.

With the exact same wake locks .7 and. 8 had battery drain worse than stock but now on 3.1 drain is about same as stock so far
[ONE Original Android Development] pchtc:
3.1 worked well. Much better than beta 7 or 8 but not quite as battery friendly as stock.
[ONE Original Android Development] andip71:
Yeah, my last explanation for this is then: OnePlus team did not give us their real source code but a different version

There can be no difference to the negative otherwise.

Andi
[ONE Original Android Development] pchtc:
I completely agree. I hope they update what they have released. Don't they have to through GPL.

Keep up the good work. Thanks for your releases. I will keep trying them.
[ONE Original Android Development] szaf:
I have much better battery life with 3.1 than beta 8,but I think beta 8 was smoother. I have boeffla tweaks enabled
[ONE Original Android Development] andip71:
Really? I did not have this impression myself. In any way the kernel is now closer to stock again, which I do believe is the right thing.

Andi
[ONE Original Android Development] popimp315:
Can someone please tell me wtf net scheduler is and why it decides to chew up my battery. I had the screenshot bit of course, my phone screen cut off and it reset the stats.
[ONE Original Android Development] andip71:
I do not know so far. But you seem to be not alone. Seems to be related to Google services.

http://www.openeducationr.com/?p=53844

But is just what I found after some quick googling.

Maybe someone knows more about this thingy.

Andi
[ONE Original Android Development] Neroga:
Flash the 5.0 gapps from here http://xdaforums.com/showthread.php?t=3082242 . tested it on both OxygenOS and HydrogenOS and it works splendidly. Clean flash on both ROMs with the kernel and gapps and kept the screen on for an hour so NO deep sleep would show. After that hour, I let the device sleep for an hour and about 95% of that was pure deep sleep. If you're having problems with the calendar sync not showing/working in settings -> Accounts or your calendar app, this also fixed that problem for me on H2.

Great work [MENTION=947981]Lord Boeffla[/MENTION]. Made my switch to H2OS a lovely experience! Only things missing (from my personal taste) is the impulse governor, underclocking, and sync threshold control in your config app.

Tested with the Kernel Adiutor and Synapse, with sync threshold disabled (or lowered to 422MHz for Adiutor) frequencies seem to scale a hell of a lot better so I'm not constantly changing frequencies depending on what I'm doing.

Again, thank ya! Much love, brother!
[ONE Original Android Development] andip71:
Questions:

- Impulse governor - why should it be included, what is so special and good with it?

- Underclocking - errm, you can underclock already both CPU and GPU?

- do you know the sysfs node for the sync threshold by any chance?

Thanks

Andi
[ONE Original Android Development] Neroga:
Impulse is pretty much conservative mixed with interactive. By default, low CPU loads are geared towards scaling on the lower frequencies so scrolling or reading doesn't immediately bump up the frequencies. Tends to stay under 1.4GHz unless you're doing something that requires the extra speed. Basically only uses what it needs to to keep everything running smoothly without lag. I usually set my max frequency to 2.88GHz but even playing games won't put too much time above 1.9GHz unless I'm playing a heavy game like Six Guns. Battery friendly while preserving fluidity and speed, and performance when you actually need it.

Unless I'm doing something wrong, it doesn't even show me an option to go below 300MHz for the minimum frequency as per the screenshot.

I actually have no idea what a sysfs node is lol. All the years I've spent tinkering and tweaking my phones/tablets have been purely by trial and error. No research whatsoever lol. I know the basics like swapping or editing files in /system and whatnot.
[ONE Original Android Development] Neroga:
Wouldn't let me attach it to my previous post.. [MENTION=947981]Lord Boeffla[/MENTION]
[ONE Original Android Development] andip71:
Ok, I will have a look at the governor in the next weeks.

True, underclocking below 300 MHz is not there. And will not be there. I had lower frequencies in a while ago and the results were not good. Same for stability. So I decided to not implement steps lower than 300 MHz anymore.

Ok, then I need to find that myself on the sysfs.

No worries

Andi
[ONE Original Android Development] andip71:
New beta

Hi guys,

new beta arrived for you.

Version

3.1-beta2

11.06.2015

Wifi drivers updated to LA.BF.1.1.1.c3-02800-8x74.0 (from CM12.1 nightly)

BFQ scheduler updated to version v7r8

Removed some compiler tweaks

ext4 tweaks commit time reduced

Changed kernel start script to optimize loading of default settings

Enjoy

Andi
[ONE Original Android Development] :
Flashing.. :)
[ONE Original Android Development] pchtc:
Flashed kernel.

Working well so far.

Will give all day tomorrow for proper test after full battery charge
[ONE Original Android Development] andip71:
New beta

Hi all,

before I disappear over the weekend, a last update. Just maintenance, but might be important for system stability, so I would recommend to flash it.

Version

3.1-beta3

12.06.2015

Kernel start script optimized again (apparently was too aggressive for some phones)

Enjoy

Andi
[ONE Original Android Development] Neroga:
Sorry to bother you, again. Would you possibly be able to add in the ability to disable hotplug boost and wake boost, as well? I've been racking my brain as to why the cores would immediately jump to the max frequency and kicking on more cores than necessary and noticed I was missing a usual step of mine is tuning the kernel lol. If not, would you happen to know where to manually change it?
[ONE Original Android Development] ZaneZam:
afaik that's not possible to setup, at least for the wake boost u would have to disable mpdecision but then u also disable all other things like thermal throttling etc. ;)
[ONE Original Android Development] jukyO:
Andi, it really does look promising:

http://xdaforums.com/showthread.php?t=3134872
[ONE Original Android Development] Neroga:
It's mainly the hotplug boost I'm looking to disable lol. I've got a wonderful setup I use with impulse or conservative. I've noticed a drop by about 1.5 hours SoT since I've been testing the difference between ROMs and kernels upon receiving my 1+1. The only way I've been able to, somewhat, counteract that is by dropping the max frequency down to what I have the input boost set to (1.19GHz). For now, I'm using Tasker to adjust the max frequency based on what apps are open (default at 1.19GHz, raised only for heavy games). Sorry for the long posts. Given the limited knowledge I have since I've done little to no actual research since I kicked iOS for Android back when the Atrix 4G came out, everything I've learned is by trial and error lol.
[ONE Original Android Development] Zach1928:
Hi all, I was wondering how people are faring with the stable 3.0 build. I've fixed the play services wakelock with tasker but Oxy's battery is still pretty lousy
[ONE Original Android Development] Neroga:
3.0 stable works well. Me thinks the 3.1 beta is better on battery life but don't take my word for it. I didn't stay on 3.0 long enough to make a decent comparison.

As for the play service wakelocks, flash the 5.0 gapps package from here http://xdaforums.com/showthread.php?p=60108493 . I've never had the wakelocks that people have described but again, I always flash one of those.
[ONE Original Android Development] acidburn94:
sorry which one have downloaded the one with caulckin's fix or which one? thanks :)
[ONE Original Android Development] Zach1928:
I haven't had any issues with wakelocks since using tasker. Also flashed the 3.0 kernel and so far so good. It's disappointing that Oxy is like half-baked.

Edit: Has anyone noticed any problems with pinch to zoom with 3.0? I've noticed that trying to zoom in on pictures gets buggy and everything jumps around resulting in a reboot to get it straight again
[ONE Original Android Development] pchtc:
wakelocks

Hi Andi

I have done some extensive testing over the weekend

I have relatively no play services wakelocks as i have already rebuilt my framework based on the article you were referencing by culkin

on any of the boeffla kernels i get a recuring wakelock for phone > RILJ

this happens every few minutes and is in to the 1000's of occurences by end of day

on the stock oos kernel there are no RILJ wakelocks at all

the information i can find on RILJ is that the OS is attempting to get a device location based on cell tower instead of GPS

I was in the same location on both days and can replicate the issue within minutes by flashing the kernels back and forth

hope this helps in identifying what they "oxygen team" may have left out when they released the source code
[ONE Original Android Development] andip71:
Thank you. Very interesting information.

But honestly I don't know what to do with it.

Because I don't know what Oxygen is doing. Whether the source code is not the latest version, whether something else is checked etc.

All I can do when I am on Oxygen again is: I try to see if I have the same finding.

Andi
[ONE Original Android Development] andip71:
New update

Hi all,

new update available.

Version

3.1-beta4

16.06.2015

Further kernel start script optimisations on ext4 tweaks and dynamic fsync

Enjoy

Andi
[ONE Original Android Development] andip71:
Ok, I am back on Oxygen now for the rest of the day.

Where did you see that RILJ wakelock showing up? BetterBatteryStats in Kernel Locks?

Or...?

So far I cannot see that coming up here at all. That is why I am asking to not overlook it.

Thanks

Andi
[ONE Original Android Development] pchtc:
i am using wakelock detector

in wakelock detector i go to the kernel usage instead of cpu usage

i get rilj wakelocks in the 1000's

but i have just read that it could be caused by the "Google Fit App"

apparently under the stock kernel the drain is there but dosent show as rilj

for some reason it seems to just be bound to google services and android os

you see, with stock, i get no rilj wakelocks but higher android os and g services

i have just uninstalled google fit and will try again after a full charge

i will report back today
[ONE Original Android Development] andip71:
Ok, good stuff, thanks.

Andi
[ONE Original Android Development] pchtc:
so far, so good

i am getting some rilj wake locks, but very little

a total of 9sec awake time

getting good deep sleep and 300

about 35% deep and 30% 300

the rilj that i am getting now is different

it is located under phone in cpu usage

i am on 3.1 b4

i will continue for rest of day, but looks good

---------- Post added at 11:38 AM ---------- Previous post was at 10:50 AM ----------

i think the issue is solved

i now have 73% deep sleep and 11% 300

i now have an estimated 24 hours remaining on battery but this morning only had 6
[ONE Original Android Development] pchtc:
ok so its been 3 days and everything is great

I regularly get over 24 hours (1 full day) on a charge

as a test i tried the stock kernel and cannot get such good results with it

it seems that boeffla only had an issue when an offending app was keeping it awake

for some reason stock dealt better with that offending app though

not sure why they both deal with it differently

either way boeffla is a better kernel under normal conditions without offending apps

it will remain my daily driver on my phone

thanks for this great kernel
[ONE Original Android Development] :
Great so far on beta4. Battery is very good, I'm using zzmoove - optimal with no further tweaks.

Now 24 hours on and 40% battery remaining. Moderate usage with 9h sleep so full standby.

Nothing negative to note so far :)
[ONE Original Android Development] misal6666:
the only missing feature is color control. please lord boeffla try to add that
[ONE Original Android Development] andip71:
Color control for rgb is in for a long time.

And I have no plans for any other color control for some internal reasons. At least not very short term.

What would you like to have and why? Give me good arguments, convince me ?

Andi
[ONE Original Android Development] andip71:
Ok, I decided to change my mind, so all the whining is over.

Next kernel will have KCAL V2 implemented.

Andi
[ONE Original Android Development] andip71:
Teaser attachend.

Andi
[ONE Original Android Development] andip71:
New beta

Hi all,

a new beta arrived.

Main changes: Color control v2 is now implemented (credits to Savoca), note you need latest Boeffla-Config App in version 2.1.86!

Also a new governor has been added: impulse governor

Version

3.1-beta6

22.06.2015

Color control V2 implemented (you need Boeffla Config App 2.1.86 or higher) - credits to savoca

impulse governor added (Click here for more info)

Note: beta5 was skipped to be in line with CM kernel versions again

Enjoy

Andi
[ONE Original Android Development] :
Flashing now :)
[ONE Original Android Development] pchtc:
on beta6

getting great results with impulse

1day 8hours remaining as compared to about 24 hours with interactive
[ONE Original Android Development] saikm:
have a good trip
[ONE Original Android Development] Lazy79:
[MENTION=947981]Lord Boeffla[/MENTION] have a really great vacation and enjoy it! :)

I just tried to build from the kernel source myself but x-settings.sh is not found and I cannot find it either. take your time when you are back! :) It is not so important, but if you could help me out here, would be great. next week is indeed ok lol enjoy your time!
[ONE Original Android Development] :
So far so good on beta6. Seems really stable to me, I hope other testers can confirm this :)