yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] abhibnl:
Thanks for the info Andi. I had some doubts with that phenomenon but you made it pretty clear. Could it be possible that render is using some other version of Smartmax than the one in yours? Maybe a tweaked one or an updated one. I'm only that there are some updates to interactive in AK kernel but as of now i'm not aware of any updates to smartax. And let me know if we're talking OT here so that i can stop posting replies in the thread. :)

Well they weren't even able to release proper sources. :rolleyes:

But hats off for your hard work brother. :good:
[ONE Original Android Development] budbay:
That's good news about kernel for oxygen, I look forward to trying it out. I tried to give you some support on that oneplus forum, but our comments seemed to fall on def ears. Thanks and keep up the good work.
[ONE Original Android Development] andip71:
It could be, he uses a different version of smartmax. Yes, would need to diff it to be able to answer that.

Yes, I saw it.

But you should know: Nothing's gonna stop me [emoji6]

Andi
[ONE Original Android Development] alexbk66:
That's the way!

One question, I know you already told that you don't even want to add 286MHz CPU step, but Render for exaple has 146MHz and even 90Mhz...

---------- Post added at 04:34 AM ---------- Previous post was at 04:33 AM ----------

http://xdaforums.com/showpost.php?p=59972535&postcount=518
[ONE Original Android Development] NuLLV01D:
As Lord already stated in the OP, he develops his kernel relatively close to stock and thus he wouldn't add them AFAIK. Also, these low clocks aren't good and actually take a toll on battery and performance as the cores have to struggle to reach optimal speeds from such low ones like 96MHz.
[ONE Original Android Development] alexbk66:
Thanks for the reply, but I really prefer developers explanation.

I doubt that "cores have to struggle to reach optimal speeds", that would depend on governor. I just thought that if there's any stupid unnecessary wakelock (which we all had recently:)) - than the CPU will be at least running at low frequency/low voltage, thus using less battery. And when needed - the governor will ramp the frequency to what ever is needed.
[ONE Original Android Development] andip71:
Actually his explanation was quite correct (seems he uses my kernel already for longer time).

I had the 267 step already added last year for some weeks. And I did not like it.

Indeed, waking up from deep sleep felt slower, I claim this step to be also responsible for some hot reboot issues.

Finally I decided to remove it as the negative impact outweighs the (non existing) benefits. Battery wise it is completely unproven to have benefits.

I prefer to go for stock frequencies to be on the safe side for stability.

Andi
[ONE Original Android Development] alexbk66:
Thank you Andy AKA @"Lord Boeffla" :good:
[ONE Original Android Development] andip71:
Oxygen OS

Ok guys,

time is closer for a first pre-testing of the Oxygen OS kernel.

Maybe tomorrow some brave people can pre-test an alpha.

I put all features in which are also in the last CM kernels, just two things missing (no swipe to wake + no kexec hardboot for multirom).

What I want to say is - people that are are interested should let me know, so I can consider them for pre-testing an alpha :D :D :D

Cheers

Andi
[ONE Original Android Development] tmimaesk:
Awesome! I'll be waiting for you to release the kernel :D
[ONE Original Android Development] acuicultor:
I'll be glad to test the kernel when it's available
[ONE Original Android Development] vraciu4you:
Me also....test test.
[ONE Original Android Development] Ofthecats:
Would you consider supporting mutirom with the test kernel?

Oxygen is my secondary
[ONE Original Android Development] jmtjr278:
I will test it for you also!

Sent from my A0001
[ONE Original Android Development] andip71:
I am not able to put the Kexec changes into the oxygen os kernel as they use different memory map.

So, no. Not before someone else does it where I can cherry pick it. I never use multi rom myself, so I have no drive to do it and no way to test.

Sorry

Andi
[ONE Original Android Development] acuicultor:
Kexec is only necessary on primary ROM, if you have OxigenOS on secondary no need multirom support on the kernel, AFAIK.
[ONE Original Android Development] andip71:
Correct. It was too early this morning when I responded, I totally forgot to write that.

Thanks for jumping in :)

