yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] incognito369:
Yes I have busybox installed. Just tried the latest beta of ka to confirm. no change. Max freq was set at 1363 and also tried higher freq plus both min and Max set at 1363.

Previously I had experimented with different root options and hadn't noticed a difference. Used SuperSu, phh's superuser and cyanogen mods built in root.
[Moto G 2015 Original Android Development] dazeone:
Using SuperSU 2.78 here, but don't know if it makes a difference.
[Moto G 2015 Original Android Development] incognito369:
Don't know if it matters but all GPU freq seem to work fine.

Also want to add a list of which kernels I have tried and if the CPU freq scale properly on my device.

Kernels that scale to all included freq.:

-Agni

-Optimus

-Shield

-Squid

Kernels that don't scale above 800mhz:

-EplosionReborn

-Fire

-Ruthless

-HelpMeruth's modified Squid and Optimus kernels.

Note, I have tried at least a few versions of each kernel in the time that I have had this device, but haven't tried all versions.
[Moto G 2015 Original Android Development] Nitg16:
Please don't remove overclocking. It is the main reason I use this kernel. Its working fine for me on cm13.
[Moto G 2015 Original Android Development] thinkfreedom:
Sure, I would love to test. Thanks for all your efforts. :)
[Moto G 2015 Original Android Development] Mukesh kalaga:
Can i flash on stock 6.0.1 having bootloader unlocked and twrp recovery
[Moto G 2015 Original Android Development] rwxr-xr-xis:
Yep
[Moto G 2015 Original Android Development] Acidfire.TM:
[MENTION=5510849]incognito369[/MENTION]

your nuts bro never had these issues ever

and been using since 4.0

have thoroughly tested/benchmarked firekernel

and it performs properly at all frequency up to

1.593Ghz. have tested it on many many Roms

so I suggest you choose a different Rom

do a full Clean install

including *formatting your Data partition.

boot up once with Roms Default Kernel.

now Install Firekernel.

and if you still have issues, try a different kernel tuner.

ps. firekernel smoked every other currently available kernel **at equivalent frequencies and identical setup***. the only one it didn't smoke

was our RuthlessKernel, which tested pretty much equal to firekernel.

Tests I used are, Game Engine Benchmarks,

Real time Cpu/Gpu load monitoring.

also compared geekbench 3 scores amongst

all of them, squid kernel performing the worst by far in geekbench.
[Moto G 2015 Original Android Development] Acidfire.TM:
maybe your hardware is screwy, because it's working fine for many many people
[Moto G 2015 Original Android Development] love4chat:
Waiting for Merlin release...
[Moto G 2015 Original Android Development] Tonystarki:
Send link ka mod?
[Moto G 2015 Original Android Development] acejavelin:
Last I heard, [MENTION=6257538]FireLord[/MENTION] is going to tame it down, not remove it. Benchmarking has shown overclocking over 1536 (?, might be off a little in exact number) has no real effect on performance and can actually quickly overheat and cause slow downs because of it.
[Moto G 2015 Original Android Development] sfoot13:
;) https://androidfilehost.com/?fid=312978532265361992

here's a flashable zip too, if you want... https://androidfilehost.com/?fid=312968873555002799
[Moto G 2015 Original Android Development] Acidfire.TM:
1593

yes, I have tested extensively,

anything above 1.593 seems a little to much for the little low powered a53

although everyone's hardware will be slightly different

due to minor manufacturing inconsistencies.

so very few ospreys will clock above 1.593

and still be stable enough to work well.

although I have a feeling slightly higher frequencies could be accomplished playing with voltages.

accomplishing a stable frequency 200+ mhz above

the designed clock speeds, is still pretty awesome.

although the number doesn't mean crap and

having frequencies that are to high set on default

causes fire kernel to make phones heat up hugely

upon boot as it "optimizes" packages.

and then if inexperienced users try and use the

extreme defaults he or she will get the wrong impression of the performance of the kernel

as it stresses itself to run at a blistering 1881mhz

that means all the caches and other parts of the cpu not designed to run at that voltage and frequencies are struggling to keep up with the extreme clock speed.

same goes for the GPU but 650 seems to be the highest frequency before the gpu will start to overheat and perform badly due to instability.

problem of inexperienced users deeming fire kernel

ineffective

could be remedied by having the default clock

speed set to 1.497 (a frequency I believe is achievable on any a53.)

*this frequency generates little to no extra heat*

on my handset it generates no extra heat.

and I get a noticeable boost in performance

in everything from web surfing/scrolling to

