yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
You mean an app setting to reboot into recovery after load&flash?

If that is what you mean, I could do it.

However, I would recommend to not use SuperSu in systemless mode (if this is possible, not sure). Or even better, keep fingers away completely from supersu but use CM internal superuser. Then all that hassle is over completely.

Andi
[ONE Original Android Development] Orphee:
http://xdaforums.com/showpost.php?p=66140836&postcount=5493

Edit :

echo "SYSTEMLESS=false" > /data/.supersu

echo "BINDSYSTEMXBIN=true" >> /data/.supersu

Then flash again Supersu V2.71
[ONE Original Android Development] andip71:
Jupp, I know how it can technically be done.

But when I tried it on COS13, it always made me ending up in a bootloop.

Andi
[ONE Original Android Development] Orphee:
I just did it and no bootloop
[ONE Original Android Development] andip71:
Even better, which supersu version did you use?

Andi
[ONE Original Android Development] Orphee:
v2.71

By default it flash with systemless mode, but with the 2 lines in /data/.supersu it flash in "compatiblity" mode.

echo "SYSTEMLESS=false" > /data/.supersu

echo "BINDSYSTEMXBIN=true" >> /data/.supersu

then flash v2.71 again

Now two apps works again :D (ProxyDroid and EDS)
[ONE Original Android Development] andip71:
Ok, I did not do the BINDSYSTEMXBIN, maybe that is why.

But I anyways prefer CM superuser much over SuperSu, so I am fine.

Thanks for letting us know though, very helpful.

Andi
[ONE Original Android Development] kryshnakishore:
Entered piece of code in terminal, flashed su 2.71,no bootloops, no conflicts but supersu has no system level root, i don't know how it worked for u... Finally back to normal CM su
[ONE Original Android Development] DjDiabolik:
mmmmm.. but the recent cos13 OTA (otherwise i stay to wait full official zip file) contain the CM su ?
[ONE Original Android Development] andip71:
No. Cos never comes with su.

It is not allowed to get Google certification.

Andi
[ONE Original Android Development] hellcat50:
That would be too good to be true
[ONE Original Android Development] andip71:
I don't understand?

Andi
[ONE Original Android Development] hellcat50:
I mean pre-rooted devices. You said that Google does not allow that.
[ONE Original Android Development] andip71:
That would never happen.

Every rom that wants to include gapps needs to be certified by Google. So no root possible.

Andi
[ONE Original Android Development] Orphee:
Did you manage to enable usb debugging on COS 13 ?

It don't work for me... never show the popup windows to authorize usb connexion... any idea ? :/
[ONE Original Android Development] DjDiabolik:
Also i already know this situation.... at this point on cos13 we need force to use supersu .zip and i don't understand if we need to reflash every future kernel upgrade :)

Sorry again for this stupid question but you affermation about CM su have create some confusion in my head :)
[ONE Original Android Development] Manholas:
When the Support built-in CM superuser for the CM13?
[ONE Original Android Development] andip71:
CM13 supports in-built superuser since day one, same goes for my CM13 kernels.

I do not know what your question is really about.

Andi
[ONE Original Android Development] Manholas:
Forget the question. Thanks for your work.
[ONE Original Android Development] Aavion:
After some further testing, I reverted back to stock kernel for now... It feels smoother and more stable than Boeffla Kernel on COS 13... Also battery seems to be better on stock kernel (all Performance/battery related settings untouched, except input boost LOWERED to 960).

Dunno what's wrong, but as of now, I'm pretty happy with COS13 absolutely stock :D Even unrooted again (even if I miss adaway a lil bit :D )

[MENTION=947981]Lord Boeffla[/MENTION] I've got no debug info for you, but I used stock settings except: input boost lowered, led speed adjusted and headphone gain increased. With your kernel, the screen is slightly less responsive, small micro lags every now and then, laggy bootanimation ( :D ), small delays in audio output, noticable when turning audiofx on and off or "liking" comments in the facebook app (that small sound sounds a bit buggy and distorted as it's routed through audiofx and you clearly hear the delay until the fx kicks in, haptic feedback while typing feels a bit less responsive, also (like it was a bit delayed). Nothing major, I wouldn't really notice these things if I couldn't directly compare the kernels' behavior, but for now, stock seems better optimized, as it's running rock solid and fluid... not a single lag or stutter or delay... runing it now and it feels like a brand new device :)

