yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] azuman:
Hi to all. First of all, thank [MENTION=3878718]lord_[/MENTION]Boeffla and [MENTION=3279788]ZaneZam[/MENTION] for this great kernel and hotplugging ;) that said, i want to see if there is any solution/workaround for a problem im having since the last cm12 builds. My wifi keeps disconnecting after a while, whenever im at home or at work, then it doesn't connect back again. I just have the exclamation mark next to my wifi icon and if i go to check the networks it always says "authentication error" and even if i forget the network and connect with the password again won't connect. I have to reboot the device, but then back again... I tried already with temasek rom (lollipop), blisspop and other roms to see if i can replicate the problem, and it always works fine with the stock kernel from cm12, but whenever i flash ur kernel this starts to happen. Tried ur kernel in different roms as well, but always a no go. Only with the stock kernel my wifi works ok. Is there any log i can retrieve so u or anyone could check? Sorry for the long text and thanks in advance guys!

Sent from my OnePlus One in Barcelona ;)
[ONE Original Android Development] DanteGR:
It's a combination of things actually.

Firstly a friend of mine wanted it badly. Secondly i still have a top notch device in my M8 so I wouldn't be missing much anyway. And thirdly the M9 releases in about 2 months time and I want to save some money so.. there you have it [emoji6]

Swiftkeyed from my Renovated HTC One M8
[ONE Original Android Development] maxver0:
It's fine here, on lastest release. Catlog of course.

---------- Post added at 01:37 AM ---------- Previous post was at 12:46 AM ----------

Boeffla didnt survived rom update :( had to do it manually.

Oneplus One
[ONE Original Android Development] azuman:
Here is the link to the logcat, hope i got the useful details. Cheers n thanks pal! [https://www.dropbox.com/s/krugz4qg...RL]

Sent from my OnePlus One in Barcelona ;)
[ONE Original Android Development] azuman:
Here it is the catlog. Cheers pals! https://www.dropbox.com/s/krugz4qgx9qhmmj/wificatlog2015-01-22-03-17-20.txt?dl=0

Sent from my OnePlus One in Barcelona ;)
[ONE Original Android Development] maxver0:
My alarm doesnt works... After few hours of deep sleep it doesnt wake phone. After hour it works. Alarm is set at 8 am. https://docs.google.com/file/d/0B6BS4V_hlZC7eUJQYlFLWFY5Rjg/edit?usp=docslist_api

Oneplus One
[ONE Original Android Development] lchiocca:
You know that the log you posted contains some really worrying stuff ;)... you're using whatsapp+ and you've been baned... who is "Henry MT Emptyness"? And you look great in your "Pacific Ocean" t-shirt ;) And try to reauthenticate facebook - it's complaining a bit too often.

But for you're actual problem, I don't see anything in the log that shows the alarm to go off... I really don't think this is kernel related.

Edit: If I were you, I'd remove that log... it contains way to many phone numbers (Family and friend and xda?!)
[ONE Original Android Development] maxver0:
No im not using wa+. Henry is a friend. What t-shirt?

Oneplus One
[ONE Original Android Development] lchiocca:
I don't know how to put it, but in the log, you've got a couple of whatsapp URLs that allow anyone to download the images/videos that were received/sent during the log. I'm just going to post one to show you (something not to 'private'): https://mmi634.whatsapp.net/d/Ktmvt...tCTBe4Y0CiZHzUXnI_fDljgtGEg_Wmex3_DwCnB8e.jpg
[ONE Original Android Development] tobitege:
OMG... Edward Snowden is doing a facepalm right now... :silly:
[ONE Original Android Development] maxver0:
*. * So what's wrong with my alarm :(

Oneplus One
[ONE Original Android Development] NickosD:
Are you using wake lock blocker?

Sent from my bacon!!!!!
[ONE Original Android Development] lchiocca:
Like I said: I don't know. It didn't trigger any events. But I really doubt that it has anything to do with the kernel. btw. What rom/cm version/alarm app are you using? Might help a bit to know a couple of details.
[ONE Original Android Development] magnamentis:
we don't know of course but did you try this: settings>apps>clock>clear data and cache ?

basically the first thing to do with any app that misbehaves. if yes, sorry for bringing up the obvious, if not, hope it solves your issue :) good luck
[ONE Original Android Development] maxver0:
Lastest blisspop, Ive made clean flash (without wiping data) three times already. Stock clock app.

No I haven't, will do! I haven't thought about it before. Silly[emoji21]

