yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] dkryder:
thanks for that information. i spent about an hour with adb shell possibilities but none would work for me. they all ended like this, to be honest i'm not well versed in this yet

shell@A0001:/ $ su

1|shell@A0001:/ $ mount -o rw,remount rootfs /

mount: Permission denied

--------------------------------------------------------------------------------------------------

C:\Users\douglas\AppData\Local\Android\sdk\platform-tools>adb push -p C:\Users\douglas\AppData\Local\Android\sdk\platform-tools\bacon.cm13\cm-13.0-20151124-NIGHTLY-bacon.zip /storage/emulated/0/Download

Transferring: 336240534/336240534 (100%)

failed to copy 'C:\Users\douglas\AppData\Local\Android\sdk\platform-tools\bacon.cm13\cm-13.0-20151124-NIGHTLY-bacon.zip' to '/storage/emulated/0/Download': Read-only file system

-------------------------------------------------------------------------------------------------

root@A0001:/ # su

root@A0001:/ # mount -o rw,remountfs /

Usage: mount [-r] [-w] [-o options] [-t type] device directory

------------------------------------------------------------------------------------------------

i'll be real happy if i find out the main problem was something in the ROM that needed fixing more than what my commands were.

anyway, nice work. thanks.
[ONE Original Android Development] andip71:
You didn't do what I said :)

On your PC in the command shell, do NOT go for "adb shell", but just type "adb remount" instead. That is all.

Andi
[ONE Original Android Development] laura almeida:
Yes, It does well with Beta3

I can confirm that!

Thankx my Lord
[ONE Original Android Development] acuicultor:
Hi Lord, i sent you a pm regarding permission. I'll wait for your answer. Thanks in advance.

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] KenjiHannya:
Amazing combo

https://plus.google.com/+JPKenji/posts/M34HZe3vvXv
[ONE Original Android Development] Mecca EL:
[MENTION=947981]Lord Boeffla[/MENTION], Swipe to wake isn't working on VM13. Other than that, thank you so much for the awesome beta.
[ONE Original Android Development] andip71:
Confirmed.

There are more issues due to the fact with cm13 the system partition can't be mounted rw.

This breaks certain functionalities of the Config app where this is required.

Next app version will check that and remind you as long as this is the case.

Andi
[ONE Original Android Development] SanOne+1:
I am using Calkulin's OnePlus One v3.7 based on CM12.1S - YOG4PAS3JL

and stable COS12.1 kernel

yesterday, I changed governor zzmoove- battery saver yank extreme.

My phone gone into bootloop
[ONE Original Android Development] andip71:
Flash reset zip in recovery and chose another profile. Seems this profile is too aggressive for your phone/setup.

Andi
[ONE Original Android Development] andip71:
Guys with CM13....

Good news!

I will release beta4 very soon, this enables system partition to be writable again with a workaround.

Means: Many tools that need it (like Adaway etc.), as well as Boeffla-Config, should be working fine again.

So - stay tuned!

Andi
[ONE Original Android Development] andip71:
Beta4 for CM13 out

Good morning,

full speed on CM13 still.

The reported sweep2wake issue is fixed now, and I found a workaround to have the system partition rw again (writable). So apps like Adaway, DPI changer, etc. etc. as well as some functions of Boeffla-Config will work properly again.

Note: This is only a workaround as the system partition is now mounted rw all the time. In worst case scenarios this could imply a minor security implication, although I cannot really think of any. But you have been warned.

Version 5.0-beta4

26.11.2015

Fix: Swipe2wake working again

Workaround: System partition is now mounted rw (writable), this makes apps like Adaway and others that need to write to system partition work again. However, this is only a workaround until a proper solution for CM13 is in place by CM team! This workaround will keep your system partition mounted rw all the time, which could have minor security implications in worst case.

Update: Ramdisk updated to official CM13.0 version of 26.11.15

Enjoy

Andi
[ONE Original Android Development] brisac:
Will this cm13 kernel work on omni rom?
[ONE Original Android Development] Stroky:
No, because it is not cm based!

Omni is based on AOSP
[ONE Original Android Development] Calvin2394:
Any plans on supporting the OnePlus X? :)
[ONE Original Android Development] andip71:
I do not have one. And I also do not plan for one.

So currently the answer is No.

Andi
[ONE Original Android Development] dkryder:
hello,