Maybe you've got an Idea, as I slightly miss my beloved headphone gain and led settings, but for me it feels much better, to see my phone running THAT smooth and stable for the first time in it's lifetime :D
[ONE Original Android Development] andip71:
No problem at all.

Whatever it is/was - I have nothing of the mentioned here.

So I can anyways not help.

Andi
[ONE Original Android Development] KaszasM:
can confirm the audio"latency" feels like it would connect the hardware slower/later. ,ex:(got lot of voice commands on daily use) and if i trigger google voice(need to launch manual, "ok"google dosnt supports hungarian atm) and 90% the start"beep" is not routed over bt to my carkit, but actually its routed just too latecan here the "endbeeptone" sometimes, 10%happens the same on my phone speaker ...just to tell on my sec. opo is rr cm13 rom and same "voicechannel|device" turns to late "bug"?
[ONE Original Android Development] andip71:
I would be super surprised when this is not the same on stock kernel.

Andi
[ONE Original Android Development] andip71:
[MENTION=361312]aavi[/MENTION]o:

Maybe, as you are currently on stock kernel anyways, could you please do me two favors?

Post what the following command gives you back in a terminal window:

cat /proc/versions

And could you also tell me the governor tunables of interactive you can find in

/sys/devices/system/cpu/cpufreq/interactive/...

Just want to check if something here has probably changed compared to COS12.1.1 / CM13.

As said, the code I put in is 99,99% the same as CM13 or COS12.1.1 (I use my same code already for almost a year with only adaptions). So I doubt very much something would cause lags etc.

Anyways, I can quickly check this when you sent me the outputs. But if this is not showing anything interesting, I will not dig further into that anymore.

Cheers

Andi
[ONE Original Android Development] Aavion:
/proc/version:

Linux version 3.4.110-cyanogenmod-g7808b1e (build02@cyanogen) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Apr 1 15:27:44 PDT 2016

/sys/devices/system/cpu/cpufreq/interactive/...

above_hispeed_delay:

20000 1400000:40000 1700000:20000

boost:

0

boostpulse:

Access denied.

boostpulse_duration:

80000

go_hispeed_load:

90

hispeed_freq:

1190400

io_is_busy:

1

min_sample_time:

40000

sampling_down_factor:

100000

sync_freq:

0

target_loads:

85 1500000:90 1800000:70

timer_rate:

30000

timer_slack:

80000

up_threshold_any_cpu_freq:

0

up_threshold_any_cpu_load:

0

Edit:

[MENTION=947981]Lord Boeffla[/MENTION] That "lags" are barely noticable ^^ Not a major thing... Your Kernel is still awesome (:

Best and easiest way to see the difference I was talking about: Use CM Theme Engine to set a well animated bootanimation (MidnightBlue's bootanimation is the one I am using for example). As during boot no custom settings are applied, it's a pretty good timeframe to see a difference, as both kernels should behave similar ;)

Flash stock kernel and look at the bootanimation.

Then flash your kernel and compare...

With your kernel, I see the animation slightly stuttering, but when using stock kernel, everything is smooth as heaven :)
[ONE Original Android Development] lchiocca:
Wow! We're getting zram on bacon!

http://review.cyanogenmod.org/#/c/140688/
[ONE Original Android Development] andip71:
When I see the commits in total, it will be even zCache.

Well well, I am not a big fan of that, honestly. But I will follow CM for now.

Andi
[ONE Original Android Development] lchiocca:
Wait a minute... zCache?! Isn't zCache:=zSwap+compression? Where is it going to write the swap to?! or is it a zRam with compression. I just hope the later.
[ONE Original Android Development] Aavion:
zRam IS a compressed swap partition within RAM.

Whereas zCache is a compressed page- and swap cache partition (afaik everything with z-prefix means it's compressed :D )
[ONE Original Android Development] Matteo_666:
Nightly is available already, anyone tried yet?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Crazy_Oni:
Im on it since the release. Camera focus and recording are broken with all camera apps. Focus is working for me on color os oppo cam but video recording dont save the video on any app.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] usmani:
I also had those stutters especially when switching between heavy apps like chrome rapidly and delay in screen response, but non are on stock kernel. Didn't report it because I didn't know how to provide logs for such a situation.

Btw I've been having them since cos 12.1 not just cos13
[ONE Original Android Development] andip71:
There are no logs for that.

So just use stock kernel then if this is an issue for you.