Oneplus One
[ONE Original Android Development] andip71:
Honestly, I cannot say.

Also the logs will not tell us anything here.

I am using 100% stock wifi drivers, completely untouched. So it must be something else in combination. But what? I dunno, especially as I never had any wifi issues ever.

Ok, understood. Still sad to lose you...

Aha? This is interesting. Which rom did you update from and to?

Because of course the kernel survival method only works if the rom installer script calls it. CM12 stock does it, CM11 too, CM11s not, and for all the custom roms around I cannot comment without looking into all their installers.

BTW - are you sure it is still switched on in the app?

Because if you restore a nandroid from a state it was not enabled, it will also restore this state back (even if it was enabled before).

This is an effect that does really not have anything to do as this is 100% rom functionality.

The only thing I can imagine is, you might have a very agressive configuration. I.e. undervolting, underclocking, battery saving governor (try with interactive for a regression test please), multicore energy saving activated etc.

You should check these points.

Andi
[ONE Original Android Development] andip71:
Hi,

I was just trying to debug this error, put all debug code in, also merged the latest kernel commits in.

And then I tried to debug and could not replicate the problem anymore (still trying, but it caps the cores correctly now, hmmm).

So I am asking to all that noticed this issue, if someone is interested in joining me to replicate the issue with a test kernel.

If interested, please PM me.

Thanks

Andi
[ONE Original Android Development] Pablo.x:
There is the problem. Stock WiFi drivers are the ones that gives the error in some devices.

For example, ak kernel v80 or tyr kernel v62 don't give that problem, but if you use lastest version of those kernel, WiFi turns unstable.

Could you try to make a version with those Wi-Fi commits that works for those who have WiFi problems? :)

I hope everything is understandable.
[ONE Original Android Development] maxver0:
Im running zzmove with moderate, UV - 75(tested it and its running stable) , GPU underclock 27-380 Also i disabled system logs. It used to be just fine.

Also It didnt happened earlier but I have no idea what could be possibly causing it because alarm works itself (I disabled all connections and left it on the desk for hour). But when i left it for whole night 5+ hours it didnt wake. It was set on 8:00. My dad woke me up and I seen on my phone notification *You have missed alarm 8:00*. And yes i have enabled alarm sound :D

Oneplus One
[ONE Original Android Development] andip71:
It is understandable. But I am sorry, I am not putting again different wifi drivers in.

They work fine for some, but make as well issues for others.

I had already some in in the past, but not planning to do that again.

My objective "close to stock" means, I wait till there is an official update for it.

Thanks for understanding

Andi
[ONE Original Android Development] andip71:
UV -75... no comment.

Even when you say it is running stable, this could be the issue for you.
[ONE Original Android Development] maxver0:
Comment, go ahead I would like to know your opinion.
[ONE Original Android Development] Pablo.x:
Well, that's logical.

But a last question.

Do you have any version of your kernel with those wifi drivers?

I thought that alpha10 had it, but when I flashed over temasek 5.5, I was not able to activate WiFi :(
[ONE Original Android Development] andip71:
Quoting from the OP:

"I will refuse to give support if you do any undervolting and experience freezes or hot reboots."

Do I need to say more?

In other words: Do not UV if you face any issues. All can happen, even if you think it is good.

Oooops, I think that was back in November on the cm11s kernel only.

So sorry, no.

Andi
[ONE Original Android Development] maxver0:
It was working just fine in previous releases with -75mV. PSV lvl 9. I'm not facing any other issues, no reboots etc. Just this god damn stock clock :D
[ONE Original Android Development] andip71:
Well, it is completely your decision.

Either you try what I recommended, or you leave it.

But as said: Undervolting = no support by me. I am not trying to hunt phantoms that are only caused by that damn undervolting.

There will come the day when I remove it...

Andi
[ONE Original Android Development] maxver0:
:good: Cleared cache of clock and set undervoling to none, will see how it goes :fingers-crossed:
[ONE Original Android Development] andip71:
Finally :)

Thanks for being open to the consultancy given. If it turns out I am wrong, then you need to search in other areas (rom etc.).

The worst are "consultancy-resistent" users that do not even try what they have been recommended :)

Andi
[ONE Original Android Development] maxver0:
We learn something new everyday :fingers-crossed: I was against undervoling at first, but then I read some article/tests here on XDA and I was quite impressed so I tried it on boeffla because why not.
[ONE Original Android Development] andip71:
Nothing against trying things. I am the same.

But whenever something odd or weird happens, undervolting is the first thing that must be reverted for doing more analysis and testing.

