yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] h-cspu:
"We trust you" ... are you his disciples?

Thanks for all your suggestions ... from don't use a current device to don't use internet at all. I appreciate that.
[ONE Original Android Development] andip71:
It has the support built in.

And there are people that say it works.

I cannot personally confirm, as I don't need it = I cannot test it.

Andi
[ONE Original Android Development] chenrp:
beta 7 bug found?

governor mode won't stick... changing to ondemand every time...

anyone else?

using the latest boeffla app so maybe it is a bug in the app itself...
[ONE Original Android Development] kurtextrem:
So should everyone manually switch /cache to F2FS? (I mean Cyanogen should have had a reason to do it)
[ONE Original Android Development] Renosh:
No need to do that. Ext4 works perfectly and you can flash any ROM you want so I would strongly advise against it

If you feel the itch you can go to TWRP and select Wipe select /data and /cache and change file systems from there but you will lose all your data (internal storage) during the conversion
[ONE Original Android Development] kurtextrem:
Okay, thanks. Is there any (slightly) advantage when F2FS'ing only /cache? (too lazy for /data)
[ONE Original Android Development] Aavion:
/cache isn't used that much to feel a significant performance gain... ext4 is more stable, i'd recommend to stick with it ;)

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Nope. Not a problem here.

When does it happen, after a reboot, or during run time after some time?

I need a debug info file generated and sent after it happened.

Andi
[ONE Original Android Development] atulclassic:
just wipe boeffla app data and restart
[ONE Original Android Development] andip71:
Hi all,

maintenance update for CM13 and COS12.1.1. kernels for you:

CM13 -- Version 5.1-beta8

29.02.2016

Important: This kernel works ONLY from CM nightly of 30.01.2016 onwards!!!

For older nightlies, you need to use the old 5.0 series.

Update: Updated with latest official CM kernel commits as of 29.02.16, 9am CET

Update: Ramdisk of official CM13.0 build of 28.02.16

Change: Maximum charge rate for ac charger reduced to 2000 mA

(I got an USB current meter now and could confirm, the MSM8974Pro-AC SoC puts a hard limitiation above 2000 mA in)

Change: Do not display actual current anymore in Boeffla-Config overview screen

(my USB current meter showed this values were far off the real values, so I rather remove it before it is misleading)

Change: Update swipe 2 sleep gestures driver to newer version (no functional changes)

Change: msm bus drivers are less chatty now and log less to kernel log

COS12.1.1 -- Version

4.2-beta8

29.02.2016

Note: It is required to update to COS12.1.1 version YOG7DAS2K1 to use this kernel version !!

Change: Maximum charge rate for ac charger reduced to 2000 mA

(I got an USB current meter now and could confirm, the MSM8974Pro-AC SoC puts a hard limitiation above 2000 mA in)

Change: Do not display actual current anymore in Boeffla-Config overview screen

(my USB current meter showed this values were far off the real values, so I rather remove it before it is misleading)

Change: Update swipe 2 sleep gestures driver to newer version (no functional changes)

Change: msm bus drivers are less chatty now and log less to kernel log

Enjoy

Andi
[ONE Original Android Development] chenrp:
can you add more light on your claim that tge MSM8974Pro-AC SoC puts a hard limitiation above 2000 mA in

thanks
[ONE Original Android Development] andip71:
I saw some inofficial comments on that, but most important: I could see it myself. Whatever you tell the charger to do above 2000 mA, it is still capped on 2000 and does not go higher.

As we directly put the requested current into the chargers circuit hardware register, it must in the end be a hardware limitation. Which also makes sense as a safety net btw.

I could personally confirm this claim with my new equipment here to measure current between charger and phone.

Andi
[ONE Original Android Development] chenrp:
what about the measuring current... you removed it because of the inaccurate reading but the reading with the screen ON is different... try putting a LOGGED charging and see if you get the same results with an external reader...
[ONE Original Android Development] andip71:
LOL, thanks for the suggestion. I have done all of that.

And still the values were far off the reality.

BTW1 - when a fix current is selected with my charging driver, there is no difference between screen off or on charging, that is only with stock logic (between 1800 when screen is off and 1200 when on).

BTW2 - the logged stuff is still in. If you want to use it, let me know and I tell you how.

I removed it as it is not accurate enough, period.