higher fps in media and games

also faster video conversion

(mkv to mp4 tested)

and for the GPU 550mhz, I'm certain this will be achievable on any osprey as well.

on mine and others handsets this frequency

will not generate any appreciable extra heat on the gpu. and performs better than stock speeds.

it has been said that for the osprey the second biggest bottleneck in the performance of the phone

is the Adreno 306 (essentially the same GPU in the

moto g1 falcon) that achieves a similar clock speed at a lower power consumption, meaning it's likely

slightly underclocked and a tiny bit more powerful than the 305 because it can be overclocked without generating as much heat.
[Moto G 2015 Original Android Development] incognito369:
http://xdaforums.com/android/apps-games/kernel-adiutor-mod-singularity-kernel-t3333549
[Moto G 2015 Original Android Development] Nitg16:
Thanks for the advice. I am now using 1593-650 combo.
[Moto G 2015 Original Android Development] n0ts0smart:
[MENTION=6257538]FireLord[/MENTION] any possibility of adding support for Mako hotplug? Provided you have the time and motivation to do so. If not still the latest kernel is excellent. Running extremely well without issues since it was available. Great work.
[Moto G 2015 Original Android Development] kailasraj97:
dt2w is in which settings?
[Moto G 2015 Original Android Development] Gravemind2015:
See changelog v5.3 in 2nd post. It has been removed.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] ranaxda200:
I'd suggest not to use that feature. That caused screen off issue while calling so even dev suggested not to use that.
[Moto G 2015 Original Android Development] FireLord:
https://www.androidfilehost.com/?fid=457095661767100496 done. tested on stock , seems stable on it dunno about on custom roms
[Moto G 2015 Original Android Development] love4chat:
Thanks Bro,Will Test On RR N DU Roms Of Urs!

Anyways it's asop based or cm based...
[Moto G 2015 Original Android Development] FireLord:
Its for all ROM.. If this supports stock then it should work with all custom ROMs :)
[Moto G 2015 Original Android Development] love4chat:
Thanks bro,seems like U r the only support for MERLIN..

Hope to see two build 3.0.0.2 for MERLIN too...
[Moto G 2015 Original Android Development] FireLord:
That twrp by squid is fine.. After all its stable and we just use it to flash ROMs and make backup from my side updating it isn't problem but its for no use.
[Moto G 2015 Original Android Development] love4chat:
Thanks bro but it would be better if TWRP would be of latest version...
[Moto G 2015 Original Android Development] Vink67:
Your FireKernel 6.1 works really great, good job.

But I have a small trouble, it's not related to your kernel because I have try other and same result.

Minimal Cpu frequency would not stay at 200, it's always go up to 800.

That's happened after CM13 update, I think it's related to Cyanogen.

Can I do something in system files maybe?

If someone have an idea?

Thanks

Sent from my MotoG3 using my finger.
[Moto G 2015 Original Android Development] Nikos dima:
Hi [MENTION=6257538]FireLord[/MENTION] .. Can you make your kernel to work with cm14?.

I was using your kernel in cm13 and I want to use it in cm14 too because stock cm14 kernel is not good.

Sorry for bad English :p
[Moto G 2015 Original Android Development] HelpMeruth:
Set battery mode to efficiency, that should fix it ?
[Moto G 2015 Original Android Development] Vink67:
Thx I will try that.

Sent from my MotoG3 using my finger.
[Moto G 2015 Original Android Development] Vink67:
Really strange, for three days without changing battery mode it stay at 200. Just after your post that problem came back !

So I switch battery to efficiency and voila !

Stay at 200 again....

Sent from my MotoG3 using my finger.
[Moto G 2015 Original Android Development] HelpMeruth:
[MENTION=6257538]FireLord[/MENTION]

are you really overclocking to 2 Ghz?

would be fun to watch how hot osprey can get :P

i hope it actually gives more performance
[Moto G 2015 Original Android Development] sticktornado:
We can either be nearing the limit that osprey can hit, or be nowhere near the limit, but we don't want to fry the processor. I'm not sure if I'm looking at that properly, but it looks like we're pushing nearly 1.4 volts through already.

qcom,cpr-init-voltage-ref = <1000000 1150000 1390000>;

