yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
And with stock COS13.1 kernel it works?

Curious...

Andi
[ONE Original Android Development] hellcat50:
Yes, using stock kernel at the moment.
[ONE Original Android Development] andip71:
Ok, could you do me a favour for a test?

Could you extract the stock kernel for me, e.g. with flashify where you can save a kernel?

I would then extract the ramdisk and give you a test kernel with it...

Andi
[ONE Original Android Development] rolarocka:
Sorry for this stupid question but how do you restore the default settings without the boeffla app?

Oneplus One
[ONE Original Android Development] hellcat50:
Here you go (keep in mind that it is patched with latest supersu):

https://drive.google.com/file/d/0B1SRgTBQYTFucG5INVE2dUJ6dlU/view
[ONE Original Android Development] ZaneZam:
u can use the recovery zip (boeffla-config-reset-xx.zip) provided in boeffla-kernel-data folder and flash it via recovery.
[ONE Original Android Development] Aavion:
I'm now trying to get an untouched boot.img without root (no debuggable image available atm) :D Flashify just crashes and dd also won't do it... I'll upload a twrp backup of the stock kernel in a few (i assume that this will work)
[ONE Original Android Development] andip71:
Ah, yeah, I am sorry. I need a real genuine, untouched boot image.

Thanks, that would work, yes.

Andi
[ONE Original Android Development] Aavion:
Meeeeh... [MENTION=947981]Lord Boeffla[/MENTION] Would a "boot.emmc.win"-file help you, too? Because there's no way to extract the raw boot.img file without root (afaik)...

this is the twrp backup folder:

https://onedrive.live.com/redir?res...83&authkey=!AARAsBPPa_1j-jU&ithint=folder,win
[ONE Original Android Development] hellcat50:
Now here is the untouched boot.img: https://drive.google.com/file/d/0B1SRgTBQYTFuX0VTOFhLeXFKbjg/view

I already extracted it using the image kitchen: https://drive.google.com/file/d/0B1SRgTBQYTFuUy02aEdGRnoyYmM/view
[ONE Original Android Development] andip71:
Thanks, I think I can work with that now.

Andi
[ONE Original Android Development] cloudx720:
Why did I sell my opo.... :(
[ONE Original Android Development] andip71:
Don't know?

But it was probably one of the biggest mistakes one can do :)

Andi
[ONE Original Android Development] cloudx720:
I think your right lol
[ONE Original Android Development] andip71:
Hi all,

next maintenance update already for CM13:

Version 5.1-beta25

08.06.2016

Update: Updated with latest official CM kernel commits as of 08.06.16, 8am CET

Update: Ramdisk of official CM13.0 build of 08.06.16

Change: Improvements to kernel build script

Enjoy

Andi
[ONE Original Android Development] funkstylez:
Any idea why flashing beta 25, it's booting back to TWRP after a system reboot? Coming from beta21...
[ONE Original Android Development] andip71:
No. It is not doing that here.

Maybe a bad download, did you check the md5 checksum?

Andi
[ONE Original Android Development] andip71:
[MENTION=5925270]hellcat50[/MENTION] [MENTION=2707213]Aavion[/MENTION]

I have a test kernel based on COS13.1 just ready (but untested as I do not yet have COS13.1 running anywhere).

Would you like to give it a smoke test?

Thanks

Andi
[ONE Original Android Development] Aavion:
I'd like to test :)
[ONE Original Android Development] andip71:
[MENTION=2707213]Aavion[/MENTION], you have a PM.

Andi
[ONE Original Android Development] feed3:
Interested to test too..
[ONE Original Android Development] hellcat50:
Yes, gimme that kernel :D
[ONE Original Android Development] Aavion:
First look:

SystemServer Init seems to be broken.