And there is no way to bring it back by discussions :)

Andi
[ONE Original Android Development] chenrp:
cool. but now there is no indicator whether the charge is fast or slow...

i used to check cables/chargers quality with your builtin option...
[ONE Original Android Development] andip71:
Yep, this is true.

But I do not want to keep something in my kernel/app that is showing wrong values, even if the very high level tendency was ok.

You can still see the charge rates in dmesg if you really want to know it, I kept it in there for the geeks.

But honestly, I would not trust this figure alot as I found out.

If you seriously want to check the charge rates on a quite accurate level, a 12 EUR device (which I also purchased) is giving you the real truth.

Andi
[ONE Original Android Development] kurtextrem:
After switching from SuperSU 2.52 to the internal CM root (flashed the zip, turned it on) some apps who need root access reboot the phone when opening. Any idea how I could fix it (or rather how can I remove the internal root again)?

(For now turning off root in the settings + reflashing SuperSU worked, no reboots anymore)
[ONE Original Android Development] andip71:
Which apps for instance? I never had this.

And I am using internal root for both CM (of course) but also COS.

Removing the internal root again should be simple: Flash SuperSu again.

Andi
[ONE Original Android Development] kurtextrem:
XDA Labs and WhatsAppX and probably another background app.
[ONE Original Android Development] andip71:
Ok, I am not using any of those.

Maybe someone else.

I have doubts this has to do with root... but happy to stand corected.

Andi
[ONE Original Android Development] kurtextrem:
After flashing SuperSu again it works. I'll test some more and report back.
[ONE Original Android Development] Aavion:
Maybe you've forgotten to uninstall (unroot) supersu first before flashing cm's internal su? Maybe some leftovers were causing problems... Just an idea ^^

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Paoliz:
Is this kernel working with aokp unofficial?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] Lookitfast:
Just wanted to report that on Resurrection Remix 6.0 I have been running latest test CM13 kernel with intelliactive/zen without any issues at all. Still a touch of lag in gallery but I'm running F2FS partitions on data/cache so still fast as hell. Would love to know if 1024 is best or if I should on 2048 for read/write?

Lookitfastz 1+1
[ONE Original Android Development] cloudx720:
2048 is recommended for 64gb, i use myself :)
[ONE Original Android Development] bloof:
This might be off topic, but I need some help.

I am using latest COS 12.1.1

My work wifi has weak diffie hellman key exchange, and they won't update it.

That means it is impossible to connect either through browser or the system wifi web login connect.

[note: you can connect through Opera, Dolphin browsers and Chrome if you uninstall updates, but this still does not help connection through the system wifi web login]

Two questions:

1. Is it possible to have an option in the kernel to enable system connections to weak diffie hellman? You can already change wifi supplicant interval, I thought there might be a similar way of implementing this.

2. Does anyone know on which system file this restriction is enabled? So i can use an older version of the file from an older COS.

Thanks!
[ONE Original Android Development] andip71:
This stuff (encryption etc.) is not handled on kernel level.

I see no way influencing that.

Andi
[ONE Original Android Development] cloudx720:
So much love for this kernel Andi ? just showing my friends my phone running at 2.8ghz #mindblown ?
[ONE Original Android Development] MMWolverine:
Sorry for OT, but since there's a discussion about SuperSU, I'll ask someone to confirm this.

I had v2.67 then unrooted and flashed the internal su + Boeffla v4.2-beta. Flashed back SuperSU, phone is rooted fine, but I have "insufficient storage" error when installing chainfire's app. The apk is in /system/app, but not visible in launcher. I'm thinking the problem might be "mount namespace separation", which was unchecked before I unrooted. Any faster solution appart from a full system/data wipe?
[ONE Original Android Development] bombadier:
Not sure if of any help but I had an insufficient storage error with Titanium backup and unticking the mount namespace seperation and rebooting the phone fixed it.
[ONE Original Android Development] MMWolverine:
Yep, that's what I did for TB, but maybe now SuperSU won't install because the option was uncked. Anyway, I'll just make a clean install when COS13 is out. :p
[ONE Original Android Development] bloof:
In response to my own problem, i found a solution. I write it here in case anyone else find it useful when searching xda.