Still, I'd love to see how much we can get out of this device, since even the 16gb model is now retailing at just $90 at my local Best Buy!
[Moto G 2015 Original Android Development] FireLord:
No faking. Such weirdos over XDA
[Moto G 2015 Original Android Development] jody2k:
2 ghz could be easy reachable pretty sure of that
[Moto G 2015 Original Android Development] sticktornado:
So does this mean that it is or isn't happening?
[Moto G 2015 Original Android Development] FireLord:
I haven't said anything on XDA about it. So that means I'm still testing and if works then only I'll release it.
[Moto G 2015 Original Android Development] HelpMeruth:
Let's do some benchmarks, I'll upload soon if anyone wants to play with it.

edit:

for me it only gives +- 15 more point in geekbench 4

please dont hate on me :P they are my tests yours may have different results.

heres a private modded squid kernel with 2Ghz: download it works with nougat aswell
[Moto G 2015 Original Android Development] sticktornado:
Only scoring 530 in single core and 1328 in multi core. Weird.
[Moto G 2015 Original Android Development] HelpMeruth:
... That's your fault I guess
[Moto G 2015 Original Android Development] sticktornado:
Maybe hotplugging or the CPU governor affected the score. What did you use to get that kind of score?
[Moto G 2015 Original Android Development] HelpMeruth:
Set min freq to 2Ghz gov lionfish and disable hotplug
[Moto G 2015 Original Android Development] WaxysDargle:
ummm we are talking about the osprey, right? you are setting min freq to 2GHZ? i hope you have an extra osprey, because you are burning out your current one.
[Moto G 2015 Original Android Development] HelpMeruth:
Not really.. Its for benchmarking purposes ;) I never recommend setting your device to max freq for a long period of time. The heat isn't an issue anyway.

Also I did some research and found out overclocking the GPU doesn't do anything, I achieved 1000mhz and didn't saw any extra heat or fps boost
[Moto G 2015 Original Android Development] WaxysDargle:
LOL well there's a lot wrong with what you just said, but most of all:

why test benchmark settings that you are never going to use? what is the point of testing if it's unusable? what is the goal?

and i don't literally mean you are burning it up... i mean your device will last only a few weeks or months, instead of years... if you continue to overclock like that. that is a fact.
[Moto G 2015 Original Android Development] dazeone:
Is that with 2ghz setting?
[Moto G 2015 Original Android Development] HelpMeruth:
Yes geekbench 4
[Moto G 2015 Original Android Development] Acidfire.TM:
Well, that doesn't mean it's not doing anything

I have seen definite benefits up to 650

Try testing with antutu 3D benchmark

Overclocking the gpu, is much much different than cpu.

And clocking too high will not likely cause much extra heat .

It will however, not work great.

There's an ark to the benefits of gpu overclocking and once over that ark, the benefits stand still or go backwards
[Moto G 2015 Original Android Development] HelpMeruth:
my final opinion on overclocking osprey is that it is not useless, but does not enhance normal daily usage.

and lets be real, people that buy osprey don't expect good gaming just a smooth email reading experience(for example)
[Moto G 2015 Original Android Development] dazeone:
For those wanting somewhat a good gaming experience but not want to keep performance up while not in use and maintain good battery. I recommend using a Tasker app and setup profiles. On intense task I enable all cores at 1881hmhz max, but doesn't mean all will be maxed and better scheduler and governor for performance. When I close the app it reduces to 1201mhz dual core battery saving governor and scheduler for battery saving. Tasker's and profiles give you the best of both performance and max battery. IMO of course.
[Moto G 2015 Original Android Development] Acidfire.TM:
Terrible recommendation 1881 doesn't perform properly

Due to it being a low powered processor originally clocked at 1.4

Its an absurd oc, you think your phone is fast??

Try lowering the oc to 1.59 it performs much better.

With 1881 causing bad performance on heavy load.
[Moto G 2015 Original Android Development] FireLord:
Amazing so much stuff for 2ghz oc when the op haven't released yet. And other guy is posting some other kernel here. Why don't you put all stuff on your thread?

I may sound bad but you are actually advertising your stuff here and ruining my thread.
[Moto G 2015 Original Android Development] Gravemind2015:
I am getting awesome battery life, about 5 1/2 to 6 hours of SOT on v6.1. Device was warming up a little bit in v5.6 but now it's all cool. I am using Darkness cpu governor with no hotplugging, 1401 Max, 400Min (efficiency battery profile). Thank you dev for this highly customizable kernel, one of the best as a battery-friendly kernel. :D

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] dazeone:
On 1.59 camera hdr took a second longer to process and any movement caused it to slightly blur. No issues on 1881. Snap snap snap and images process quick in hdr. My benchmarks were higher and my phone had no issues loading apps quick. And swapping between apps is almost instantly.

