yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] magnamentis:
too much work

just download and flash new version and reboot, that's it.

wiping cache and dalvik has nothing to do with the kernel except perhaps the kernel app but is not necessary you can even use the in-app feature under "actions" to download and flash so that you will simply end up with a booted phone and the new kernel up, running and set up. this if you don't have other things to flash at the same time.
[ONE Original Android Development] DjDiabolik:
wait wait wait... i can flash the newest zip direct from config app?

#Edit#

Yeah.. i have update to beta 11 directly from app whitout problems.....
[ONE Original Android Development] Vortex1969:
Been running your Kernel on my Last Bliss Pop test build. All has been great. Thanks for the great kernel.

Regards,

Vortex
[ONE Original Android Development] andip71:
Yes, that is absolutely fine.

For explanation: The Boeffla-Config app supports multiple kernel versions by history.

It started with Samsung specific kernels, later I added CM and Omnirom kernels.

Samsung kernel flashing is different to CM and Omnirom.

So the latter fall into the same category from the app point of view.

So if the message comes a "CM/Omnirom" kernel is being flashed, then it is right. Because cm11s is in it's hart a CM kernel.

All good :)

It is correct, but if you do not use multiboot, it is complete overkill.

Use load&flash in the app is all you would need to do. Simple and easy :)

Cleaning dalvik cache and cache partition is not required, this is a big fairy tale for long time. The kernel does not even know what dalvik cache is... so why should the kernel bother about it...

But cleaning dalvik and cache is also not something wrong, thats why you can even configure in the app settings, during a kernel flash this should automatically be cleaned for you.

I think, it cannot be more easy to flash kernels than with my app/kernel combos :)

Just if you use multi-boot, you need to flash in that specific TWRP still, as something special is being done there...

YES, that functionality is built in since the app exists, so for around 2 years already.

Enjoy it !!!

And look once into the "Action" menu of the app, and also into the settings... you will find many more functions that you are probably not aware of, which would be REALLY sad...

Andi
[ONE Original Android Development] otisman:
Happy Thanksgiving everyone! Enjoy your day of family and friends aloha
[ONE Original Android Development] andip71:
No such a thing here where I live, but thanks anyway :)

Andi
[ONE Original Android Development] otisman:
Dam didn't know that confined to a little speak of land in the middle of the pacific I will Andi aloha
[ONE Original Android Development] andip71:
LOL... no issue at all. Enjoy the day!

Andi
[ONE Original Android Development] acidburn94:
Ehi andi! I have flash your alpha 11, stable and great as usual! Really thanks!

Just one thing, I've installed it using your app load and flash, but how is possible that the app load the right kernel for cm11s and not the one for cm 11? It's a curiosity :)
[ONE Original Android Development] SaschaKH:
I know all that and that it's booting. ;)

Well maybe it's a german problem :D but as you can see other ppl are confused from that too.

I find it especially odd that the file is named 'boeffla-kernel-CM-2.0-beta11.zip (and not CMs). Sure I can look in the updater-scipt to see that it's CMs, but it is confusing.
[ONE Original Android Development] andip71:
The kernel tells the app which kernel variant it is, and the app then loads the correct one.

But where do you see the CM instead of CMs? I think I overlook what you mean still ;)

Andi
[ONE Original Android Development] SaschaKH:
After I flashed the new kernel yesterday I have a file in my boeffla-kernel-data folder that is named 'boeffla-kernel-CM-2.0-beta11.zip', I think it's the same as the file on your HP named 'boeffla-kernel-2.0-beta11-CMs-bacon.CWM.zip'.
[ONE Original Android Development] andip71:
Got it. Yes, indeed, nobody spotted that ever for around 1,5 years.

Good finding, will put that into the new app version to correct this.

Thanks!

Andi
[ONE Original Android Development] jgcaap:
Anyone here getting random reboots? Need kmsg logs :p
[ONE Original Android Development] andip71:
No random reboots, no.

Why, should we get some? :D

Andi
[ONE Original Android Development] Hana88:
lord boeffla with your kernel, i saw when i wrote to my friend on whatsapp or any other program who need the keybord to write, than after a while, the phone it self become a little slow, and if you wait a few second, the phone return smooth like the begin...
[ONE Original Android Development] andip71:
Hmmmmmmmmmmmmmmmmm. And what makes you believe that would be kernel related? (unless you have chosen weird configuration)