Andi
[ONE Original Android Development] andip71:
Quick update:

I am currently testing the upcoming beta6 version for CM12.

There were a huge mass of new kernel commits to the CM repo the past days.

If all is well, new beta for all tomorrow.

Andi
[ONE Original Android Development] magnamentis:
did i miss beta6, cannot imagine that i missed a version ? but still things can happen :)
[ONE Original Android Development] andip71:
No, you are fully right.

I mixed it up with the version of the CM12 kernel for the S3...

So it is, of course, beta6 :)

Thanks for spotting it, I corrected it already.

Andi
[ONE Original Android Development] maxver0:
Also nobody replied to my issue on blisspop rom thread :crying:
[ONE Original Android Development] HaTrED_:
Itchy... Itchy... [emoji16]
[ONE Original Android Development] eagleeyetom:
[MENTION=947981]Lord Boeffla[/MENTION] I must say that I love your kernel. It's rock solid and customized charging is a must-have for me. Phone charges crazy fast. Danke!
[ONE Original Android Development] andip71:
Tomorrow [emoji3]

Mainly changes around camera which the CM guys committed today.

Thanks, sounds like a happy user.

Andi
[ONE Original Android Development] magnamentis:
not true, you got many answers including from me, how comes you're telling stories here, that's not motivating

this the link for refreshing your memory: and then you are very reluctant with the thanks button in general, perhaps that helps go get more answers (just kidding) of course NOT :)

http://xdaforums.com/showpost.php?p=58349494&postcount=2347
[ONE Original Android Development] maxver0:
:silly:
[ONE Original Android Development] magnamentis:
it is indeed, sorry for oversight of that little detail :) so i assume it did not work for you.

so try to uninstall the clock app after clearing data and cache and dirty flash the rom again, so that the app will be installed "clean" that's how one sometimes can get around an entire clean flash if only one or two apps are having issues.

this happens sometimes when following kernel and rom thread with the same users on both, just dont' check the thread title each time something catches ones attention.

i hope i can make up for it with the above workaround, it worked for me many times but dont' restore form TiBu, that would make the move obsolete.
[ONE Original Android Development] ek69:
Gonna check out this kernel thx for it :) hopefully I can squeeze some more battery out of it

Sent From Lollipopified Bacon Goodness!
[ONE Original Android Development] NeGriTa79:
Hello [MENTION=947981]Lord Boeffla[/MENTION], which settings you are using right now ???
[ONE Original Android Development] maxver0:
Lord Boeffla is using different settings all the time, he keeps testing new stuff etc. Answered before. Check boeffla sharing kernel profile thread or something like that :P
[ONE Original Android Development] andip71:
Absolutely true.

I am not "stable enough" in my settings.

Nevertheless I am on zzmoove + zzmoove moderate profile with zzmoove native hotplugging at the moment. Max CPU reduced to 19xx Mhz, GPU max to 27 MHz.

Deadline scheduler.

Andi
[ONE Original Android Development] Roulianooo:
Can't wait to test beta6 :p
[ONE Original Android Development] andip71:
I am about to create the change log and push it soon.

Andi
[ONE Original Android Development] andip71:
Update for all kernels...

Hi all,

after I returned back from my business trip yesterday night, I now provide you kernel updates for all three active kernels: CM12, CM11 and CM11s.

CM12 - Version 3.0-beta6

23.01.2015

Reported issue about not working hotplug profiles (e.g. restricting to 2 cores only etc.) seems to be resolved, could not replicate it anymore

Updated with latest >50 CM kernel commits for CM12 until 23.01.15 (-> c2b66bcd5), those are mainly camera related by the way

Removed a few optimisation commits for stability purposes

Ramdisk updated to official nightly of of 22.01.15

CM11 - Version

2.1 stable

23.01.2015

Updated with latest CM kernel commits for CM11 until 23.01.15 (-> f0a2e1d)

Removed a few optimisation commits for stability purposes

CM11s - Version

2.1 stable

23.01.2015

Removed a few optimisation commits for stability purposes

Enjoy

Andi
[ONE Original Android Development] DjDiabolik:
Updating the Config APP and flashed the 2.1 stable........ whitout problems as always :)

Little question:

After i have successfully resolved whit OTG and my controller PAD... using this kernel there exist a method to connect the bluethoot version of controller 4 xbox360 to my OPO whitout any trouble ?
[ONE Original Android Development] jgcaap:
Lord did your last update include the glitch fixes from cm?
[ONE Original Android Development] suaverc118:
So is there no more pegasus? I flashed this and had trickster mod already, so I don't think it went with stock settings. I also installed the apk to work with this kernel. Any tips on getting this close to your stock Boeffla?
[ONE Original Android Development] suaverc118:
Is this the default for this kernel?
[ONE Original Android Development] Leicxan:
No, default governor is interactive ,scheduler is row
[ONE Original Android Development] andip71:
If you have a specific commit in mind, let me know and I check.

Basically beta2 of my kernel is built on kernel shipping code for kernel 38R + all reasonable cm commits until 10.10.2014.

I just merged chages of last night (incl. newer wifi drivers -> do not work, will revert them again) in, so next beta will contain of course all the latest cm commits as well (I will always rebase to the cm-11 branch as good as possible until the shipping tree gets updated again).

No, pegasusq is not contained in that device/kernel. I have that on my list for a potential port (or to check if it is worth/doable), but more on the mid-term list after I can be sure everything is fine with my first kernel versions.

No. interactive is the default.

Simplest is to reset your profile in the app's profile maintenance screen. Then you have defaults again.

Andi
[ONE Original Android Development] Leicxan:
I uncheck the enable full busybox checkbox in boeffla config. but the busybox version is 1.22.1 2014-1-29, stock one is 1.22.1 bonic 2014-10-6.
[ONE Original Android Development] andip71:
Yes, and? What is the problem exactly?

Kernel busybox is in /sbin and is version 1.22.1 2014-1-29.

CM busybox in /system/xbin is 1.22.1 bonic 2014-10-6.

Andi
[ONE Original Android Development] Leicxan:
I didn't check enable full busybox.And the description of this option is enable kernel busybox to work as full-blown busybox known to the whole system.So i think the default busybox is cm busybox not the kernel busybox.Correct me if i'm wrong.

edit: Type busybox in terminal , it shows 1.22.1 2014-1-29 and i didn't check enable full busybox option.
[ONE Original Android Development] brunsman6229:
@ lord boeffla! very nice to see you here, i'm a old user of your work since galaxy s3... i have a question.

since i updated to xnph38R, i have a very good battery, just loose 1% in a night of 12 hours...; if i flash your kernel, is this will affect my battery life? (with your stock kernel settings)

also thanks for your work
[ONE Original Android Development] andip71:
Yes, because /sbin is in the path before /system/xbin.

So when you do not fully specify the busybox path, it takes the one it finds.

The full busybox option just means, it will symlink all applets to the kernel busybox. Nothing else.

As we are here in the CM world, which comes with a full busybox already, this option is not required anyways to be used.

Nobody would be able to guarantee that of course.

But as my kernel has nothing implemented that should jeopardize it, I would assume it should be the same as long as you do not change the kernel configuration in some weird way.

But the only way to find this out is to try it...

Andi
[ONE Original Android Development] RCT1:
I'm on franco kernel, is it necessary use come kernel cleaner, or like on S3 it's just flash?
[ONE Original Android Development] osmosizzz:
Surprisingly, deleting the Boeffla folder helped remove the bootloop I had when flashing another kernel. Anyways, I was totally ok with the kernel until I started to listen to music. Before this phone I used the LG G2 and a custom kernel that used faux sound, also use ak kernel which has faux sound and it does make a difference in clarity of music. Will it be possible to add this specific audio modification?

Sent from my OnePlusOne
[ONE Original Android Development] NickosD:
There is a restore script in boeffla kernel data folder that brings back the default values.
[ONE Original Android Development] sui81:
[MENTION=2040569]jgcaap[/MENTION]

Witch settings did set to Boeffla Kernel ?
[ONE Original Android Development] andip71:
I reverse engineered faux sound and Boeffla Sound does the same modifications.

So I will not implement faux sound of course.

Deleting the folder avoided your boot loop? That's interesting. I think you have a miracle opo [emoji2]

It makes zero sense, but most important is, it works for you.

Andi
[ONE Original Android Development] andip71:
Not sure how Franco kernel applies it's settings. But I would suspect it is just a flash.

Make sure no scripts are left in your init.d folder if something behaves strange (that is a general statement...)

Andi
[ONE Original Android Development] RCT1:
With your app I've cleaned init.d. folder and wiped dalvik cache, just in case...

Thanks for all your support since S3!

Edit: Is ASV level the same as in S3? The better "quality" of processor?
[ONE Original Android Development] anybuddy:
Hi Andi, thanks for your unofficial CM11 genuine Kernel, works really great and it seems, the Batterylife is quite similar to AK's Kernel. Here is my small contribution, to make the Kernel official :victory:

6XS265465V7658340

I have also a request. Can you please add the Slim Governor and a min. max. Frequency for Screen off?
[ONE Original Android Development] jgcaap:
Can you also be able to enable mic modification?

---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------

Nothing major.

Interactive + row + swapiness at 10% here I cannot edit much more where is kernel supported =p
[ONE Original Android Development] Han-Droid:
Just to make it clear for me:

Should init.d be completely empty ?

I found this:

99superSudeamon

00banner

90userinit
[ONE Original Android Development] andip71:
Only via OTG. There are no bluetooth drivers for the Xbox controller available.

Andi
[ONE Original Android Development] gondsman:
That's mostly because the x360 wireless pad is not bluetooth. :p
[ONE Original Android Development] supermax:
Hello everybody

I am using multiboot with Stock CM11S + Version 2.x Boefla Kernel in Primary and cm12 Kernel version 3.x in official CM12 nightlies in secondaty.

All OK with Beta4 Kernel in secondary.

I Tried Beta5 and Beta6 but I obtain a boot loop while CM is starting.

I tried to clean Dache but no success.

I reinstalled Beta4 and all ok.

Any Suggestion?

Thanks
[ONE Original Android Development] andip71:
Yes, you have an outdated rom which does not apply the latest firmware.

Read here from this post downwards.

http://xdaforums.com/showpost.php?p=58367971&postcount=82

Andi
[ONE Original Android Development] supermax:
Thank you very much!

One question

Do I have to flash Modem in Primary or secondary partition? ( In Cm11s or CM12)?

Thanks
[ONE Original Android Development] waterdaan:
Cm11 and cm12 use different modems

So if you flash the cm11 modem you'll probably have problems on cm12 and vice versa

If you've flashed cm12, the cm12 modem is included
[ONE Original Android Development] tobitege:
Since I wrote a related reply in another thread, copied it here:

Let's see if I can answer for better understanding: since 2 weeks ago most custom LP roms require a newer firmware than we had with KK/CM11.

So if you need KK, you must flash before a CM11 firmware (or factory image) again to get that firmware, a flashable firmware-only ZIP for CM11 I have here: https://mega.co.nz/#!iAlzGTQJ!WfxRiJVhA9Q-H_6AKD1tt4eEhf4VEEXlBsT22UpjpII (originally taken from official CM11 nightly).

Flash firmware always on primary recovery screen, not from within MultiRom, regardless which rom you want to boot next.

If you want to use your KK rom, flash the above firmware first in recovery; if you want to use LP rom again, flash the CM12 firmware again (from my sig).

Once a firmware is flashed, it stays/persists across rom installs/updates/wipes, so you'd only need to flash it once for either staying in KK or LP.

Edit: fixed copied/pasted mega link
[ONE Original Android Development] andip71:
-- deleted --
[ONE Original Android Development] DjDiabolik:
Ok....

You are really sure ?? On youtube there exist any varius method to connect the wireless pad to android device but i thinks this using the microsoft usb adapter at this point.

Otherwise if it's not bluethoot it's wi-fi ? or IRDA ? I don't know any other method to send a wireless signal......
[ONE Original Android Development] gondsman:
It's some kind of 2.4 GHz wireless connection, but it's not the standard wi-fi interface, so it requires an ad-hoc usb dongle to use. :/
[ONE Original Android Development] fards:
The 360 uses a proprietary multi layered rf 2.4ghz connection.

The Xbox one uses a hacked up WiFi direct one.

To get the wireless 360 controller working with android you need the PC receiver connected to a usb otg host cable

It's easier to just use a wired 360 controller.

The nvidia shield tablet controller works using WiFi direct. That's a great piece of kit. I haven't tried it with opo (no real need) but it also works on PC with USB cable better than the Xbox PC controller!
[ONE Original Android Development] molonad:
Hi, iam sorry that iam repeating myself but two cores only work till I lock my devise, when I unlock, all cores are working again ☺ cm12 temasek 6.0 beta6.
[ONE Original Android Development] NickosD:
No issue with zzmoove hot plug, 3 cores off

Sent from my bacon!!!!!
[ONE Original Android Development] andip71:
Can't replicate this anymore on latest cm12 nightly...

Andi
[ONE Original Android Development] molonad:
So you don't have this problem? ☺I don't understand exactly what is replicate - replicate - copy?ok I will just use zzmove native hotplug and in tuneables I will turn off cores ☺