i flashed the 11/26 cm13 bacon and then the beta4 and it seems you have taken care of the mount /system rw problem. adaway had no difficulties as well as better battery stats and build.prop editor. Whatever you did works well on my device. Thank you.
[ONE Original Android Development] andip71:
Yes, that what I explained in the change log for beta4 with:

Workaround: System partition is now mounted rw (writable), this makes apps like Adaway and others that need to write to system partition work again. However, this is only a workaround until a proper solution for CM13 is in place by CM team! This workaround will keep your system partition mounted rw all the time, which could have minor security implications in worst case.

Andi
[ONE Original Android Development] Mecca EL:
Once again, everything is running beautifully. Swipe to Wake feels smoother than on COS12.1 . Thanks [MENTION=947981]Lord Boeffla[/MENTION]
[ONE Original Android Development] cloudx720:
COS13 won't be long maybe? :D
[ONE Original Android Development] andip71:
No clue. Only the dev team at CM knows I guess.

At least I have not even started working on a COS13 kernel as there is nothing to test against...

My belly feeling says, earliest in February 16.

Andi
[ONE Original Android Development] noahvt:
The boeffla config app still doesnt work for me, keeps saying kernel version / busybox issue, busybox is installed, and I have today's kernel running
[ONE Original Android Development] Mecca EL:
From what I've read, COS reached EOL at 12.1, and from here on out there's just CM13+. They've even ported COS apps over to CM.
[ONE Original Android Development] andip71:
You have todays nightly installed?

You have beta4 of today installed?

You have SuperSu 2.52 installed?

You have Boeffla-Config 2.2.11 installed?

You should not install a custom busybox on CM, everything needed is there. This might be the issue even (especially when you use Stericson busybox which deletes other busyboxes during start - so Boeffla cannot find its busybox anymore)

Andi
[ONE Original Android Development] Pablo.x:
I'm facing a weird bug.

Mobile data doesn't turn on when I enable it after disabling wifi.

May be kernel related or just ROM related?

Running 26/11 nightly + boeffla beta 5

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] andip71:
Cm13 is 3 days old for the opo.

So these kind of bugs and glitches are to be expected.

Switch airplane mode on and off. That is what works for me. At least a workaround.

The whole switching between mobile data and wifi is still slow and bumpy.

Andi
[ONE Original Android Development] Pablo.x:
Yay, that works!

Little fix, just wanted to know if it was just me...

Thanks Andi!

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] Arunragav:
[MENTION=947981]Lord Boeffla[/MENTION], really appreciate the recent update for cm13, inclusion of changing selinux mode is awesome, system partition is also unlocked..... a big hug to u and kudos :good:
[ONE Original Android Development] infatality:
Source? OPO has stated our device will get COS 13 from cynogen some time in January.

https://forums.oneplus.net/threads/marshmallow-upgrade-schedule-for-oneplus-devices.406778/
[ONE Original Android Development] Rahulrulez:
He means official CM13 nightlies
[ONE Original Android Development] magnamentis:
official cm13 nightlies for OPO are already out, hence they cannot be meant to be released in january if they were released already now in november
[ONE Original Android Development] xlollomanx:
I think he's talking about of cm13 snapshot, a stable release of cm13, that will be released in January.

Sent from my Oneplus One
[ONE Original Android Development] thedoctor.gz:
Today's build 11/27 is a little bit more stable, but I think not so much for a daily use.

[MENTION=947981]Lord Boeffla[/MENTION]: do you think CM12.1 will be updated anymore and your 4.x kernel too?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
I do not know if they release further 12.1 builds. Maybe.

If new builds come that bring changes, I will update the kernel again. Clearly.

Andi
[ONE Original Android Development] thedoctor.gz:
Great! Thank you :)

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
Heads up

Guys,

quick heads up... in todays gerrit, a patch to fix the system partition remount error was contained.

So I compiled a CM13 with that fix just now and voila... the problem is now really gone.

So, with tomorrows nightly, this big problem should be finally history and I can remove my workaround again in a few days :)

Just wanted to let you know already now about it.

Andi
[ONE Original Android Development] redbull1:
I use beta 4 with vm 13 build today. All works smooth. Good job andi.

Gesendet von meinem A0001
[ONE Original Android Development] vinman12:
I implemented that commit into my build this morning all worked fine after that.
[ONE Original Android Development] Rahulrulez:
Waiting for next nightly and next kernel upgrade.. Only problem bugging me right now is quick data <-> wifi switch. :D good progress
[ONE Original Android Development] Spaulding89:
Nightly is there but no new Kernel [emoji1]

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Current kernel is still working fine.