I cannot confirm that at all here.

Andi
[ONE Original Android Development] Hana88:
because it happen when i installed the kernel? :D
[ONE Original Android Development] andip71:
Well, then you need to install a different kernel :D

No seriously, these reports do not really help. Everything can cause a slow down. And most likely not the kernel but another app, background process, etc etc.

You did not give us any helpful information, not even which rom you use and which kernel type and version. Also not what you configured etc.

How would you assume someone can help?

Sorry, but had to say that.

Andi
[ONE Original Android Development] Hana88:
i would like to use your kernel because with the galaxy s3 you did a very GREAT job, even with this phone you do a really good job, but i saw this slowdown, and i had to come back to stock one...

i use the stock kernel, 2.0b11 and ALL STOCK (governor etc)

i saw that slowdown even with the stock kernel, but less...

---------- Post added at 06:41 PM ---------- Previous post was at 06:37 PM ----------

i don't know how to explain, but it's like after a while you write with the keybord, the phone it's starting to become a little less snappy...
[ONE Original Android Development] andip71:
Ok, I honestly cannot help you.

I do not face any slowdowns, and you are the first one who reports this.

If you have that even with stock kernel, it is an indication that something else is sometimes or always causing it. Rom, Apps, Processes... I cannot find out for you.

Typical advice is: Do a wipe and then try again with a fresh system, only install the most important apps for the test. But it is up to you if you want to do that or not.

Sorry

Andi
[ONE Original Android Development] Hana88:
thank you anyway :)
[ONE Original Android Development] andip71:
If I ever come across something like that on one of our 3 OPOs, I will let you know and check.

Promised :)

Andi
[ONE Original Android Development] acidburn94:
Ehi andi sorry for the OT but I'm very grateful to you for these results, you deserve it THANKS!!
[ONE Original Android Development] andip71:
Wow, looking really good. Thanks for sharing.

Andi
[ONE Original Android Development] molonad:
What settings did you use to get this stats? Thanx ☺

---------- Post added at 10:20 PM ---------- Previous post was at 10:20 PM ----------

What settings did you use to get this stats, thanx ☺

---------- Post added at 10:37 PM ---------- Previous post was at 10:20 PM ----------

Please can someone tell me which cpu governor is best for battery.. Zzmove - battery plus or yang battery extreme or interactive battery extreme, but interactive battery extreme is slowest from these three so I didn't like it. Please people can you share your best battery settings and stats? Thanx ☺ and if you can can you share your battery and speed balanced settings, thanx ☺
[ONE Original Android Development] acidburn94:
yes it does, it's ****ing great the best kernel ever tried ,really thanks!!!:)

i use zzmove with zzmove extreme battery yank with max speed 2.5 ghz and minimun 300, but i suggest you to use art, i'm on art with greenify in root modality and alpha 11 :)
[ONE Original Android Development] molonad:
Sorry, what is greenifi? Thanx

---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------

OH that's app iam sorry
[ONE Original Android Development] jgcaap:
Trying to discover reason of random reboot. We came already to some conclusions. When we get ota update from cm the update is not done correctly so it gives always problems. And we think is related to recovery, but still trying to find evidence about this. Ah ahh user has a lead on this. Many people complaining about the phone rebooting many times. I also had this issue and now trying to find a solution. :)
[ONE Original Android Development] andip71:
Hi ladies and gents,

major update of Boeffla-Config V2 !!!

For all CM12 users, the good news is you can now switch the app design to "Material Light", which gives you a seamless user experience.

Also, soft rebooting is now fully supported finally.

Happy updating and enjoy

Andi
[ONE Original Android Development] spanish33:
Yesterday I forgot to report gov settings doesn't stick on quick boot, today I got this update that fixed it.

Amazing!
[ONE Original Android Development] andip71:
Yes, it is/was a known issue already in the S3 times etc.

And as this behaviour now breaks partially with a design goal I have, I was long time reluctant to put something in which fixes the issue.

However, as the app evolved I built some stuff in to detect soft- and hot reboots recently, so now I can apply this as an exception handling. Which makes it finally ok for me :)