Andi
[ONE Original Android Development] NikoZBK:
I'd be more than happy to test your Oxygen kernel :)
[ONE Original Android Development] NuLLV01D:
Since I Am a Student, I cannot donate to you. Thus, the least I can do is Fairly test your kernel and Help you improve your already f**ktastic Kernel!
[ONE Original Android Development] andip71:
Oxygen OS kernel pretest

Hi all,

so finally, the testers that volunteered to pre-test an Oxygen OS Boeffla-Kernel alpha version since yesterday just got a PM.

So let's see what this pre-testing phase shows.

Cheers and thanks already to the pre-testers now.

Andi
[ONE Original Android Development] acuicultor:
Thanks, flashed and testing;)
[ONE Original Android Development] spanish33:
Hmm where is my pm?
[ONE Original Android Development] andip71:
hm... in your mailbox? ;)

Andi
[ONE Original Android Development] lokesh.3440:
Would you mind sharing it with me as well Lord??
[ONE Original Android Development] Setting.Out:
Got it set up.. ;) I had to try an advanced feature, it then redirected me.. You should make this a section of the settings menu.. ;)
[ONE Original Android Development] RCT1:
On beta 3 started to get random reboots since changed to zzmove. Now on intelliactive everything is fine again.
[ONE Original Android Development] Albieri[SPAM]:
Follows the performace battery with beta3 kernel:

Config: zzmove / zzmove - battery yank / row / sd 256/1574 max cpu / -25mv / +5 speaker / 1036 touch boost / tweaks boeffla.

Normal use without game // 4G/3G: 80% and WIFI: 20%:

|

|

Normal use with game // 4G/3G: 80% and WIFI: 20%:

| |
[ONE Original Android Development] andip71:
As always:

- switch kernel logger to on (if not already)

- use zzmoove again

- after the hot reboot, create a debug info file in Boeffla-Config app (action menu, last point)

- mail it to me

- then ZaneZam and me can look into the log

Andi
[ONE Original Android Development] andip71:
App 2.1.51

Hi all,

I just released a new app version which has some corrections for working with the genuine CM11 Boeffla-Kernel.

So please make sure you update soon.

Andi
[ONE Original Android Development] cerealguy:
YEEEAAHHHH! Finally a beta for genuine CM11. It's time for a beer!! Like my old S3, even the OPO is '' BOEFFLIZED''!!! :D
[ONE Original Android Development] andip71:
Hey, welcome back to the world of Boeffla, welcome back on the dark side. Hehe.

No - good to see you back, buddy.

Thanks for the kind donation!!! Always helpful.

Cheers

Andi
[ONE Original Android Development] magnamentis:
first results

first night on this kernel, same 1% in 10h idle sleep like always = very good

further i would like to say that besides the kernel i really enjoy this app as well, so interesting that the two guys who seemingly pefect kernels

also make the best apps but no surprise really. my compliments here.

i have just one question about the app, let's say, out of "costumbre" ( gewohnheit ) how to set settings on boot or no the other way around, since i think they are automatically set on boot, how to disable set on boot ? should i forget to flash a component, ( kernel i.e. ) with the app set on boot trying to achieve non-existing tweaks it could end up in a bootloop and so i got used to restore settings after booting over setting them on boot. last but not least i got used to that because i've seen too many times ( not this kernel ) that settings on boot are not always applied propperly and with a restore i have a better chance that my settings were applied.

this is nothing i need to have, just curious whether there is a way to disable the set on boot, thanks
[ONE Original Android Development] andip71:
Hi,

thanks for the detailed feedback.

The philosophy of the app is: whatever your currently configured settings are, they get applied also after boot.

Be aware you can have as many different settings which you can put logically into profiles. So you can change the complete kernel konfiguration with just a klick in the app, or even put shortcuts to selected profiles on your home screen. Then you can even change settings to another profile without opening up the app.

And... if you want to automatically switch profiles based on events, you can even connect it to the well-known tasker app.