Monday next kernel release...

Andi
[ONE Original Android Development] andip71:
Surprise !!!

Good evening,

found some time today, so I was working on a CM13 kernel update.

Here we go:

Version 5.0-beta5

26.11.2015

Note: You

HAVE TO

use nightly 28.11.2015 or newer (where the system partition rw issues has been fixed)

Updated with latest official CM kernel commits as of 28.11.15

Removed system partition rw workaround of beta4 as the issue is now officially fixed in nightly of 28.11.2015

Update: Ramdisk updated to official CM13.0 version of 28.11.15

Enjoy

Andi
[ONE Original Android Development] cloudx720:
Hey Andi are you personally gonna wait for cos13 or you using cm13 nightlys? ?
[ONE Original Android Development] andip71:
I have two OPOs.

My daily driver runs under COS12.1. This will not change before COS13 comes.

Andi
[ONE Original Android Development] Spaulding89:
Today is monday?? Damn i missed the weekend :p :D

Thanks for the Update everything is great
[ONE Original Android Development] KaszasM:
[MENTION=947981]Lord Boeffla[/MENTION] now i got to ask should i update the config app or not? got the 07 release, i saw the post here earlier but you wrote it should be clean (didn't find the post now) because of the changes.... our the changes are general for the cm 13 thanks for the support. and again asking only for the config app
[ONE Original Android Development] andip71:
The Config app can and should always be updated.

Unless I say different, it is always compatible with all my kernels.

Andi
[ONE Original Android Development] Rahulrulez:
I flashed recent nightly with beta 5.. R/w is working fine now.. (tested with Gsam battery monitor root permissions).. Is there any way to get SuperSU work?
[ONE Original Android Development] dnikogosyan:
Guys, I know this is probably rom related but I'm hoping maybe some of you can help me, I started using official cm13 with boeffla kernel (thank you Lord))all the latest and I get 14% drain overnight.. I would be OK if something like an app was causing the drain. Any way the stats speak for themselves. As you can see the phone is asleep, but the drain is high.. And Cyanogen mod system is the cause, anyone else has this?
[ONE Original Android Development] andip71:
By the way: I am just compiling beta8 now for my internal tests.

For a quick teaser, change log will be:

zzmoove hot reboot issue hopefully fixed (ZaneZam worked hard during the weekend to pinpoint the issue and fix it, fingers crossed - all credits to him)

AC charge rate default changed from 2100 (which is faster than normal charging) to 1500 (which is slower) for increased battery lifespan (as we cannot replace the battery, I thought this might be better this way)

3 governor profiles for interactive in a very first version (battery, battery extreme, performance) - but those require for sure some more fine tuning over the next weeks

Andi
[ONE Original Android Development] RobbieL811:
Ok. I guess I will be left to init.d for now. Maybe I can talk APB_Axel into adding the need sys paths to UKM so values can be set with Synapse. Is there no other way to set Boeffla sound parameters for Bistros Sound Control that is not in your kernel?
[ONE Original Android Development] andip71:
Bistros Sound Control? What is that?
[ONE Original Android Development] RobbieL811:
Lol stupid auto correct! Boeffla sound control.
[ONE Original Android Development] andip71:
Haha. autocorrect is really funny, yes.

Well, I do not know. I always provide my kernels with my own app to control everything, so the whole package works.

But of course it would be rather simple to address the sysfs for Boeffla Sound directly by any other app. Let me know via if you need support to spot which ones you need to set in which way. It is currently only 3 of them active on the OPO.

Andi
[ONE Original Android Development] RobbieL811:
Ok. Awesome. I will look into more tomorrow after work. Maybe I will get with the dev of Synapse then too. I think that all he needs is the sys paths. If I can't figure them out, I will get with you tomorrow. Or you can message me to them if you have them handy. It is 1:30 am here though and I have to be to work in the morning. Stayed up to fuc**** late again messing with Android!!!!!!!!
[ONE Original Android Development] andip71:
New beta

Good morning all,

beta8 is on the line for you, both cm11s and cm11 kernel variant.

Most important: It contains a fix for zzmoove that should avoid triggering hot reboots. Fingers crossed and thanks to ZaneZam for spending his whole weekend working on it.

Version 2.0-beta8

03.11.2014

zzmoove governor updated to 1.0-beta2, should fix hot reboot issues (credits to ZaneZam)

3 governor profiles for interactive added (battery, battery extreme and performance; please note, battery extreme could make your phone a bit laggy) - these is the first set of profiles for interactive, expect some finetuning of it over the next weeks

AC default charge rate lowered down to 1500 mAh (from 2100 before, stock is 2000) to increase lifespan of your battery; I think this might make sense as we cannot replace the battery of the OPO

Enjoy

Andi
[ONE Original Android Development] andyfmking:
Good job my friend, beta 7 on CM11s 38R with ondemand governor @ 2.5GHz with the rest set to default. Great performance, testing battery but so far much better battery than Franco's latest kernel. I like a phone that responds as soon as I want it to and this is it. ? Well done. Screen response is sweet as candy ?
[ONE Original Android Development] andip71:
Thanks for the feedback. Promising... :)
[ONE Original Android Development] BrunoNRG:
Yes, I tried ak and fk kernels before, but I ended up choosing yours because I'm more used to the config app, I also used it on my S3 ;)