---------- Post added at 10:49 PM ---------- Previous post was at 09:55 PM ----------

As I mentioned in a couple comments above about running 1881 with Tasker and lower frequency dual core setting. I used my phone a lot with my performance apps. I watched YouTube, took pics, social media, texting and calling and battery was like this
[Moto G 2015 Original Android Development] Mukesh kalaga:
While using this kernel if i flash stock 6.0.1 osprey then will i get stock kernel
[Moto G 2015 Original Android Development] Gravemind2015:
Yup.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] Aditya_001:
Merlin version is also working great no problems so far....
[Moto G 2015 Original Android Development] cesarXP:
Which configuration you use?
[Moto G 2015 Original Android Development] Aditya_001:
Impulse and fiops.. Rest all left unchanged default... Zzmove is also working fine...
[Moto G 2015 Original Android Development] cesarXP:
OK I will test, wich version you use?
[Moto G 2015 Original Android Development] Aditya_001:
FireKernel-mm-merlin-v6.1-08102016
[Moto G 2015 Original Android Development] FireLord:
osprey- https://drive.google.com/file/d/0B6OvQA_EFUcxalM0dm1KSWVra1k/view?usp=sharing

ChangeLog v6.2

-Linux: 3.10.104

-Latest merge from cm(cm-13.0)

-Tweaked thunderplug from dev-harsh for quad devices

Wish u all a very happy diwali :D
[Moto G 2015 Original Android Development] Realz4747:
Sorry for this dumb question, but what are the consequences (positive and negative) of disabling these wakelocks?
[Moto G 2015 Original Android Development] Gravemind2015:
Maybe they help save battery a bit. I am interested in these too :)

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] FireLord:
ChangeLog r7.0

Nothing.. just added support for android n roms :D

https://www.androidfilehost.com/?fid=529152257862677514
[Moto G 2015 Original Android Development] TheForce:
Thank you [emoji4] [emoji106]
[Moto G 2015 Original Android Development] nARMstrong20:
Great stuff, this was my favorite MM kernel. Just a note though, I tried enabling MSM hotplug and got a reboot. Not an issue for me since I normally use Alucard or Thunderplug but here's a last kmesg if it helps.
[Moto G 2015 Original Android Development] ziyadft:
Can I request backlight dimmer feature please?

since the lowest brightness is still too bright I think :confused:
[Moto G 2015 Original Android Development] gene.pavlovsky:
I'm not using Viper4Android, don't see any reason to have SELinux set to permissive. The kernel that came with my ROM (Resurrection Remix) had SELinux set to enforcing and I didn't have any problems.

How do I keep using FireKernel but switch SELinux back to enforcing?