So that is the concept. Now, when you configured the kernel to death for some reason (uv, oc, whatever...) and you are having a bootloop due to that, help is easy:

Enter manually recovery by the known key-combination, then flash the reset script named boeffla-config-reset-v3.1.zip. You can always find this in the folder /boeffla-kernel-data on your device (the kernel places it there during every start).

Flashing this zip in recovery will reset the configuration back to defaults, so your device will boot again. Then go into the app and do the configuration again.

Simple? I hope so :)

All the rest about what else you can do in the app (copying profiles, resetting profiles etc.) is explained here:

http://www.boeffla-kernel.de/index.php/boeffla-config-help

http://www.boeffla-kernel.de/index.php/kernel-settings

http://www.boeffla-kernel.de/index.php/faq

Cheers

Andi
[ONE Original Android Development] Josolanes:
Hi Lord,

I flashed the latest 2.0 beta and am using it within SlimKat. With the kernel flash, Hotspot and WiFi stopped working. Anything I can do to resolve this? I really like your kernel and dirty flashing back to sensei resolves this but I'd prefer to use yours as I came from a Galaxy S3 and like using your governor set and config app. I do use Hotspot a lot, WiFi less so.

Thanks,

Josh

Sent from my OnePlus One
[ONE Original Android Development] andip71:
Well, never tried it with Slimkat. In the S3 world Slimkat was based on Omnirom.

Is it the same here, or is it based on CM11?

Because, as stated in the release notes of my kernel - it requres a fairly up to date rom. If the Slimkat you use is older than a few days, it is likely still expecting the old wifi drivers and will therefore not work.

Andi
[ONE Original Android Development] Josolanes:
Ah that wasn't something I considered. It is several days old i believe. Thanks Lord, I'm considering changing the ROM now to something that will stay more up to date.

Thanks again for the help and the excellent kernel!

Sent from my OnePlus One
[ONE Original Android Development] andip71:
Allright, thanks as well.

Many people do not understand and want me to create a third kernel with the old wifi drivers in, not seeing the work behind it.

Cheers!

Andi
[ONE Original Android Development] magnamentis:
very easy, thanks

sure, very easy, so instead of choosing set on boot or not i will simply make a profile with default settings, easy, just a new way for me but good.

last night i just froze the app and defroze it after flashing, works good, settings stick, so once more there are many ways but i like to go the way things are meant to function, usually pays off in the long run :)

i knew about the flashable, thanks anyways, the on boot thingy was more about to set it upfront before flashing so that i would not need the flashable, on the other hand comes to the same result :) many roads are leading to rome as we know.
[ONE Original Android Development] andip71:
Exactly, just create a new profile, it will contain default settings automatically.

Or reset an existing profile by long-pressing it and choose reset.

Many ways to reach the same stuff, yes.

This is just like I thought it is useful. Everything in profiles, which always get applied.

In worst case, an "emergency" flashable zip to come back to life.

Cheers

Andi
[ONE Original Android Development] Franc38:
Yeah!!!

Just got my One this evening... Very first thing I did: root... and flash your kernel. Very happy that you did move to Oneplus ahead of me, since your kernel was my main driver on the Galaxy S3!
[ONE Original Android Development] Notor1ouS-:
nothing beats this kernel.

had it on my s3 and now on the One.
[ONE Original Android Development] Josolanes:
Switched to CM11 and the combination of your kernel with CM is extremely fast and smooth. I think I've found what I'm sticking with for quite a while! :)

PS: and WiFi and tethering works now also of course. Thanks again!
[ONE Original Android Development] andip71:
Glad it works now.

Will have to look at slim as well one day. I still use that on my s3...

Andi
[ONE Original Android Development] BonzenPaule:
Hi Andy!

Recieved my Opo yesterday and installing your kernel was the first thing I did. As I said before I am really happy that you moved to the Opo and your kernel was one of the reasons I didn't wait for Nexus 6 but bought an Opo. Since I was using your kernel on the S3 for about 2 years now I thought it was time to show my appreciation.

Go buy yourself a beer or what ever ;)

Greetings from a Prussian living in Munich.