(various FC's because of system servers not running / activities not resumable).

Best to replicate: Theme chooser and Lockscreen MOD settings FC while trying to access them.

No problem with stock kernel...
[ONE Original Android Development] andip71:
Absolutely not cool...

Andi
[ONE Original Android Development] Aavion:
It's the same behaviour as with 5.0b5... Kernel is usable, as long as you don't try to get into theme chooser or want to use those "MOD"s :D
[ONE Original Android Development] andip71:
Ok, I uploaded a new version again into same folder.

Can you please give that a smoke test again?

(it was a f****ing SeLinux thingy...)

Thanks

Andi
[ONE Original Android Development] Aavion:
yes

Gesendet von meinem 1+ One
[ONE Original Android Development] gro95qg:
Tks bro

Envoyé de mon Oneplus One®

Attente livraison moto360®
[ONE Original Android Development] NickosD:
Can you make a cm12 version? I prefer your kernel over ak...
[ONE Original Android Development] DanteGR:
I'm quite sure he will when he gets back. He's just on vacation right now [emoji4]

Swiftkeyed from my OPO A0001
[ONE Original Android Development] vikrant82:
Are you doing a soft reboot rather than regular reboot?

Sent from my A0001
[ONE Original Android Development] sui81:
On latest CM11 based Rom's like CrDroid and Temasek with Beta9, i'm not able to record Video above 720p Resolution with CM11S Camera (2.0.004)

If i use 1080p or 4K, the Recording stopps after 3sec.

I think it's Kernel related because it works with Stock Rom Kernel or the latest Avalon.
[ONE Original Android Development] nosidefcp:
[MENTION=947981]Lord Boeffla[/MENTION] thanks for the amazing work. are you planing a kernel for cm12?thanks in advance
[ONE Original Android Development] andip71:
Yes, when I am back from holidays, I will look into it.

However, I will not be a very early adopter of it. At least there should be a "usable" official CM12 version available so it is worth spending the time on it.

Interesting... just tried it with CM11 nightly. Can record with 4k for minutes. Maybe some CrDroid specifics that may cause a conflict?

Anyways, beta10 is due to be out soon (in a few days) which is a complete rebase on latest CM11 branch code and not relying on the shipping branch in the cm kernel repo anymore. Of course this only is valid for the cm11 genuine Boeffla Kernel...

Yep, read above. There will be of course a kernel once an almost stable CM12 is available for the OPO.

Andi
[ONE Original Android Development] ak:
CM12 branch is the future, I think CM will drop updates for CM11.

You can use it with your spear phone without problems.

ak@bacon@pancetta
[ONE Original Android Development] osmosizzz:
Yeah cm12 already works without issues. Only some NFC things and Bluetooth things are not working well..

Sent from my OnePlusOne
[ONE Original Android Development] gianton:
2.0 beta 9 working rock stable with great battery life on CM11s 44S. No issues this time like the loss of notification sounds I had.
[ONE Original Android Development] mindblizzard:
Same here, only video for 3 seconds, francokernel same problem
[ONE Original Android Development] Franc38:
Same here. No problems with the camera.

But... 2 reboots of the phone ever since I'm with 44S and 2.0b9. Then again, I also updated my recovery to TWRP 2.8.1.0... So, many new elements and two reboots in a week, nothing really catastrophic and it's hard to guess where it's coming from.
[ONE Original Android Development] DjDiabolik:
[MENTION=947981]Lord Boeffla[/MENTION]:

I have a little question for you but i don't know if you can debug or you can resolve and i don't know if it's a bug of stock kernel and if it's fixable by your next kernel... but i want to ask this:

Before to start to use your fantastic kernel i ever used the stock kernel.................. before to use the 2.0 beta on my 1+1 i have a little problems whit my home wireless connection and on italian oneplus forum section a user has suggest to me to try to use your kernel because you have make some fix on wireless function right ?

This is my little problems:

On my home i have a ADSL whit Fastweb..... i have a wireless configured whit WPA2 PSK and if i come back to my home with the screen turned off my 1+1 do not connect to my wireless connection! For obtain this i need simply to turn on the screen and my opo connect it in about 3 seconds...........

I have try to change the channel to my wireless... change key... change the protection from WPA2 to WPA or WEP but nothing help me whit this problems....... i also try to delete the access point and after reassociate it but never working.

I don't know if i can debug this... i don't know what's appened but, for now i hope, I have this problem only in my house because i have try whit another wireless (for example in house of my friends or parents) and i never obtain this problems.

If you can make some change in wireless setting inside kernel you can investigate about this problems ??

I also tryed, some week ago, to open a JIIRA on bug tracker of CyanogenMOD but my ticked it's been closed and assigned by duplicated to another but different case......

P.S. Sorry for my english..... i don't know if you can understand it.......... but if yes thanks in advance if you can help me to resolve this bug...

Aah... i have miss some important information:

Recently i come back on stock kernel because i have installed the recent OTA and this problems i have it's not been resolved....
[ONE Original Android Development] jgcaap:
[MENTION=5919577]DjDiabolik[/MENTION] how are you? First of all... Have you tested this on other wireless? If yes does the problem persist? If doesn't... It's your home wireless router which can have some sort of incomoability.

The other thing that can be is your phone wireless is damaged.

So please test on other wireless first.. A kernel dev cannot help here without that info. :) thanks
[ONE Original Android Development] Vortex1969:
Many thanks for sharing your great work with all and the time it takes that many may never know. Least of all kernel is smooth as silk..