Andi
[ONE Original Android Development] Aavion:
Did you try the bootanimation-thing I suggested?

(look at the "edit" part of my posting about the values you requested... btw: did they help in any way?)
[ONE Original Android Development] kryshnakishore:
Off topic :

Privacy guard shows phone is awake while charging phone(location service) is waking up only while charging.. Anysolution?

1.i have disabled screen awake in dev options

2.i am using original charger

3.i am on latest cos13

4.while charging screen is completely off & no background apps running (greenifyd)

Even wakelock Detector also shows phone awake.. How to disable??
[ONE Original Android Development] cloudx720:
Kernel not playing well with cos13 Andi?
[ONE Original Android Development] infatality:
[MENTION=947981]Lord Boeffla[/MENTION] Now that cm13 has introduced zram etc. Is it possible for you to add an option to your kernel app for zram related settings? I understand you may not be a fan of zram related stuff but I hope some advanced users could benefits from that. [emoji1]
[ONE Original Android Development] Aavion:
Phone doesn't need to enter deep sleep while charging... So it doesn't matter ;) But I remember that behavior being working as intended for a long time now. I first noticed the phone staying awake while charging in Android 4.3, but it may be present in older versions, too...

Don't worry...
[ONE Original Android Development] kryshnakishore:
I am on latest version cos13, no issues i faced in cos12.1..phone is getting heated alot while charging so it issues for me. Any possible way to keep phone(location) service to disable

---------- Post added at 09:00 PM ---------- Previous post was at 08:54 PM ----------

Yes for me too but still love using Boeffla-Kernel
[ONE Original Android Development] atulclassic:
no such issues here..highly stable

although battery drain is quite fast in comparison to COS12.1.1 kernel but since it is in early stages of development that too without the source being released..i am happy with what i got
[ONE Original Android Development] kryshnakishore:
Wakelock Detector shows while charging these two are awake

1.qpnp-charger-ee254800

2.PowerManagerService.Display

Any solution for this??

---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------

Wakelock Detector shows while charging these two are awake

1.qpnp-charger-ee254800

2.PowerManagerService.Display

Any solution for this? Phone is getting heated while charging because of them
[ONE Original Android Development] andip71:
Have not yet tried it, as I am not on COS13 at the moment. I am most of the time on CM13. But once I am back on COS13 I will try.

The mentioned bootanimation - what theme does include it?

Says who? I would say, it is playing exactly as nicely as COS12.1.1. kernel.

Which would make sense, as it is 99% the same code.

You have been told already by another user above, during charging the OnePlus One sets a wake lock.

This is normal behaviour and you have to just live with it.

(and just to say, when your phone is on charger it does not matter if the phone is awake or not, it makes almost zero difference, thats what it is like that.

BTW - this was already the case with all my other mobiles (Galaxy S3, N8000), so I do not understand why you want to change normal behavious or what bothers you with it)

Andi
[ONE Original Android Development] Aavion:
MidnightBlue from Playstore... But other's too have this "stuttering"... But with this one (circular Animation) it's easy to notice..

btw: i've replied to your pm :)
[ONE Original Android Development] andip71:
Ok, I looked at it.

So far I have decided in the first step to take over the default CM zRam of 509 MB.

So we can see how that behaves over the next weeks.

However, for those that do not want to use any zRam, it can be disabled in settings -> kernel startup options.

So, currently it is switchable - on and off.

Maybe in further future, when we gained more experience how it behaves, I will make it fully customizable.

But my first tests indicated, it is almost not used at all (as expected). Hence I want to see it a bit longer...

Thanks, have seen your reply. I am very busy today, but will certainly come back to you soon.

And - I tried this boot animation. Either my eyes are too weak already or I just don't have it (to be fair, I only tested on CM13 so far, not COS). We will see when I do some tests with you.

Andi
[ONE Original Android Development] Stroky:
Im also very interested if the zram brings an improvement for the bacon.

In the theory I would say no, but the guys from cm have something in common with that I gues

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
CM13 kernel update

Hi all,

CM13 kernel update, as promised:

Version 5.1-beta16

18.04.2016

Change: CM now uses zRam of 509 MB size by default -

if you do not like that, you can switch it off in Boeffla-Config in "Settings -> Kernel startup actions -> Disable default zRam" (reboot required)

Update: Updated with latest official CM kernel commits as of 18.04.16, 10am CET (incl. added zRam and new Wifi drivers etc.)