BonzenPaule
[ONE Original Android Development] AndrolinRoot:
Hey guys I am new here :) Is the latest cm12.1 goody stable ? :)
[ONE Original Android Development] hughfollett:
Just out of curiosity, how did you manage to make the kernel work without an answer from OnePlus??:eek:
[ONE Original Android Development] andip71:
Well, I was reverse engineering the zImage binary of their stock kernel. Here I got some indication what the device tree blobs could have been. So I went to the code, put some changes in to load what I thought, and it finally worked.

Then figured out, they did not include the wifi drivers in the code, so I crossported the CM ones and made it a module.

Then finally lots of cleanup done and yeah, thats where we are now :)

Andi
[ONE Original Android Development] andip71:
CM12.1 kernel update

Hi,

new update for you, included all recent CM kernel commits.

Version

4.0-beta10

30.04.2015

Updated with latest 7 official CM kernel commits as of 29.04.15

Fixed scheduler hardlimits for external sd card (not used in OPO, but nevertheless fixed now)

Ramdisk updated to official CM12.1 version of 30.04.15

Cheers

Andi
[ONE Original Android Development] hughfollett:
OMG! They should've provided properly working sources, but congrats for the hard work man!
[ONE Original Android Development] acuicultor:
Noticed the cm WiFi drivers because with original o2 kernel had poor WiFi download speeds and some random disconnections but with boeffla-kernel WiFi works like it should. Didn't notice any bad behavior or instability with the kernel. For me all is working perfect and improved battery life without changing anything. As always great job lord.
[ONE Original Android Development] lokesh.3440:
Sorry for my ignorance but is it compatible with Mokee 5.1.1 ??
[ONE Original Android Development] andip71:
I do not know, as I do not know Mokee 5.1.1 ??

Whatever it is, I never use customized roms. So you would need to try, or at least find out first what it bases on.

Andi
[ONE Original Android Development] Promez:
:eek:

great job!! :good:
[ONE Original Android Development] Mrwargod:
No love for the CM12 version?

Or are there no noticeable changes?
[ONE Original Android Development] tmimaesk:
booted without any bootloops, no signal drops, no SODs for now! Using zzmoove which I missed a lot with oxygenos :)
[ONE Original Android Development] grotesque02:
I'm on cyanide L (last 5.0.2 version), and phone is really slow to charge (4% in about 5 hours, phone off) .

I flash stable CM12 kernel and install app.

Maybe I have to change something under "Charge rates"?

For now I leave to 0=stock logic, but it's enought for have "old" time charge?
[ONE Original Android Development] magnamentis:
with compliments as always :) :good:
[ONE Original Android Development] andip71:
CM12 is dead from cm development side. Not any single change anymore since cm12.1 is out.

You should consider switching...

Great stuff. Enjoy it.

Setting to 0 indeed triggers stock logic.

But you can try to set manually to something like 1800 and check the difference.

Thanks my friend [emoji3]
[ONE Original Android Development] Mrwargod:
:good: Thnks for your reply.
[ONE Original Android Development] Ofthecats:
Hey lord, what is required to be a tester? I am interested
[ONE Original Android Development] bloof:
[MENTION=947981]Lord Boeffla[/MENTION]

Just FYI, you haven't put the latest kernel for CM12S17L on your website (i was looking for a flashable). It has a different md5 hash than CM12S0YL.

I also noticed that the boot.img from Calkulin's ROMs is different (MD5) than boot.img from OTA zips. Not sure why.

I thought I'd link you the flashable i made but it would probably take you less time to do it yourself than to dismiss it... :)
[ONE Original Android Development] lou2s:
Just moved from cm12s17L (boeffla 3 beta4) to euphoria 1.1 (boeffla 4 beta10, comes in time!). So far so good!