Andi
[ONE Original Android Development] NeGriTa79:
[MENTION=947981]Lord Boeffla[/MENTION] settings that are using the version Alpha4 and CM12 ???
[ONE Original Android Development] andip71:
I use pretty much default/standard settings at the moment, just scheduler changed to deadline.

Then touch boost freq lowered to 12xx Mhz. Then I increased fading speed of notification led.

And on last tab, I switched off all loggers + loaded the cifs module (as I frequently use it).

Andi
[ONE Original Android Development] NeGriTa79:
Thanks ... now I try them right away ...
[ONE Original Android Development] DJEXTRO:
Hi, congratulations for the excellent work. Can you insert the % of the level battery charge when the phone is turned off? This function there was in the 33R and there on AK. Thanks
[ONE Original Android Development] andip71:
Umm, let's see. Not with any priority.

I don't understand why you all switch the phone off for charging... This makes no sense.

I never have it switched off, what for?

So, I look into this when I have time left and no more important functional things to do.

Thanks

Andi
[ONE Original Android Development] DJEXTRO:
I switch off the phone because the charge is faster. Thanks for availability
[ONE Original Android Development] andip71:
But this is not correct.

Phone can charge even faster when switched on. Just use charge current control in Boeffla Config.

I put it on the list, as said. But with low prio as this is cosmetic and not functional.

Thanks for understanding

Andi
[ONE Original Android Development] jgcaap:
You should turn off radio at night at least. (flight mode)

The radiations provoke many types of issues to our Body. Mainly cancer. Turning off the phone or turning it to flight mode not only is healthier as the phone circuits are more durable.

Many videos about this on YouTube. http://youtu.be/hqafAzugooY

BTW try calling yourself and put an egg near the phone. Give it like a 10 minute call... See what happens :p

http://youtu.be/axUBeF-W7II

After that imagine on our brain :) our skull protects us from most radiations but is not perfect. :p
[ONE Original Android Development] Han-Droid:
http://www.snopes.com/science/cookegg.asp

So much for that.....!
[ONE Original Android Development] andip71:
I always put my phone in flight mode overnight.

But I never switch it off completely. There is no reason to do that.

Andi
[ONE Original Android Development] acidburn94:
Andi, here a suggestion, your kernel it's fantastic right now, but why don't you try to implement the idle mode for 1+1? I think results will be great! :) it's only a suggestion

Sent from my OnePlus One
[ONE Original Android Development] andip71:
Already answered in this thread a while ago.

I can't. It is obviously an Exynos specific thing that doesn't exist for Qualcomm...

Thanks

Andi
[ONE Original Android Development] SaschaKH:
Andi, in fact I see no reason to not switch it off. Go to developer settings and turn quick start on, than it's quicker turned off and on again than switching to flight mode.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Anybody can do as he/she wants.

The point was - I don't do it because in my opinion it is nonsense (my right to have this opinion). So don't expect I work on anything that is not important for me with any kind of priority.

Andi
[ONE Original Android Development] RCT1:
If you don't expect any call during the night... But some people have needs! Emergencies can occur!
[ONE Original Android Development] kurtextrem:
May I kindly asked what advantages this kernel has over the AK? (not gonna use a kernel w/o description (Furnace) or Franco, because see first post of this thread here)

and don't reply "it's german" pls :D
[ONE Original Android Development] magnamentis:
don't think so

seriously if i'm not completely wrong this is one of the questions you may not ask. perhaps this sound rude but it's the exact answer to your question to my best knowledge, ready to stand corrected. IMO this would lead to a comparison which i understood is not a welcome thing to do.

further, a bit more clearly speaking, you could read and find out yourself. there are not many kernels with a better description if you read and find the links to the description in the process.

i thinks i have to log out because it seems to become on of these days uhhhh....
[ONE Original Android Development] kurtextrem:
Of course, did that already. I'm not too professional, so I don't really understand (too) much. For example, how do I know which compile chain(?) is better than another?

I don't wanna have a comparison, just a vague thing like "Boeffle is friendler for noobs" or whatever.
[ONE Original Android Development] nicesoni_ash:
It's based on ur choice actually. It's insulting asking how's it better than other in any kernel or rom thread. Better improve ur knowledge by reading and compare yourself.

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE Original Android Development] kurtextrem:
Well I understand that, thank you.
[ONE Original Android Development] DanteGR:
[MENTION=947981]Lord Boeffla[/MENTION]

