yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] 3Dota:
hmm ... I'll try again later then ...

I'm not installing your SU zip previously ... will report back later then ...
[Moto Maxx Android Development] quantum tao:
is this to make android pay work, credit, bank apps?

i realize it hides su but how would i test in real world situation?

i currently dont have anything that makes me need this but i would like to help test it, is why i ask.
[Moto Maxx Android Development] fgl27:
Theoretically it can be used to pass Safety net verification but, I too can't test for android pay and other related I have no place to test it here.

There is apps like that Pokemon game that need this, it seems to works ok on that...

Is a simple feature that I will improve and can be of great help on CM base ROM and those none ROOT blocker apps...
[Moto Maxx Android Development] 3Dota:
[MENTION=5747496]bhb27[/MENTION] ... my xt1254 become blazing fast ... :angel:

your recent kernel [202] work superbly in the end ...

full unroot from SuperUser app ... power off device ... reboot to recovery... install kernel ... install kernel auditor ... install SuperUser beta you provided ...

blazing fast lol ...
[Moto Maxx Android Development] vinydasilveira:
After this last update, my phone is heating up more than normal and some games after a certain playing time, simply close. Flash made a clean because it was installed together with the ROM RR. I installed the V201-9-M version and returned to normal.
[Moto Maxx Android Development] fgl27:
What you change in kernel?

What is the thermal setting?
[Moto Maxx Android Development] pedrohxn:
[MENTION=5747496]bhb27[/MENTION] I'm facing an issue with the camera right after flashing the new kernel...

The camera app displays "Can't connect to the camera".

I'm pretty sure that this doesn't have anything with the kernel itself but, strangely, happens after flashing it.

I have tested 3x and it happens everytime.

Flashed kernel > Camera stopped > reflashed rom > camera works > flash kernel > camera stopped > reflashed rom > camera works > flash kernel > camera stopped...

I checked the system logs and I found an error with the mm-qcamera-daemon. Googled it and I found it was a very commom bug in previous Android versions.

Trying to fix it, but I'm almost out of options.

Any ideas?
[Moto Maxx Android Development] vinydasilveira:
I did the same thing I've always done. Decreases the power to 1.5GHz on 4 cores. I put the CPU in covernor conservative. The beginning of sync, I put in 960MHz, the core of the pulse frequency, I put on 729mhz, all core. The GPU 500mhz in powersave. And I used to put the policy scheduler and powersaving, but this new update is already by default. Only that.
[Moto Maxx Android Development] fgl27:
thermal kernel setting?
[Moto Maxx Android Development] quantum tao:
BHB27-Kernel-V202-0-M.zip is amazing on battery. everyone should just stop installing their greenifys and amplifys and changing all that kernel stuff and leave it as it is. or just ignore me and keep on doing whatever it is you do. like everyone usually does.
[Moto Maxx Android Development] fgl27:
The logs are full of camera logs most are harmless, is really hard to find the one that is the problem between so many...

last V did not change any thing direct related to camera... Have you try clean the camera app data? and clean any config to the kernel app?

this may be related to a app not the camera but one that may have access and you don't know is hard to find...

Last time I get this problem, I reflash the radio.img, clean install did not restore the data of the camera app and all was good, but that was a long time ago...
[Moto Maxx Android Development] vinydasilveira:
It is the default settings
[Moto Maxx Android Development] fgl27:
I finish optimizing iSu apk....

Download Isu apk
[Moto Maxx Android Development] pedrohxn:
Thanks for replying.

So, I think I found out what's causing this error.

I'm on Whatsapp beta program, and I think it is the latest beta version that's causing it.

I'm testing right now to give you a feedback.

As I said before, I'm pretty sure it isn't related to kernel. And I think it was pure coincidence that whatsapp beta was updating right after flashing the kernel and giving me a headache with this error hahahaha

Thanks again!
[Moto Maxx Android Development] fgl27:
Kernel Adiutor update

KernelAdiutor-0.9.9.4.+27.BHB27-Mod.apk​

Download Kernel auditor

Changelog

Installation

APK or ZIP?

If you have building Kernel Adiutor like in RR ROM you must use the zip.

If you don't if install it from play(original KA) or is using my KA apk you must use the apk.

Install APK:

* Install it like any other apk from file manager (like ES File Explorer)

* May be necessary to uninstall the old version first if it doesn't install.

Install ZIP:

* To install the zip 1° uninstall Kernel Adiutor (original KA) if you have it.