As one of many thanks and Regards,

Vortex
[ONE Original Android Development] andip71:
Hey,

just a quick note I am now almost back from holidays. Will be fully back by Monday.

Beta10 for both cm11s and cm11 are almost ready to go. Just waiting for a bugfix on zzmoove by ZaneZam (this does not yet play well with the new MSM devfreq 3.10 backport CM put in their sources).

Once this is delivered and running fine for 24 hours, I will release beta10 for all of you.

And most probably beta10 will then be converted to 2.0 stable.

And theeeeen.. it is time to join the CM12 club :)

Andi
[ONE Original Android Development] andip71:
Hi,

unfortunately this sounds very much like an issue in the rom to me, not in the kernel. Which is proven by the fact, the same happens on stock kernel as well. Probably also on all other custom kernels.

Sorry, but maybe they fix it with cm12.

Andi
[ONE Original Android Development] magnamentis:
heads up

as promised my heads up on "testbuild" boeffla-kernel-2.0-beta10-CM-bacon.CWM.zip "TESTBUILD"

a) issue with settings not sticking for the entire last week since ß9 = installed ß10, booted up, all stuck = all fine =

solved

thanks

b) issue never mentioned before but long since was there with notification not showing after additional bootup delay ( always worked without additional bootup delay )

....installed ß10, booted up, waited 60 seconds, icon ( notification ) was showing up as expected =

solved

thanks

No other issues like before, perfect like ß8 that's it, very much appreciate your efforts during holidays :)

comments from cm11s users are not necessary on the matter because it was a cm11 issue, limited to certain configurations only, thanks.
[ONE Original Android Development] hellcat50:
i knew it :)

because when I switched to permissive theme chooser worked again.
[ONE Original Android Development] Aavion:
Did a quick "run" through all screens and a few apps and everything seem to be working fine (:

Will test further with my preferred config, but all major bugs are solved now ;)

--

Off-Topic but I wonder, if anyone has found a solution for the missing weather-settings, yet? I already installed those weather providers from playstore for cm but I cannot find a screen where I can configure them to show me some weather information... (COS 13.1)
[ONE Original Android Development] hellcat50:
You can start the activity by using "activity launcher" from play store

---------- Post added at 12:10 PM ---------- Previous post was at 12:07 PM ----------

Yup. Now everything seems to work fine.

Off topic: they included the lock screen bug in this build, which has been fixed in the nightlies since start of may. wtf!
[ONE Original Android Development] Aavion:
But what activity? cLock widget e.g. doesn't doesn't has those weather settings anymore within it's options....
[ONE Original Android Development] hellcat50:
deleted because off topic :)
[ONE Original Android Development] ch-vox:
damn ! I thought it was related to COS13 properly, but in facts the culprit was the custom kernel ... I've tried latest COS13.1 release and I've installed Boeffla Kernel on it, everything seemed to work fine except Theme chooser and some other things that were getting FC's. I didn't know the Kernel could have any kind of impact on Theme chooser FC.

[MENTION=947981]Lord Boeffla[/MENTION]

I'm interested in testing your freshly new COS13.1 kernel.

I'll update (again :p) my OPO tomorrow to give it a try.

EDIT:

there is a new stock option in the settings to switch off LED notifications while in DND mode ;)
[ONE Original Android Development] andip71:
Hi,

yes, selinux is a beast.

My kernel comes with patched selinux policies, in order to enable the internal superuser in case people (like me use it).

And it seems COS13.1 implemented two new system services (which are started by the kernel init script), one for designs and one for the MOD stuff.

As my patched selinux policy did not yet know these services, they were not allowed to start and hence the user interface could not connect to them.

That is the explanation in a nutshell.

Was hard to find it as usually it is enough to merge the code changes and the new ramdisk in. This time it required a bit more.

Ok, so the DND LED option is back, which is good. I did not miss it anymore as I wrote my own little app to take care of it. But better to have rom support for it of course.

Andi
[ONE Original Android Development] andip71:
Hi all,

with having COS13.1 already in the pipeline, I will hereby declare the COS13.0 kernel as a stable release with is final now

Further developments will flow into the COS13.1 kernel always.

COS13.0 -- Version

5.0 stable -- Final

09.06.2015

Note: You should update to COS13.0 version ZNH0EAS2JK to use this kernel version !!

Note: Do NOT use this kernel on COS13.1 !!

Update: Boeffla kernel reset zip updated from V4 to V5 (smaller file size)