Is dynamic filesync enabled or disabled by default in your kernel? Cause sometimes it's showed as enabled and sometimes it's showed as disabled when i reboot the device. And i have never touched this setting. Thanks

Swiftkeyed from my OPO A0001
[ONE Original Android Development] andip71:
Just try it. You can always go back to stock or another kernel if you don't like it.

Default is on. And I never saw it off at my end. Hmmmmm...

Andi
[ONE Original Android Development] S1ay3r666:
Hey Lord Boeffla,

I am new here, coming from s3.

I have one question which Governor do you prefer and why?

Zzmoove was awesome on s3 with your kernel.

Thanks

Slayer
[ONE Original Android Development] RCT1:
It's missing a thread to share kernel configurations as we have on S3. ?
[ONE Original Android Development] S1ay3r666:
Yeah, it is awesome!

Maybe someone can start one ☺.
[ONE Original Android Development] Nimblebit:
Your sound application force closes when you try to run it! Even though busybox is install along with exposed!
[ONE Original Android Development] carburano:
Hi dev!

i just noticed you updated your touchscreen firmware... but it isn't activated in kernel because it is specific for OPPO find 7.

I noticed in your code that in CONFIG file it says: CONFIG_MACH_FIND7OP=Y

and related to touchscreen firmware

#ifdef CONFIG_MACH_FIND7OP //for 14001's wintek tp

#include "synaptics_firmware_tpk_14001.h"

#include "synaptics_firmware_wintek_14001.h"

#else

#include "synaptics_firmware_tpk.h"

#include "synaptics_firmware_tpk_find7s.h"

#include "synaptics_firmware_wintek.h"

so latest updated synaptics_firmware_tpk.h is useless for OPO.

Ciao

F.
[ONE Original Android Development] andip71:
That would be brilliant, yes.

Hehe, no, not at all. Because the "Boeffla Sound" app in Playstore is not done by me. It has been done by another dev, and it works only on Galaxy S3 and Tab 10.1.

It does not work on OPO and will never, as the development of that app apparently stopped. You need to configure sound in my own Boeffla-Config app.

Mh, if you are right, it is a good finding which I probably overlooked.

Will check that and if you are right, back it out again.

Still nice then, as I got some reports by users, the touch screen improved again with that new firmware. So then it would be another proof of subjectivity, which is quite human :) As it then is/was a placebo.

Let me check over the next days (preparing for a business trip just now, so limited in time) and revert back to you.

Andi
[ONE Original Android Development] carburano:
i think panels are the same on find7 and OPO but CM team keep drivers separated for testing purpose.

So maybe you can build a very experimental build to test this driver on OPO (on find7 it seems it solved many sensitivity issue).

So... if you want to try I will happy to test it :)

About subjectivity: a reboot always increase placebo touch sensitivity :)
[ONE Original Android Development] andip71:
Yes, building a test version would be fine. And I would (together with the investigation I mentioned before) do that asap, however preparing for a business trip for the next 4 days at the moment. So it is not likely I get it done very soon.

However, my airline (Lufthansa) goes on strike tomorrow, so it might be by flight gets cancelled last minute, then I would stay at home and could look into it earlier :)

Let's see...

Andi
[ONE Original Android Development] carburano:
Take your time my friend and good luck for your business :)
[ONE Original Android Development] Arise:
Did a build on ZaneZam custom crosscompilers and raised the OC limits in msm8974pro.dtsi to 3GHz instead of the max 2880MHz.

Somewhat managed to build the boot.img by repacking on his builds using my zImage, don't know how you do it, would be great if you can explain that, also asked ZaneZam here: http://xdaforums.com/showpost.php?p=57136222&postcount=187.

To my surprise, I managed to boot just fine, then started your Boeffla-Config app and... the max overclock went from 2880MHz to 2900MHz, while I was expecting to get 3Ghz. :)

So, is this some hardcoded limitation in your Boeffla-Config app or I did something wrong when I tried to adjust OC tables in sourcecode?
[ONE Original Android Development] DjDiabolik:
I'm again back here :) Now come.. new question and thanks in advance for explain this my dubs :