Solution: uninstall updates to webview app. (it uses chrome components (independent of whether chrome is installed or not) to help other apps display web content such as web login pages, etc.).
[ONE Original Android Development] hellcat50:
Hey [MENTION=947981]Lord Boeffla[/MENTION] ,

Are you planning to build a kernel for dirty unicorn rom (or aosp since dirty unicorn is based on it). I read in earlier posts that you only support official rom's. and dirty unicorns is official.

or do I misunderstand something?
[ONE Original Android Development] andip71:
You understood correctly.

I will not support it as it is not CM based.

I am not doing aosp or caf kernels.

Andi
[ONE Original Android Development] suaverc118:
I believe laura has used your kernel as a base to get it to work with VM13 ROMs. I wonder if that's a possibility for her to do?
[ONE Original Android Development] hellcat50:
Thanks for the quick response. You probably have your reasons why you don't do it, so I respect that :)
[ONE Original Android Development] andip71:
Yes, I have.

a) I am not interested in these roms (sorry, I am super honest)

b) I have enough kernels to maintain already

Andi
[ONE Original Android Development] laura almeida:
I managed to get Boeffla Kernel to work on DU but the Boeffla Config App is not supporting.

maybe [MENTION=947981]Lord Boeffla[/MENTION] can look into it ('cat /proc/version' command does work on terminal)
[ONE Original Android Development] hellcat50:
I really like the new Dirty Unicorn 10.0 (Android 6.0.1)! Rock-solid with nice features other ROM's don't have. (and CM theme engine!)
[ONE Original Android Development] andip71:
I do usually not need these features. Normal CM is more than enough for a minimalist user like me.

Hehe

Andi
[ONE Original Android Development] andip71:
Well, no idea. When the controller script is there and can be executed successfully as root in a terminal, then I do not know.

Then it is some speciality of the rom maybe. Maybe selinux stuff or similar.

Andi
[ONE Original Android Development] laura almeida:
I agree!!

There is something wrong with the rom

What does the "Working Directory: null" means ?!?
[ONE Original Android Development] hellcat50:
Nice to see that someone is trying to port this kernel!

Muy bien!
[ONE Original Android Development] laura almeida:
Don't get me wrong!

I used to work on that port but I couldn't get the App to work

So, I gave up!!

(Check my screenshot, last time I worked on it was on 08th Feb 2016)
[ONE Original Android Development] hellcat50:
Todo bien!

Learning spanish in school :P
[ONE Original Android Development] NickosD:
Feels good to be back. I'll report tomorrow the 1st cycle ☺️

Sent from my bacon!!!!!
[ONE Original Android Development] inzaghi89:
I've checked for few days and what I've observed that on boeffla kernel my battery keeps phone for 12-20 hours on default stock settings and same period on battery save present. I don't even know how it's possible while on stock OnePlus One kernel I've 20-28 hours. I've disconnected phone from charger at ~00:00. Phone was in my pocket until now (2:30 pm) and I've 35% of battery. I'm on default boeffla settings.

Wytapane na Oposie.
[ONE Original Android Development] andip71:
This is in theory not possible.

No single code change I did can lead to any battery drain. No additional single wake lock added.

And my original builds here use even the same compiler (hope you were not comparing unofficial recompilations with other tool chains).

But if you are more happy with stock kernel, no problem if you move on.

Andi
[ONE Original Android Development] kurtextrem:
So I've fixed my root issue. Flashed SuperSU again, deactivated CM root, activated respect CM settings, wiped SuperSU settings (the "switch Superuser App" thingy), then clicked the option below the previous option. After rebooting, enabled CM root, still didn't work. Next reboot I've installed SuperSU (the App), clicked the wipe thing again, removed the app and now it works... It's magic LOL

Only Power Toggles doesn't work - it reboots the phone when I switch off mobile data. :/ (Works through the native settings though)

Are there any logs I could look into?
[ONE Original Android Development] Renosh:
If you want to unroot, wipe system in recovery and flash ROM + gapps. You can also go to boeffla-kernel-data folder and flash reset if you want it back to stock configuration. That's what I normally do and never had issues switching from Superuser to SuperSU. These methods you're using may not work as cleanly as completely wiping su from system and having the stock OS back then flashing root of your choice. What ROM are you on and what other mods do you have installed?
[ONE Original Android Development] kurtextrem:
I don't watch to switch to SuperSU, I want to switch from SuperSU to the internal Superuser from CyanogenOS/Mod. Apart from Power Toggles everything is working fine.
[ONE Original Android Development] Renosh:
http://xdaforums.com/showthread.php?t=2906746