Tried `echo 1 >/sys/fs/selinux/enforce` or `setenforce 1` from a root shell and it's still permissive.
[Moto G 2015 Original Android Development] FireLord:
Custom kernels should be permissive mostly.. and do you really need Enforcing ? let me know why it is important? for n it will be permissive for sure
[Moto G 2015 Original Android Development] gene.pavlovsky:
Honestly, I'm an old-school Linux sys admin, I never used SELinux on my Linux systems, or researched much about should I start doing that. But I see the trend of Android development has moved from no SELinux to permissive SELinux and now to enforcing SELinux. Better security is always good, no? It can only have a downside if some feature stops working and can't be made to work anymore (you mentioned Viper4Android, which personally I've never tried).

Basically, I saw many threads "how to permanently set SELinux policy to permissive", with few people having a deep understanding what security implications that has (I don't have a deep understanding). Imagine somebody trying to set up some UNIX daemon/service on a UNIX server, messes up permissions on some config or data dir, and just decides to run the daemon as root, rather than figuring out and fixing the permissions. In Russia we have a proverb for that - "shooting sparrows with a cannon". So I'm just trying to get an understanding what is the pros and cons of permissive vs enforcing mode, and if there's any reason to stick with one or the other.
[Moto G 2015 Original Android Development] FireLord:
Yes enforcing makes device secure. But people around herr might be using those mod so for them permissive is required..

https://en.m.wikipedia.org/wiki/Security-Enhanced_Linux

https://source.android.com/security/selinux/

Btw I heard sys admin get hell headaches due to errors :v how you manage? Hahaha
[Moto G 2015 Original Android Development] gene.pavlovsky:
I understand the reason some people want permissive (although I'd urge them to investigate if their issues can be fixed with more "narrow-spectrum drugs"). I suppose you have disabled the ability to set SELinux to enforcing as part of kernel config, didn't you? Would it be difficult to provide ability to use either permissive or enforcing? People who need permissive would be able to use it, people who don't would keep enforcing. If that's a big pain to do, then I understand if you don't want to bother.

I don't work as sys admin for years, the only headache I sometimes get when I work with my dev servers, but mostly everything works nice and smooth. When I was just learning about Linux, some simple things (e.g. connect to WiFi) took days to figure out (didn't use any GUI tools, had to learn exactly how to do everything manually).
[Moto G 2015 Original Android Development] Tron_Legacy1680:
I saw that D2W is enabled in the kernel but how is it done? As the device has an IPS/LCD display and not an OLED. I read somewhere that for D2W the screen has to be active the whole time (please correct me if I'm wrong). Also if the screen is active the whole time with this kernel, does this not affect the battery life?

Thanks in advance!
[Moto G 2015 Original Android Development] EvilHowl:
Is losing network data normal? The only way to fix it is reinstalling the kernel or installing other and wiping cache.
[Moto G 2015 Original Android Development] dazeone:
This might help . I think the digitizer is on without the display being on. https://www.google.com/amp/s/amp.re...el/noob_question_how_does_double_tap_to_wake/
[Moto G 2015 Original Android Development] Acidfire.TM:
great job with the release of 6.2 for N

I'm sure it kicks just as much ass, as the version for M.:good:
[Moto G 2015 Original Android Development] luca_amateis:
Setting N

Hi, somebody can tell me which is the best set for N rom? I have problem with I/O perfornance, and low score. Thanks
[Moto G 2015 Original Android Development] Tron_Legacy1680:
So, how is d2w activated? Is it just activated after flashing or is there an option in settings or something?

Also how do I backup stock kernel? Is it the boot partition? To flash this kernel should I wipe anything or just flash?

Thanks!
[Moto G 2015 Original Android Development] acejavelin:
DT2W is activated in Kernel Adiutor. The boot image is your stock kernel, you can restore it if needed. Wipes are never required when flashing a kernel.
[Moto G 2015 Original Android Development] Tron_Legacy1680:
Thanks for clearing my questions!!!

So, I just backup boot and the kernel is backed up and if I want to restore I just restore boot?
[Moto G 2015 Original Android Development] acejavelin:
If you're stock, yes, although I would backup everything and copy it off the device for safe keeping... With a custom ROM it is best to just dirty flash the rom to remove the custom kernel.
[Moto G 2015 Original Android Development] Tron_Legacy1680:
Thanks a lot!
[Moto G 2015 Original Android Development] asti patel:
In aosp extended v1.1 with firekernel v7 there is no option for d2w in kernel auditor.
[Moto G 2015 Original Android Development] KrapK:
FireKernel doesn't have support for DT2W.
[Moto G 2015 Original Android Development] robot_head:
Double tap to wake will eat your battery up.
[Moto G 2015 Original Android Development] Vink67:
[MENTION=6257538]FireLord[/MENTION] love your kernel 7.0 for nougat, works really well. Thx.

Just one little thing missing ! Westwood algorithm congestion.

If you can add it like your kernel for MM it would be really nice.

Sent from my MotoG3 using my finger.
[Moto G 2015 Original Android Development] luca_amateis:
Please, help me which this troubleshooting!
[Moto G 2015 Original Android Development] nARMstrong20:
What's your settings right now? If I'm not mistaken lower values mean less performance in favor of latency as it reads in smaller blocks. Your memory card speeds may also be a factor.
[Moto G 2015 Original Android Development] Vink67:
My SD card died yesterday, stuck in read only. Try every method and software on earth ! Nothing work. Don't know if it's Nougat but that's sucks.

Maybe someone have an idea ?

Sent from my MotoG3 using my finger.
[Moto G 2015 Original Android Development] Gravemind2015:
I got that too, I tried hard but couldn't mount it R/W. I had tried to format using diskpart and (g)parted, tried rebuilding partition table but no progress. Surface test concluded that nearly all of the blocks were bad. Mine died after TWRP backup gave me an error while backing up /data (it was code 256 or something similar). Maybe a warranty replacement is your best chance right now, backup whatever you can as the card is still showing up.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] luca_amateis:
I have SD extreme xc I 32 gb high performance!

I'm setting the scheduler I/O: ROW

Governor CPU: conservative

Using GZR Tesla 7.0 on moto g 2015
[Moto G 2015 Original Android Development] luca_amateis:
You can see the screenshots about the test on internal storage and external storage speed.