Change: Improvements to kernel build script

Enjoy

Andi
[ONE Original Android Development] andip71:
Yeah, and now we come already to the brand new version for COS13.1.

Here we go (note it is the very first public release, so expect bugs...):

COS13.1 -- Version

5.1-beta1

09.06.2015

Note: You have to update to COS13.1 version ZNH2KAS1KN to use this kernel version !!

All functionalities are exactly the same as in last COS13.0 kernel version 5.0 stable

Based on latest kernel source code for COS13.01 (branch stable/cm-13.0-ZNH2K)

Ramdisk from rom version ZNH2KAS1KN

Enjoy

Andi
[ONE Original Android Development] Dhairya:
thanks a lot hoping charging and heating issue will solved by this
[ONE Original Android Development] andip71:
Charging maybe.

Heating? Not likely. But I never had heating issues, the CPU can happily run on 80 degree centigrade.

Andi
[ONE Original Android Development] Dhairya:
aha then would be issue with my charger but if we have quick charge then would be awsm as on stock kernel the backup is bad as hell without boeffla i cant be on cos !
[ONE Original Android Development] Aavion:
Hey it's me again...

I'm playing around with different settings to further test your cos13.1 kernel and suspecting the input boost driver to be faulty in this version....

with screen untouched in idle state, cores 0&3 are running at 300MHz (as expected).

I tested different scenarios (input boost on/off, default and set to 960 and 1190) but none of my settings seem to have an impact on core frequency while touching the screen.

The frequency of cores 0&3 jumps almost everytime to 1728MHz (almost, because sometimes all four cores jump to 1574 for no reason), even if the input boost driver is turned off....

observing this behaviour for more than an hour now on alpha1 and beta1 (so there was a reboot in between)... it's not annoying, but doesn't seem to work as intended, as it looks like the set values are being ignored :D

(running on interactive/interactive battery, default hotplug)

I'll do further tests, but except this little culpy everything seems fine :)
[ONE Original Android Development] Aavion:
Some screenies to show, but not much to see here :D
[ONE Original Android Development] andip71:
Hi,

ya, I will look into that in the next days.

I am not even sure this was working on COS12.1 correctly? Maybe it was.

BTW, was it working for you on COS13.0? That would be an interesting fact.

Thanks

Andi
[ONE Original Android Development] Aavion:
Never touched that setting on cos13.0 (left stock), but I remember the freq being at 1497MHz when touching the screen (what should've been stock). Also the table of used freqs looks very differently on COS13.1 than it was before the ota: 1497MHz is barely used, while it was the most used "high"-freq on cos13.0. Now the most used "high"-freq is 1728MHz. max-freq seems to be used less often than it was before, so overall power cosumption should be the same. no noticable changes in low frequencies.

PS: I remember exactly, because i was observing the differences between hotplug profiles ~a week ago :D

Core freq (for all active cores, except those that already ran on higher frequency) ramped up to 1497MHz everytime I touched the screen.
[ONE Original Android Development] andip71:
Thanks. This has, honestly, not a priority for me at the moment. But will put it on the list for research.

Thanks

Andi
[ONE Original Android Development] Aavion:
No problem.

It's not important for me, but I thought it could be helpful if I share my observations with you ;)

Everything else seem to be working as expected.

For me, efficient battery mode with stock kernel settings (except battery gov-profile) is pretty awesome. also overall speed and "snappiness" of cos13.1 is exciting compared to previous versions, while giving pretty decent battery life.

I'm impressed. COS is getting better and better with every update. Feels like a real stock rom now :D
[ONE Original Android Development] Matteo_666:
Is the ZIP file you provided for using the internal root still working with the latest COS?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Yes, it does.

It is nothing than the su binary, so it should work for a long time still.

Andi
[ONE Original Android Development] ch-vox:
it works like a charm.

maybe it's placebo effect, but I seem to have better battery life with this latest COS 13.1.

no bug so far.
[ONE Original Android Development] andip71:
Hi Aavion,

I did a whole lot of testing this morning.

And to my surprise, at my side it is working as intended.

I mean, yes... there is a clear focus now on the 1574 frequency.

But for a test of the cpu boost driver I configured the following:

- boost frequency to 2265 MHz

- duration of boost to 4 seconds

Then I was clearly able to see the effect of it.

I believe, something in CM13.x/COS13.x (could be even the rom) makes the CPU boost to 1574 frequently, as you have seen already. And this of course "overlays" all cpu boost actions with lower frequencies and short durations.

Andi
[ONE Original Android Development] andip71:
Well - that is how it is intended to be, eh? ;)