Download the signed flashable zip of COS12.1.1 from this thread. Wipe system and flash this zip. You're back to stock and removed supersu. I usually reboot even though it's unnecessary. Reboot to recovery. Then flash superuser and Boeffla then reboot.
[ONE Original Android Development] cloudx720:
After some serious gaming with this kernel i can honestly say it's awesome! The overclock from stock CPU frequency of 2.45ghz to 2.7ghz really makes a difference especially with graphics intensive games. Even though we can't overclock our GPUs, overclocking the CPU alone makes a huge difference :D #peace
[ONE Original Android Development] andip71:
You know my opinion about gaming... But of course happy to read that.

Andi
[ONE Original Android Development] andip71:
Result of recent poll about displaying actual charge current in Boeffla-Config.

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

In short - feature will be back in next updates, however slightly modified to indicate the information is potentially very inaccurate.

Andi
[ONE Original Android Development] Renosh:
[MENTION=947981]Lord Boeffla[/MENTION]

Just wanted to confirm something. Optimized Hotplug only changes the behavior of the governor during idle? I'm using it with Interactive and its really working smooth with 1958 max, 1267 boost and GPU max 200 and no stutter and no annoying heat during gaming
[ONE Original Android Development] andip71:
Yes, this is correct.

In fact, the logic is - when phone is idle and mpdecision (wrongly) decides to still keep 2 cores online, the kernel will switch off one more core.

If the phone is not idle, all is as usual.

Andi
[ONE Original Android Development] bloof:
I am getting a bit confused by the need to flash superuser. After install of COS12.1.1 can't you just enable superuser in the settings?

Or is this a 3rd root access option? (ie: SuperSU, superuser, CM native superuser)
[ONE Original Android Development] Renosh:
COS12.1.1 isn't pre-rooted as its an official factory OS and has to pass Google's certification suite. CM nightlies are rooted so its more of an issue of you're not getting they are two different ROMs based on the same source. COS uses stable branch and has some closed source features and no root (hence need to flash superuser) and CM is open source uses experimental branch (things break often) and is pre-rooted with superuser. Snapshots builds are built from stable branch
[ONE Original Android Development] cloudx720:
Sorry for off topic but say i wanna go back 100% stock to receive ota i saved my stock recovery with flashify. So i uninstall SuperSU boot into stock recovery reflash full cos12.1.1 will this method allow ota in the future? :D
[ONE Original Android Development] andip71:
Well, you need to ensure all SuperSu files are gone.

Also you need to flash stock recovery of course, as you said.

I would just flash the last full rom dirty over, then you can be sure all is settled to receive OTAs again.

Andi
[ONE Original Android Development] cloudx720:
Looking forward to cos13 with boeffla! Oh sounds so good ?
[ONE Original Android Development] andip71:
... when it will get available one day... sigh.

Andi
[ONE Original Android Development] Naz7x:
bro, really have a good time with your kernel when using S3 before...love your works bro...been aiming to test your kernel..hehe...love your work bro, may thanks to you bro
[ONE Original Android Development] udo 240:
Simple use Wugfresh Bacon BRT... You only have to google:cowboy:
[ONE Original Android Development] cloudx720:
I have it and use it all the time but i don't have access to my PC for awhile ?
[ONE Original Android Development] hellcat50:
[MENTION=947981]Lord Boeffla[/MENTION]

What is this??

"Sonstiges" is very high :eek
[ONE Original Android Development] andip71:
Dont know, I dont have it in my statistics.

Did you click on it to get more details?

If not... betterbatterystats will help you to figure out what it is.

Andi
[ONE Original Android Development] Crazy_Oni:
I have the same problem. Seems like android system.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Then it is, as expected, not kernel related but a rom/app thing.

Sorry

Andi
[ONE Original Android Development] bloof:
I only use COS, never CM, but i always found the "root access" option in developer settings. I assume that is the same as the CM option.
[ONE Original Android Development] Aavion:
Yes, there IS a Root-Option, when the kernel has debuggable-flag set. But for it to work, you also need a "su"-binary from CyanogenMOD in "/system/xbin", as this doesn't come with official COS.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] infatality:
Looking for forward to beta 9..
[ONE Original Android Development] andip71:
... which is ready already.