* Then flash via TWRP, no wipe is need.

If encounter any problem:

Clear data of yours BHB27 Kernel Adiutor app + deleted the KernelAdiutor and KA_profiles folder from internal memory (if not possible by the android file manager use TWRP one), reboot to recovery and clean/wipe Dalvik and cache before reporting things.

You can make a copy of profiles.json file inside KA_profiles folder (in case you save a profile), after the reboot place it back on the folder then apply the setting on the app, if encounter problem after the apply the profile is the problem deleted it and redo the cleaning and don't use it again...

This helps when the apps functions are odd, misbehaving and or slow to load/display.

Sharing profiles

The only ting need to share a profile is the file profile.json in side KA_profiles folder, it can be just simple copy and past to another devices, the file is very small and easy to share.

Use my version of Kernel Adiutor to better support this Kernel. :good:
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V202-1-M.zip​

Marshmallow only.

Download BHB27-Kernel

Changelog

Note:

Use this with the latest version of my mod KernelAdiutor-0.9.9.4.+27 or up to control the many featuring of the kernel.

Download Kernel Adiutor App

SuperSu support on Stock ROM have change read the TWRP screen when installing it has this warning:

Link for BETA-SuperSU-v2.62-3-20151211162651_3

It need to be fallow if you wanna SU

-----------------------------------------------

Setting up as Stock ROM MPG24.107-70.2

In Stock ROM is need to Reflash ROOT
After a kernel Update, Reflash Su
Demanding! First Flash the Kernel then
Su Version:
BETA-SuperSU-v2.62-3-20151211162651_3
Then Update Su if you wanna

Is possible to do all in one queue
Kernel + BETA-Su + Update Su

-----------------------------------------------

Download iSu app (A simple app to enable/disable of Su works with CM Su binary)

Don't use this on a old ROM version give preference to the newest version, please don't report bugs from a old ROM version...
[Moto Maxx Android Development] pedrohxn:
Anxious for N [MENTION=5747496]bhb27[/MENTION] :D
[Moto Maxx Android Development] fgl27:
Me too, but have not time to make it work today... going to wait to the end of the year wen things are more stable and I have way more free time...

Have you find the cause of camera stop working? to you..

My stop today was working then I open and it stop, the only thing that resolve was clean install, old version of the kernel, or revert to stock kernel by dirty flash did not solve...

So I'm not shore if is a kernel problem, it seems to be a app as clean install solve and dirty not...

I'm running some test but as the problem did only show up today on my device will take long time until it comes back if it does I will know more, if not I know was because some fix I just did...

:good:
[Moto Maxx Android Development] pedrohxn:
It's working fine now... really don't know what the heck was happening!

At first, I thought that was Whatsapp beta or some other app which has media/camera access.

Then I restored a backup from a week ago, flashed the latest kernel and it had 25 available app updates.

Began updating 3 by 3 apps, rebooting and testing the camera, to spot the buggy one....

And, for my surprise, all of them were updated and no issue with the camera.

This makes no sense at all.

I still wonder why... but if it ain't broke, don't fix it, right? hahaha
[Moto Maxx Android Development] fgl27:
Ok, that is good, probably some random thing related to a app, I did only notes it after some apps update...

If it happens again let me know... :good:
[Moto Maxx Android Development] 3Dota:
any chance ISu would work on stock 6.0.1?
[Moto Maxx Android Development] fgl27:
Not my intention to works with SuperSU I let chainfire to work on his project.

check OP

and read below... and fallow that thread...

http://xdaforums.com/showpost.php?p=69021494&postcount=1592
[Moto Maxx Android Development] xboxbr:
maple or noop?
[Moto Maxx Android Development] immadeofpixels27:
[MENTION=5747496]bhb27[/MENTION] Are you planning on integrating the updates from KA into your custom version? Just curious after seeing CPU activity graphs in its store page :good:
[Moto Maxx Android Development] fgl27:
That graphs use the same code for CPU load of the old app is just converted to graphs...

That is not a update, is a new app that took Grarak months to make, I have not intention to use it as is just cosmetic and will take me months to make good as the current is today.

For now is like... Rain on the wet. ;)
[Moto Maxx Android Development] kitcostantino:
i went maple bc i figured it couldn't be that bad. its Maple
[Moto Maxx Android Development] xxspookyxx:
Please help me..

I Cant install Systemless Root Super SU in this kernel, how i fix this?