Update: Ramdisk of official CM13.0 build of 18.04.16

Enjoy

Andi
[ONE Original Android Development] suaverc118:
What does the zRam 509 do differently for our device?
[ONE Original Android Development] andip71:
It extends the 3 GB physical memory by putting a dynamic swap devices in a compressed area of the memory.

So in theory, more data can be put in memory with some small performance it doing compression/decompression.

However, I am not a fan of that. I still have the opinion 3 GB physical ram is more than enough still. So don't know why they have implemented it (their comment was: improve when device runs for long time).

I switched it off straight away in the app :)

zRam already on other devices in the past was never a solution, just a workaround. And I do not see this required on the OPO still.

Andi
[ONE Original Android Development] Stroky:
When im right, zram also consums more battery, right?

Gesendet von meinem SGP511 mit Tapatalk
[ONE Original Android Development] suaverc118:
Thanks bro
[ONE Original Android Development] andip71:
Well, not noticeable honestly.

Ok, it needs to compress/decompress data many times, yes. But it does not really make a significant difference.

Andi
[ONE Original Android Development] hellcat50:
Enjoy your xda ad-free, my contribution to your hard work!
[ONE Original Android Development] andip71:
Updates to COS13 and CM13 kernels

Good afternoon,

thanks to CM, who pushed lots of code again last night, new updates today :)

CM13.0 -- Version 5.1-beta17

19.04.2016

Update: Updated with latest official CM kernel commits as of 19.04.16, 10am CET

(this also includes the change to increase timer HZ rate from 100 to 300)

Update: Ramdisk of official CM13.0 build of 19.04.16

Change: Kernel information message (displayed after every flash in Boeffla-Config) removed

COS13.0 -- Version

5.0-beta3

19.04.2015

Fix: Broken adb root fixed

Change: LED control driver prepared to support some upcoming functionalities (too early to disclose details, sorry)

Enjoy

Andi
[ONE Original Android Development] Stroky:
Really interesting that cm also changed the timer rate for the one!

I found it really good that Google did it with the nexus 6 a few weeks ago!

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
I really wonder what is means in terms of

- smoothness / performance

- battery consumption

Time will tell us.

Andi
[ONE Original Android Development] Orphee:
Thank you !!!

adb was completly broken for me ! Now it works !
[ONE Original Android Development] andip71:
And to get a better grip on that, I ported the 300 Hz change also to a (not official) test version of the COS13 Boeffla-kernel.

Just to let you know, I am testing it a bit more here :)

Andi
[ONE Original Android Development] Aavion:
Do you see any advantages of this up to now?
[ONE Original Android Development] andip71:
I have not used my phone a lot since then.

I also ported it for the Galaxy S5 kernel (and for the OPX), and two testers on the S5 report slightly increased performance.

We will see...

Andi
[ONE Original Android Development] andip71:
COS13

Sooooooo, I think I mentioned already a while ago, COS13 is currently a no-go as daily for me.

Reason: COS13 is missing the configuration of the notification LED for the do-not-disturb mode. While this is possible in CM13 and also in the older COS12.x versions, they have removed it.

But I NEED the notification LED to be disabled when I am on DND during the night.

So I worked in the past days to write a small companion app that emulates that behaviour again - "Boeffla DND Helper". And the app required this mysterious extension in the kernel which I did not more detailed disclose in the latest kernel change log.

To cut a long story short: I am currently testing this little app and if it runs fine, I consider making it availabe on either Play Store (yes, the app has nothing relevant in which could make Google blocking it) or via my homepage.

But first I need to verify it does exactly what I want in all cases.

Screenshot is attached.

Have a nice evening!

Andi
[ONE Original Android Development] andip71:
Experimental test kernel with changed HZ rate !!!

Hi all,

as you might have heard, I was experimenting with a kernel change Google recently released for the Nexus 6P also on our device.

The change is about bumping the internal kernel tick rate to 300 HZ (from 100). See here:

http://www.ibtimes.co.uk/nexus-6p-o...nectivity-improvements-well-bug-fixes-1548908

And everyone being interested can join this test as well. Just go to the kernel download folder, you will find a sub folder there called "HZtest". This is the latest kernel, just having the HZ change in.

On Bacon, this is available for COS13 and COS12.1.1 - CM13 has this already built-in officially by CM.

During or after testing, please let me know your personal result by attending the following poll:

http://www.easypolls.net/poll.html?p=5718f105e4b0c242dab233f6