Just I have 6 hours non-stop videoconference with my US management now, so it will be evening before I can ship it.

Andi
[ONE Original Android Development] andip71:
Updates

Hi all,

updates for CM13 and COS12.1.1.

CM13 -- Version 5.1-beta9

09.03.2016

Important: This kernel works ONLY from CM nightly of 30.01.2016 onwards!!!

For older nightlies, you need to use the old 5.0 series.

Update: Updated with latest official CM kernel commits as of 09.03.16, 9am CET

Change: Actual charge current is displayed again in Boeffla-Config, however prefixed with a tilde (~) sign to indicate it is very inaccurate

Change: Correct SELinux contexts for Boeffla-Kernel specific files for better compatibility (e.g. Root Explorer app is now working again)

Update: Internal kernel superuser updated to su 2.65

Update: Ramdisk of official CM13.0 build of 09.03.16

COS12.1.1 -- Version

4.2-beta9

09.03.2016

Note: It is required to update to COS12.1.1 version YOG7DAS2K1 to use this kernel version !!

Change: Actual charge current is displayed again in Boeffla-Config, however prefixed with a tilde (~) sign to indicate it is very inaccurate

Change: Correct SELinux contexts for Boeffla-Kernel specific files for better compatibility (e.g. Root Explorer app is now working again)

Update: Internal kernel superuser updated to su 2.65

Enjoy

Andi
[ONE Original Android Development] hellcat50:
As german would say: "Läuft bei dir!" :D
[ONE Original Android Development] infatality:
[MENTION=947981]Lord Boeffla[/MENTION] Any ideas what going on? After flashing beta 9.. The apps don't recognise the kernel.
[ONE Original Android Development] Renosh:
You're holding it wrong [emoji15]

JK
[ONE Original Android Development] Arise:
Had some more testing and I decided to stop changing governor/frequencies from ROM side (in preferences), but that option is still there, doesn't mean I can remove it entirely. I guess it could be possible by making a custom ROM, but this is out of question for now.

Anyway, yes, I have a reason why I use "performance", basically I'm interested in raw power ignoring battery life, with usual governors in stock or modified kernels it seems that performance is the best governor I can get for best performance. I can go for other governors, but I have an issue, they scale up too slow and the benchmark results are not good at all. With "performance" governor it seems that the cores scales up fast enough in the warmup phase.

I'm testing with this app: https://play.google.com/store/apps/details?id=org.hwbot.prime&hl=en

With usual governors, it scales kinda badly, some cores goes at max long after finishing the usual warm up phase, in the middle of the true benchmark, and that scores me down. The rest of the cores can just jump up down without staying fixed at some fixed frequency.

So this is somewhat the reason why I go with "performance" for most kernels.

Now I gave that zzmoove with insane a go and the results were fine, I was able to get nice results, however I still see two cores(1 and 4) at 2880MHz while the other two in the middle (2 and 3) going at 2457MHz.

At this point I try to touch boost by pressing on the screen however the problematic cores shortly jumps from 2457MHz to 2880MHz and then they go back to 2457MHz.

Also, I see that in most governors, usually I have 1 or 2 cores at some frequency, and the other 2 cores shut down. Touch boosting by keeping the finger on the screen will boost the already working cores at their boost frequency, however the shut down cores will stay shut down, no matter how long I keep the finger on my screen.

Anyway, thanks for the Chainfire app suggestion, first time when I see it, it looks awesome, thanks again for this recommendation. And thanks to Chainfire, he makes so many useful apps. :)
[ONE Original Android Development] andip71:
Thanks Arise.

So, I cannot comment on the performance governor, as said. I am not using it.

The rest seems about to work fine then, based and your description.

But seems now you got a new toy with zzmoove, to play around. So, wish you lots of fun with it.

As I wrote in the OP, I am not a gamer, I am mainly interested in battery life vs. good performance mix. And I think and hope I will reach these targets with my kernel.

Cheers

Andi
[ONE Original Android Development] Arise:
Anyway, do you have any explanation why I can't get all four cores at same time at 2880MHz?

zzmoove with insane profile selected, max frequency and min frequency set at 2880MHz.