http://xdaforums.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
[Moto Maxx Android Development] fgl27:
way you need it?
[Moto Maxx Android Development] fgl27:
I update the iSu app there is no changes that affect users of my kernel or ROM...

Don't use it without the flash .zip that is in the iSu download link.

I will update the kernel later and include all need changes to it so will not be need to flash that iSu.zip... the app has it's on thread know...

http://xdaforums.com/android/apps-g...e-activate-t3478348/post69079068#post69079068
[Moto Maxx Android Development] colthars:
yesterday i got this camera problem too. tried flashing rom, kernel, old and last version. nothing solved. tried uninstal apps. nothing. I'm will try a clean install when get back to home.

Enviado do meu Moto MAXX
[Moto Maxx Android Development] mubaidr:
Same thing happened to me too. No camera app was working, flash option went missing from quick settings panel. Removing application, dirty flashing did not solve it. Had to backup and clean install. :confused:
[Moto Maxx Android Development] immadeofpixels27:
For those of you experiencing camera issues: did you change the advanced settings in the hidden menu of Moto camera before the problems started? The last time I had camera issues was immediately after changing those hidden settings and closing Moto camera.
[Moto Maxx Android Development] mubaidr:
I did change camera settings (feature settings in debug), can you specify which of these settings cause this issue, so we can avoid changing it.:confused:
[Moto Maxx Android Development] immadeofpixels27:
I don't know exactly which settings cause crashing, I just know that my camera failed very soon after i changed the hidden settings. It's definitely not all of them; I do have a few changed now. I think the feature settings are the culprit since UI settings should theoretically only effect the app, not all other apps too.

I've attached screenshots of my settings.
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V202-2-M.zip​

Marshmallow only.

Download BHB27-Kernel

Changelog

Note:

Use this with the latest version of my mod KernelAdiutor-0.9.9.4.+27 or up to control the many featuring of the kernel.

Download Kernel Adiutor App

SuperSu support on Stock ROM have change read the TWRP screen when flashing there is a warning fallow it

After it kernel update, reflash SU in this simple order:

Kernel + BETA-SuperSU-v2.62-3-20151211162651_3 + Update SU version

Update Su version not demanding.

Link for BETA-SuperSU-v2.62-3-20151211162651_3

Download iSu app (A simple app to enable/disable of Su works with CM Su binary)

Don't use this on a old ROM version give preference to the newest version, please don't report bugs from a old ROM version...
[Moto Maxx Android Development] mubaidr:
Could it be KPI settings? next to feature settings. I do remember turning it off but not sure if that is the culprit.
[Moto Maxx Android Development] fgl27:
This camera settings makes sense must be some thing conflicting with CM setting...

If you guys find the exactly change that cause a problem let me know here...

I was playing with those then after I get that problem, only fix after clean install...
[Moto Maxx Android Development] immadeofpixels27:
Nope KPI isn't settings, just debug info/logging. The only settings pages are UI and Features.
[Moto Maxx Android Development] colthars:
yeah

i changed some settings on Moto camera....

only solved after clean install

Enviado do meu Moto MAXX
[Moto Maxx Android Development] immadeofpixels27:
I made a spreadsheet on Google Sheets to track which settings are known to be safe or cause camera instability; this way we can work to figure out this problem without bloating this thread.

Link: Moto Camera settings stability

Comment on the spreadsheet if you'd like to contribute to it.
[Moto Maxx Android Development] immadeofpixels27:
I found one culprit: Temporal Noise Reduction. There might be others, but I haven't tested much else yet.

It seems that the camera only breaks after you change settings and then reboot.
[Moto Maxx Android Development] willerson:
SafetyNet updated again

haha, sad, but true, SafetyNet got updated again, so, iSu solution isnt working anymore, using last kernel from Oct/12, working nicely, just safetynet problem haha, can't play PoGo =[
[Moto Maxx Android Development] gangrenius:
I'm sure Google is starting to run A. I inside their code pretty soon everything will be patched in moments.
[Moto Maxx Android Development] fgl27:
It seems to be related to CyanogenMod, it seems I piss them off with my app (joking of course)...

Other implementations that worked on CM are now not working so I have no idea...

complete removing SU and having no other unsafe app or related in the ROM doesn't guaranty a pass in CM anymore.
[Moto Maxx Android Development] Q9Nap:
[MENTION=5747496]bhb27[/MENTION], Thanks for your work on this and twrp!

Do you know what specific modifications to the kernel allow using alternate radios for a given build?