(Off topic: Forced the move as suddenly got stuck in boot logo after a theme update. Deleting the theme apk, dirty flash didn't work, so far the experience is better than in cm12s!)
[ONE Original Android Development] Clark789:
Good morning,

i'm sorry to say, that hotplugging with zzmove native default is still an issue with CM12S. After a few restarts it stays, that 3 cores will go offline and won't ramp up, when they are needed. Now i use the default hotplugging and this works very well, but to my mind it ramps down the cores not as fast as zzmove native default usually does....

Any chance to correct it?

Regards

Clark
[ONE Original Android Development] Mandrake2010:
boot.img by Calkulin is different because it contains SU enable root native cyanogen ( in Developer Options ) .

This one point I would like to ask [MENTION=947981]Lord Boeffla[/MENTION] if your kernel was compatible with the native root of cyanogen,because if flash boeffla kernel after flash calkulin i lost root.
[ONE Original Android Development] ZaneZam:
only if I can reproduce your problem which, I can't atm. ;) everything normal here on all roms I test + cm12s which is my daily driver. and yes you are right mpdecision doesn't switch cores that fast. I have no clue what's "so special" on your side. I didn't follow all your posts but again: maybe a fresh install + flashing only boeffla + avoiding tools that can influence gov settings might help. but I guess u tried that already?
[ONE Original Android Development] Clark789:
Thx, you're right. I tried already and i have nothing special on my phone: Stock Rom, no xposed or something similar and pure Boeffla... Leaves me a little clueless... But there was another user, who had the same issue. But this gives you no hint... I'm surprised, that you don't have any issue.. Congrats! ;)

I'll try a fresh install again and report back...

EDIT: I did a fresh install and firstly nothing changed. Three cores went offline and stayed offline. But then i changed the governor profile. I always used zzmove insane and then changed to performance. Seems as if it works! when the cores go offline, they'll ramp up, when needed. ZaneZam, did you try your device with insane? I'm happy, that hotplugging works again... :) Each attempt of course with zzmove native default...

Cheers

Clark
[ONE Original Android Development] ZaneZam:
great a progress! and yes it's "inzanely" working here on cm12s and cm12.1 :) BUT i just saw it could work better without giving it the default hotplug block cycles which are present in all profiles. they are "needed" to calm down hotplugging otherwise it kind of freaks out because of zzmoove's speediness ;) but "inzane" setting is really insane (name analogies are allowed *g*) and outstanding as it uses an complete unusual way of doing scaling decisions and depending on other settings hotplug also depends on the actual freq so it get's influenced. i'm still not convinced if there is a bug as i honestly think the sentences "Three cores went offline and stayed offline" and "when the cores go offline, they'll ramp up, when needed" are your subjective impression. :) i only can confirm the mentioned thing that it might work better without the hotplug block because then the cores are coming up much faster, but still they are also coming up with the blocks, but then sometimes slower. i actually doesn't like that behaving but i have to state again: i still have to rework all profiles for opo devices as promised ages ago *gg*, and that leads to a question to myself what about v1.0 beta7??

and that leads to saying to myself: "when i have more time, much more...." sry i'm rambling.... :)

long story short: if u can provide a screenshot with insane + 100% system load (constant and after a minute or so!) with only one core online then i start to believe :)
[ONE Original Android Development] bloof:
When stuck at boot after theme change:

Boot to recovery, mount system, then go to data/system/theme and delete the files.
[ONE Original Android Development] Clark789:
Please have a look at the following screenshots. Insane governor profile and native default hotplugging.

I changed back from performance governor profile to insane. When three cores went offline, i started the Antutu benchmark. As you can see, it starts with a single core and stays there during the whole test cycle and the result is pretty bad... So, for me it is a repeatable issue. Not only subjective impression... ;)

Regards

Clark
[ONE Original Android Development] DrNinjaa:
Calkulin has mentioned about the use of custom kernels on his rom in the OP of rooted 44s, u have to change the parameter in the build prop about Superuser to 1... by that u can use custom kernels with the built in root.

Please read the OP of the link I provide below.... hope it explains ur doubt...

http://xdaforums.com/showthread.php?p=56582168

#HappyFlashing#
[ONE Original Android Development] lou2s:
Thanks. I am too new for this theming engine thing. Lesson learnt.