1) On last time i come here i learned it's possibly to upgrade the version of boeffla kernel directly from config app :) Yeah... it's a great feature but the question it's.... the config app download the newest version and after that flash direcly but the newest kernel it's been checked before to flash about your integrity ?? For example before to flash the kernel just downloaded the config app make a MD5 Check ?? If not i thinks this is a usefull feature you can add...... because whit download (if you have really bad luck) can be obtain a corrupted kernel and flash a corrupter kernel can be obtain a hard brick your OPO..........

2) This is a generic and i have a partial myself answer..... if i change some value from config app (like change the AC mA for example) the value just changed it's been applied in realtime or i need to restart my OPO for this modify has been applied ? I thinks i need to restart my phone.. it's correct ??? Or exist another solution like a softreset or a precise function in config app to apply changes whitout restart my phone ?
[ONE Original Android Development] Hexxer:
Hi,

im not sure that it is kernel related - but i like to report (also in german therunder).

Im on latest off. OPO (XNPH44S) with Boeffla beta10 or 11. Also installed Boeffly Config app - latest. No other systemrelated tuning. zzmove and zzoptimal

Im on a "load loop". If i shutdown my OPO and put in the power plug it loops up to the green battery-symbol and after a short while it vibrates and "reboot" again to this load symbol. On and on and on. Same happens if i plug power in and shutdown later. Put power out and everything is fine. There is no other problem. Loading works fine if it is up&running. To solve that problem i have to flash the hole XNPH44S+root. After that i cant rebuild the problems. Installed kernel beta10 and boeffla config and everything is ok. But i like to report it.

german:

Keine Ahnung was das ist/war. Gestern mein OPO runtergefahren und Strom eingesteckt. Da fängt es an zu loopen. Bis zum grünen Akkussymbol und dann wieder aus und wieder bis zum Akkusymbol. Immer und immer wieder. Strom raus und alles ist gut. Ich hab vorhin das Stock 44S+root installiert und alles war wieder OK. Dann Boeffla-Kernel drüber - alles OK, dann Boeffla-Konfig - alles OK. Dann zzmove/zzoptimal - alles OK.

Ich weiß NICHt ob es am Kernel lag (vermutlich nicht) aber ich hab keine bessere Idee. Es sind keine weiteren Systemapps installiert die irgendwas verändern. Vielleicht taucht so eine Meldung ja nochmal auf.

VG/Regards
[ONE Original Android Development] andip71:
Hexxer, how did you upgrade first to 44S, and then how did you do the second time (which fixed the issue).

I can only think of an incomplete update at the first time, where some of the partitions (bootloader etc.) were not flashed or not correctly flashed.

Just a wild guess however...

Andi
[ONE Original Android Development] ZaneZam:
Yeah sry very less time at the moment :( just a quick answer:

There is a bit more to do to have an additional freq step than just adding the freq to the table - look at the oc commits from Lord boeffla then u will see and u have to use mkbootimg to bring your zimage and ramdisk together take a look at ak's or furnace's kernel repos they provide build scripts. ;)

1.) actually it ever did a md5 check before flashing as for the Lord safety comes first ;) and hard bricking by flashing wrong /defective images might be easy fixable ask the Lord :)

2.) most of them are applied on the fly no need to reboot if there is a need to reboot u will be informed by the app
[ONE Original Android Development] andip71:
Hi,

although ZaneZam already answered.

1) By doing load&flash in the app, the kernel file is downloaded, and this is compared to the md5 checksum I store on the server too. So there is no way to have a corrupted or incomplete download which does not get detected.

Saying that, I always told people in the past on the S3 and Tab 10.1 as well, load&flash is one of the safest ways of flashing the kernel.

2) If the app does not tell you to restart, the setting is applied on-the-fly directly. 99% of all settings are applied just straight away.

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

I don't know what you did but beta11 cm11 version seems to have fixed my random reboots problem on slimkat latest build. It's the first time in 2 months having the OPO that i do not have a RR in almost 2 days and a half. In beta 10 i DID have reboots. Could you enlighten me on what change between beta 10 and 11 might have fixed this? Many thanks in advance my friend ?

Swiftkeyed from my OPO A0001