After I fixed the wifi problem, I flashed beta7 and everything seems to be working great, and you released a new version, beta8, already :D

Thanks for all the amazing kernels :good::good::good:
[ONE Original Android Development] NickosD:
Did I missed something? I flash rom again because I had ak and then the kernel, but no WiFi.

---------- Post added at 02:13 PM ---------- Previous post was at 02:13 PM ----------

Beta 8 and 29/10 pa saber rom
[ONE Original Android Development] andip71:
You probably missed, beta7a and beta8 are only for roms which base on nightly 01.11. or newer.

If you are on a rom which was built 29/10 (as you write), you need to still use beta7 (without a) as the rom is too old for the kernel.

Andi
[ONE Original Android Development] cerealguy:
[MENTION=947981]Lord Boeffla[/MENTION] even with beta8 I have problems with video rec... Anyone else? :(
[ONE Original Android Development] [armitage]:
Just made a minute long vid, with latest beta 8 kernel on latest temasek rom.

Worked fine.
[ONE Original Android Development] cerealguy:
Ok.. Thanks.. It's a LiquidSmooth problem...
[ONE Original Android Development] Franc38:
I did flash the latest (beta8) on CM11s38R and I still have my problems with wifi (which seem not to be the same as most...).

I can turn wifi on and off, but the speeds are dreadfully low if existing at all.

I did reflash the "restore stock wifi firmware" which solved (a bit) my woes, but there's still a sort of "struggle" to get the wifi data coming... I'll test more extensively tonight with a better network than here at the office.
[ONE Original Android Development] magnamentis:
did you check ?

how many devcies did you try on the same network ?

i suspect your router could be the culprti, restart your router ( 20-23" ofr the power socket) and see how it goes.

of course you should check other devices with same router as well as your devices on other networks if not already done.

good luck
[ONE Original Android Development] Notor1ouS-:
does the TRIM command work on the opo? or is it not recommended trying this.

I'm on beta7 / 31.nightly now, insanely smooth btw.
[ONE Original Android Development] andip71:
It would still work, but since Android 4.3 this is not required anymore.

Android does an automatic trim for quite a long time already.

I put that in long time ago for the Android 4.1.x based devices. But I left it in as it also does no harm.

Andi
[ONE Original Android Development] magnamentis:
1st time ever that i did a benchmark test for a friend to compare results, but since i already have the shot in my d'box i thought i could post it here as well :) ;) :good:

PS: no idea as to what it's worth but at least it's on top haha.....
[ONE Original Android Development] laura almeida:
What do you mean ?

SuperSU v2.52 is working fine!!
[ONE Original Android Development] vicky2131:
Has it been working from long back for you or only from 28th nightly?

Because it never worked for me on the before builds and it gave a bootloop only(today i flashed 28th build and using inbuilt root)

If possible give me a proper link for the SU
[ONE Original Android Development] andip71:
It was always working for me.

http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

Andi
[ONE Original Android Development] andip71:
GPU settings with CM13 kernel

Hi all,

I would like to ask all users of the CM13 kernel to check their GPU max setting.

All CM13 kernels so far have bug that is causing the GPU running overcocked by default.

If you do not want that, please select 578 MHz again in Boeffla-Config now.

I will address it with the next kernel update.

Andi
[ONE Original Android Development] feed3:
Mine underclocked by default to 389. Didn't realized it because no obvious slowness whatsoever for me..
[ONE Original Android Development] vicky2131:
Yes! its been overclocked and i had changed it to 330mhz. Btw thank you for the link.

Lord speed as always ;)
[ONE Original Android Development] Rahulrulez:
I flashed SuperSU 2.52 on Nightly 28th. and phone refused to start. Don't know what happened.
[ONE Original Android Development] laura almeida:
Can you try the same with SELinux status : permissive
[ONE Original Android Development] andip71:
CM13 kernel beta6

Hi all,

quick bugfix release for you, to avoid during startup (and later as default setting) the GPU is running overclocked.

It was due to some CM13 changes, so my old code did not work properly anymore. So it was slightly bigger than expected but is now fixed.

Version 5.0-beta6

29.11.2015

Note: You

HAVE TO

use nightly 28.11.2015 or newer (where the system partition rw issues has been fixed)

Fixed startup without GPU overclocking (due to a CM13 change, GPU was by default always overclocked)

Advice: Check (only once after updating the kernel) the GPU max frequency in Boeffla-Config to make sure it is on 578 MHz if you do not want to overclock

Thanks to [MENTION=3279788]ZaneZam[/MENTION] for informing me about this glitch.

Enjoy

Andi
[ONE Original Android Development] Mecca EL:
Aahhhhh! I was wondering where that drain was coming from. Thanks!
[ONE Original Android Development] andip71:
Sorry, but I do not think this caused any significant drain :)