Good luck for tonight, opening game of the European championship.

Andi
[ONE Original Android Development] KaszasM:
YEAH had luck before a few days, now Hungary is back again after 44 years (lol) so see you in the end game!

anyway good luck to all the countrys :)

schöne grüße aus Bayern
[ONE Original Android Development] ch-vox:
I'll stay far away from my TV... :laugh:
[ONE Original Android Development] Aavion:
Did a quick test again with boost duration at max and you're right... it works as intended...

could you please tell me, what is shown, when you keep your screen touched (long press)?

for me, it mostly shows up as 1574 or 1728 during the time period i hold my finger on the screen. as soon as i release, it falls back to 300 - so it must be touch related somehow...

not a big deal, though, as it doesn't annoy me... just an observation :)
[ONE Original Android Development] andip71:
It is 1574 as long as I touch the screen.

I am quite sure this is a new feature of mpdecision used in COS13.x.

Andi
[ONE Original Android Development] Dhairya:
well new update on cos 13 kernel is pretty good a bit high battery drain charging seems to be improved if boeffla can see on battery drain like need to

at 2pm device full 100% and at 6pm its 65% and hardly use just whatsapp 20mins ! rest all good
[ONE Original Android Development] Aavion:
And on COS13.0 it was 1497 when i held the screen. But as long it brings UX improvements I'm the last one to complain :D
[ONE Original Android Development] andip71:
???

Sorry, I do not understand your message. What did you want to say?

Thanks

Andi
[ONE Original Android Development] anagramgenius:
ZNH2KAS1KN boot.img

Patched boot.img. In case if someone wants to revert back to stock kernel.

File: boot_ZNH2KAS1KN.img

CRC-32: 59198015

MD4: 5aa8b5c9a2e93467eca1be5b602473f6

MD5: e08d4f92fe3c3192935540281419f22d

SHA-1: c34904cc18e2b8e68cf2664da532f7e36975d94e
[ONE Original Android Development] andip71:
Patched with what?

Just to say, I always provide COS stock kernel zips to flash in recovery also in my download areas.

Andi
[ONE Original Android Development] anagramgenius:
Forgot to mention. Patched the OTA kernel with the previous kernel image. Until the fastboot zip is out, this would come in handy.

EDIT: Oops. Didn't check your website. You already have it.
[ONE Original Android Development] hellcat50:
Hey Andi,

Are you planning to buy the OP3 and develop for it? I love your work so it would be awesome if you would do it :)
[ONE Original Android Development] andip71:
Is in my plans.

Maybe not very soon, but in general yes.

Andi
[ONE Original Android Development] fmc000:
Stuck in a bootloop.

I am trying to use this kernel with SmartisanOS, a CM12.1-based ROM with many customizations. It uses stock CM kernel (3.4.67-cyanogenmod-ge728d16) and by default it runs with Selinux in enforcing mode.

I tried a couple of times but the result is the same: flashing Boeffla kernel results in a bootloop at the bootanimation level. Just to be clear, I'm trying boeffla-kernel-4.4-CM12.1-bacon.recovery.zip .

AK.311.OP1.CM.zip works fine, BTW, so the ROM is definitely able to run custom kernels.

Any ideas?
[ONE Original Android Development] andip71:
My kernel is only for CM roms and roms that are compatible.

I state that every time again and again, and I do that for a reason, not for being funny.

Andi
[ONE Original Android Development] fmc000:
I know that, I was just trying to understand what I could do to insure compatibility between the ROM and your kernel. As the ROM runs natively the CM kernel I thought it was worth a try.
[ONE Original Android Development] andip71:
Nothing you can do.

Either the rom boots up with the CM ramdisk which is included in my kernel, or not.

Yours does not, nothing you can change.

AK kernels use anykernel method, so they kernel works on more custom roms.

But I am not interested in that + do not like anykernel method (see op), so my kernel is more limited in terms of roms.

Yeah, I make the kernel primarily for myself, and I use only official CM and nothing else. Sounds selfish, but it is just like that. Sorry :)

Andi
[ONE Original Android Development] fmc000:
Crystal clear. Thanks for the thorough explanation.
[ONE Original Android Development] LPW00:
Does anyone know which version works on new Paranoid?
[ONE Original Android Development] Renosh:
None
[ONE Original Android Development] LPW00:
Goodbye paranoid...
[ONE Original Android Development] Crazy_Oni:
Wise decision [emoji6]

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] LPW00:
Maybe they change camera blobs on next update...