I'm interested in building the 6.0.1 kernel from source for this specific purpose.

Thanks in advance!
[Moto Maxx Android Development] fgl27:
On the other side...

I test my kernel in stock ROM and it works OK regarding safetynet... So the problem is with cyanogem or something related....:eek:

I made a .zip to remove CM-SU and prepare to systemless SU to use in CyanogenMod

This also doesn't work on CM, I just wanna leave it here in case it start work as this .zip is just a fast way to have systemless on CM ROM, and those implementation of SUHIDE or any other may help in the future.

Flash the attached, them flash latest SU version and Suhide:

SR1-SuperSU-v2.78-SR1-20160915123031 or newer

and SUHIDE

There is also this app:

suhide-GUI

I'm not supporting anything here I just sharing info, go to the threads and have fun try not to spam this thread please...

I don't really have time to try and test things now, if any one find something working in the future let me know... after the 10/20 I will have some time I see what can be done...

:good:
[Moto Maxx Android Development] fgl27:
doesn't seems to have relation, M kernel works with any M radio and with previously android radio version. Works better with the latest Radio but works with any...

The only thing that has radio relation it Moto wifi driver that we don't really need. We use the latest from caf works with any radio any ROM stock or CM.
[Moto Maxx Android Development] quantum tao:
Strange problem, Microsoft onenote hasn't worked for me for a while. I could clear the app data and it would work until i closed it in resents or rebooted, then it would just force close at the loading screen. Since it was the only app doing this i thought it was the recent updates from Microsoft that caused it and i let them know how I felt about it.

But, after doing some digging in posts from 2014-15, i found some rooted users who were forcing gpu rendering solved it by unchecking it in developer options.

I did not have it enabled in developer settings so i thought maybe kernel is doing this. I use bhb kernel as is with no changes.

Dirty Flashed rr rom, now onenote works.

Im sure there was some setting in ka i could have changed but i don't know enough about it and would probably make some other problem.
[Moto Maxx Android Development] fgl27:
If you flash the kernel know, the problem comes right after the flash?

Really difficult to me to make a kernel that will affect one app,there is the chance that there is no kernel problem is something else related to system and changes you make to it.
[Moto Maxx Android Development] fgl27:
Kernel Adiutor update

KernelAdiutor-0.9.9.4.+28.BHB27-Mod.apk​

Download Kernel auditor

Changelog

Installation

APK or ZIP?

If you have building Kernel Adiutor like in RR ROM you must use the zip.

If you don't if install it from play(original KA) or is using my KA apk you must use the apk.

Install APK:

* Install it like any other apk from file manager (like ES File Explorer)

* May be necessary to uninstall the old version first if it doesn't install.

Install ZIP:

* To install the zip 1° uninstall Kernel Adiutor (original KA) if you have it.

* Then flash via TWRP, no wipe is need.

If encounter any problem:

Clear data of yours BHB27 Kernel Adiutor app + deleted the KernelAdiutor and KA_profiles folder from internal memory (if not possible by the android file manager use TWRP one), reboot to recovery and clean/wipe Dalvik and cache before reporting things.

You can make a copy of profiles.json file inside KA_profiles folder (in case you save a profile), after the reboot place it back on the folder then apply the setting on the app, if encounter problem after the apply the profile is the problem deleted it and redo the cleaning and don't use it again...

This helps when the apps functions are odd, misbehaving and or slow to load/display.

Sharing profiles

The only thing need to share a profile is the file profile.json in side KA_profiles folder, it can be just simple copy and past to another devices, the file is very small and easy to share.

Use my version of Kernel Adiutor to better support this Kernel. :good:
[Moto Maxx Android Development] quantum tao:
i wouldn't expect you to change anything for 1 app, just thought i would put it out there in case someone else might be having a similar problem.
[Moto Maxx Android Development] fgl27:
I may have phrase it wrong...

In the changes already present on the kernel in relation to the stock, there isn't a single change that can affect a single app, if one change affect one app need also to affect others app and others devices.

That is way I make that question... If yo are shore there is a problem, you need to tell me when it start, tell me version xxx works after version xxx no...

that is the only way to really find and fix something.
[Moto Maxx Android Development] Shooting Star Max:
Something really weird is happening.

My device suddenly rebooted by itself while sitting on a table. It got stuck in the 'Starting apps' stage. Well, I said, I will need to clean cache or something. I did that. It got stuck anyway. I clean-flashed everything, and it still got stuck.