Andi
[ONE Original Android Development] Mecca EL:
I was being funny. ;):highfive:
[ONE Original Android Development] Rahulrulez:
I have adjusted Charge rate (AC) to 1800 from Boeffla-Config v2 app.. however, when I plug in my phone. I can see, my phone is being charged at rate of 800-1050 mAh only (tested using Ampere app). Tested with two chargers just to check if my charger has gone kaput.
[ONE Original Android Development] kalapapa:
When your phones screen is on it doesn't charge at its potential.
[ONE Original Android Development] andip71:
True. Thanks for explaining.

Andi
[ONE Original Android Development] magnamentis:
you only can measure the real charge rate with an ampere/voltmeter which is a device to link between device and power source. however if it does not charge as expected it's in 99 out of 100 cases the cable and not the charger. i made thorough testings when i had once charging issues on my motorbike and one would not believe how many cables are poorly charging and since i have good cables i never had such issues again. the thing with screen on was mentioned :)
[ONE Original Android Development] Crazy-Silver:
Deleted
[ONE Original Android Development] dkryder:
i've read that the device itself is what determines the charge rate. if this is the case then the same charger/cable combo might deliver different results. i've also read that one should use the cable that came with the device for best results. it is very interesting to me that suggested charge routines can vary so widely. my thinking is exactly what you did, your own research with the cables and chargers that are available. it is also possible that one combo would give optimum results for one device and then give less than optimum results for another device according to what i have read.
[ONE Original Android Development] andip71:
Okay guys, I say good bye for a few days now.

Going to have a business trip to Netherlands from tomorrow early morning on, returning back before weekend.

Have a good time and cu soon...

Andi
[ONE Original Android Development] kurtextrem:
Have a good time!

And for all of us, expect a new COS update this week ;) :D :D
[ONE Original Android Development] Spaulding89:
Have a good time in netherlands

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] deepaklunked:
Really? Now that's good news.

Tapatalked through VM-ed Bacon
[ONE Original Android Development] kurtextrem:
Andi gone = Cyanogen releases a new update. Everytime (but this time he isn't long enough away I guess :( )
[ONE Original Android Development] DJMartini:
Coming from AK kernel there was a discussion thread around custom profiles created by individuals for best battery savings. Is there anything similar to this kernel by individuals by chance?

Thank you!
[ONE Original Android Development] ZaneZam:
Yes check for example this out : http://xdaforums.com/showthread.php?t=2998145
[ONE Original Android Development] andip71:
I think this time we are safe.

Cos13 is still quite far away. And I don't expect a cos12.1 update anymore.

Andi
[ONE Original Android Development] nitishp7890:
Yes latest version is super stable and battery life is ****ing amazing thanks for this awesome kernel and I think this can be end of development for cm 12.x kernel