Please note - you test this on own risk. This kernel is absolutely experimental.

I cannot guarantee full stability of that change, although I have not encountered anything bad myself.

Enjoy testing some new fancy stuff :)

Andi
[ONE Original Android Development] Promez:
Can I ask what should improve this change?

Or better what really means the kernel tick rate?

I always like your explainations[emoji14]
[ONE Original Android Development] Arunraj Nayak:
[MENTION=947981]Lord Boeffla[/MENTION] Sorry for bringing this up again!

When I set charge rate to stock logic i.e. 0, the charge rate drops to 500mA for wall charger. Not sure if its something to do with charger.

Also, if I set to higher values in App, charge rate increases. But many times, even though if I set it to 1800, I observe very slow charging. At that time in app's first page shows charge rate as 100/150. I have to disconnect and reconnect the charger to solve that every time.

Need some guidance.:confused:
[ONE Original Android Development] andip71:
Look here:

http://xdaforums.com/showpost.php?p=66479509&postcount=146

Andi
[ONE Original Android Development] andip71:
I would need a crystal ball to know what happens.

Kernel code is unlikely, as this is pure stock charging driver when set to 0.

So can be faulty cable, faulty charger, dirt in the connectors, defective charging circuit on the phone.

But also do not trust the charge rate display a lot, as I explained long ago, it can be super inaccurate (I even removed it for a while...).

I really do not know more.

Andi
[ONE Original Android Development] Aavion:
Wow, feels very good :) Thanks.

First impressions: Feels smoother and a bit more responsive than b3 on COS13. No performance improvements (in games via fps measure).

For battery life time will tell...
[ONE Original Android Development] Promez:
thank you! very interesting reading
[ONE Original Android Development] atulclassic:
[MENTION=947981]Lord Boeffla[/MENTION]..currently i am running COS12.1.1 with your kernel 4.2 beta 9..but today i see another kernel in your folder without any number..is it the same kernel as beta 9 or changed?

PS : I am not asking about the HZtest kernel
[ONE Original Android Development] andip71:
Screenshot please? No idea what you exactly mean.

4.2 is already released stable for a long time. So beta9 is clearly not the latest version anymore.

Andi
[ONE Original Android Development] kewinhdorff:
can i use this cm13 stable 5.0 kernel version on my cm snapshot which was released 04-19-2016 ? or do i need to download the test version ?

also if i download the test version what if i want to change to the later stable versions ? do i just dirty flash over it ?
[ONE Original Android Development] kryshnakishore:
U can use any version both are working fine for me and u can revertback from test to stable version. Make sure you have the right zip
[ONE Original Android Development] kewinhdorff:
okey thanks :) and if i want to switch back to cyanogenmod stock kernel ? do i only need to flash the cm 13 snapshot ?
[ONE Original Android Development] kryshnakishore:
Wait what? Cm & cos are different if u use cm rom then flash cm kernal (stable/test).. If u use cos rom then flash cos kernal (stable/test).. We can't inter change kernals for cm&cos. Make sure u flash right zip.. And yes if u want stock kernal u can revert to stock kernal no need to flash entire rom. Stock kernals can be found at our boeffla-kernel website
[ONE Original Android Development] kewinhdorff:
i know cm and cos are different im on cm rom i tried to install the boeffla kernel 5.0 stable on the 04-29 cm snapshot. bootloop :/ didn't even get to the rom bootlogo.

so im charging my phone and will try if the beta 17 will work
[ONE Original Android Development] kryshnakishore:
Ok cool
[ONE Original Android Development] kryshnakishore:
New update for cos13 :

https://forums.oneplus.net/threads/new-cos13-znh0eas2jk-update.443376/
[ONE Original Android Development] molonad:
I Dont want to change to stock recovery to flash that, is it possible with twrp? Thanx. But still i Will wait till Mistr boeffla will have new version and new kernel done ?
[ONE Original Android Development] kryshnakishore:
With twrp we can't flash it, just flash recovery image & update the zip. After updating u can flash your twrp.. No boeffla has nothing to do with these incremental update u need to flash update.. Boeffla makes kernal update, even to install new kernal u need to flash this zip first
[ONE Original Android Development] molonad:
So i Will have to use twrp to flash stock recovery? And then update cos incremental update? And after update i Will be possible to flash twrp in stock recovery? I Dont use stock recovery from day one - 2 years. Thank you