I pinned it down to this kernel, but I can't find any explanation! My device boots well with the stock CyanogenMod kernel. When trying to boot with BHB27 Kernel, this appears in the logcat while the device is stuck at the 'Starting apps' stage:

10-15 01:47:22.903 578 578 I ServiceManager: Waiting for service AtCmdFwd...
10-15 01:47:23.904 578 578 I ServiceManager: Waiting for service AtCmdFwd...
10-15 01:47:24.905 578 578 I ServiceManager: Waiting for service AtCmdFwd...
10-15 01:47:25.906 578 578 I ServiceManager: Waiting for service AtCmdFwd...
10-15 01:47:26.906 578 578 I ServiceManager: Waiting for service AtCmdFwd...
10-15 01:47:26.909 533 671 I ThermalEngine: Sensor:/sys/class/power_supply/battery/capacity:14 mC
10-15 01:47:26.920 533 679 I ThermalEngine: Sensor:max170xx_battery:38000 mC
10-15 01:47:26.932 533 669 I ThermalEngine: Sensor:apq_therm:38000 mC
10-15 01:47:26.937 533 667 I ThermalEngine: Sensor:chg_therm:39000 mC
10-15 01:47:27.063 533 693 I ThermalEngine: Sensor:tmp108:40000 mC
10-15 01:47:27.064 533 693 I ThermalEngine: Sensor:max170xx_battery:38000 mC
10-15 01:47:27.068 533 693 I ThermalEngine: Sensor:chg_therm:39000 mC
10-15 01:47:27.073 533 693 I ThermalEngine: Sensor:wchg_therm:36000 mC
10-15 01:47:27.078 533 693 I ThermalEngine: Sensor:chg_therm:39000 mC
10-15 01:47:27.078 533 693 I ThermalEngine: Sensor:VS-BATT:39600 mC
10-15 01:47:27.907 578 578 W Atfwd_Sendcmd: AtCmdFwd service not published, waiting... retryCnt : 4

That Atfwd thing seems to be the culprit...

Anyway, I hope there's something you can do with this information. Thank you for your nice work, I've been following this kernel since quite some time and I feel grateful.
[Moto Maxx Android Development] fgl27:
There is very little on this post I can't reproduce my device boot just fine over and over don't matter how many times I flash this kernel, the word "AtCmdFwd" doesn't show in my logs at all, and I have on my device the atfwd.apk.

AtCmdFwd is related to Atfwd app with is the "com.qualcomm.atfwd" Qualcomm's WiFi display. Start some related search to that...

There is several situation that can cause this, I today don't seem to be able to reproduce if you know exactly let me know... I recommended one simple test clean install flash the kernel if the problem persist there is a incompatibility if not was some config of yours, after you start changing after the clean install problem appears again is related to something you change...
[Moto Maxx Android Development] Shooting Star Max:
Well, it all happened so suddenly, I didn't even install a new application or something. Still, thank you very much. I will try a completely clean install (wiping data) soon, I hope it will work nicely after that.
[Moto Maxx Android Development] vinydasilveira:
Unfortunately after a few tests using BHB kernel 200-9 with CM13 07/21 also tested the RR 5.7.1 + BHB 200-9, I concluded that the latest updates have less performance and battery dies more fast as the old versions. I have no idea what can be
[Moto Maxx Android Development] hpbrasil:
what is happening with the kernel and the ROM? every update continues losing autonomy battery. the version of bhb kernel 200-9 is lasting very well with the cyanogen the date 21/07, after the updates the battery is increasingly worse. multiple users reporting this.

[MENTION=5747496]bhb27[/MENTION] [MENTION=3250376]ChazzMatt[/MENTION]
[Moto Maxx Android Development] kitcostantino:
Using the latest bhb27 kernel, version 2.02-2 M has been awesome for me. Mind you, i have it scaled back for battery. at like 1190mhz. i was playing around with the new options in bhb27 Kernel Aidutor v28 and running high/low cores (2496[core0,2] /1180[core1,core3] ) earlier today, and then decided to test low speed (1180mhz) to see if battery was good. if all one does is apply the kernel updates and change no settings, i do not believe an improvement will be yielded.

My day started at 0700. Now, 13 hours later, battery is depleted a bit. Also, my Screen On Time is exaggerated by my Moto Display replacement app. Still, great battery for how excessively i have used my Droid Turbo today. many thanks again [MENTION=5747496]bhb27[/MENTION] !!!