yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] Hedied4me:
The latest versions I think only works with marshmallow. I could be wrong though that may have only been r14b.

sent from my CDMA Virgin Mobile Moto G3
[Moto G 2015 Original Android Development] jaswinprakash:
I have an issue with moto g turbo edition. Games are lagging when the device starts heating tried asphalt 8 and real racing 3. Without heat the games are perfect. Will this kernel fix this issue..???
[Moto G 2015 Original Android Development] Causical:
Hello, I'd be willing to donate for a 1.5-1.6 GHz over clock. This phone has better specs than the few lower end phones I've come from, all of which have gotten over clocks of at least 1.5-1.9 GHz. Any possibility?
[Moto G 2015 Original Android Development] TechnoAnder:
It depends of settings Kernel, you can try change the governor, IO/Shed, use more settings for the best experience
[Moto G 2015 Original Android Development] BreakCake:
What is the latest version that will work with CM12.1 on android 5.11? R15 does not say it is CM or Marshmallow only but when I flashed it I could not get my phone to boot.
[Moto G 2015 Original Android Development] boswelja:
Are said phones on the same chipset?
[Moto G 2015 Original Android Development] Moto G User:
This phone is capable of getting a 1.5ghz overclock. The Bluspark kernel (eol) managed to reach this overclock before. I would like if this overclock was implemented. Should give the phone a increase in performance.
[Moto G 2015 Original Android Development] boswelja:
Can you provide more details on blu spark kernel oc, like exact frequencies, I'm trying to add this to my dominionos project, running on a modified squid kernel
[Moto G 2015 Original Android Development] Moto G User:
Ive uploaded the zip file for the blu spark kernel. It only works on lollipop . I'm currently on marshmallow so can't test it ATM because of my unstable internet stopping me from downloading a lollipop ROM. Maybe you will have better luck:) Would be great if you successfully implement this OC. looking forward to it :)
[Moto G 2015 Original Android Development] FalKoopa:
Try r11e and see if it boots up.

[MENTION=6485916]squid2[/MENTION]

Can you please clarify.
[Moto G 2015 Original Android Development] Causical:
Nope, but yeah blu_sparks did succeed in a 1.6x over clock he moved on however and no longer supports the device, so we don't get it updated for cm13......However I'm wondering if it's going to be difficult to build a kernel that works well across all variants, I'm on Virgin Mobile and it seems that something is needed specifically in the boot img, along with the correct APN files in order to not break CDMA/LTE usability.
[Moto G 2015 Original Android Development] squid2:
If you benchmark the blu_spark kernel at 1.36 GHz and compare it to 1.6 GHz, you'll find that the CPU performance is exactly the same. It reports running at higher frequencies when you modify the appropriate DTBs, but the hardware ends up running at the same frequency.

I had spent many hours trying to overclock this CPU (the surnia variant) way back in March last year (see https://github.com/sultanqasim/android_kernel_surnia/commit/20b8ec614320961c18682fdca8aa2ca747e4ed69). It would report running at the overclocked frequency, but it would actually keep performing the same and and run at the frequency limited by the hardware. I had later looked at blu_spark's overclocking commit (back when it was available) and sure enough, it was equivalent to what I had done back in my old branch last March. When I benchmarked it with and without the overclock, sure enough, the overclock didn't actually work (even though it reported the higher speed).

You can try it yourself with something like Geekbench 3 on the blu_spark kernel. You should usually do a warmup run before counting the results. Run it once as a warmup run. Then run Geekbench without the CPU overclock (max speed at 1.36 GHz). Then run it with overclock. You will find that the result would be about the same in both runs. If the overclock actually worked, the overclocked score would be around 20% higher.
[Moto G 2015 Original Android Development] Hedied4me:
Thanks squid now we can put that to rest and the endless questions for OC.

sent from my CDMA Virgin Mobile Moto G3
[Moto G 2015 Original Android Development] Causical:
Oh wow, Craziness.... Well thanks for telling us. That's alright, you guys make some pretty badass kernels anyhow.
[Moto G 2015 Original Android Development] ==vj==:
Hmmm overclocking...! So the fact continues to Qualcomm. 3yrs ago we had conclusion of overclocking not actually being possible (appears to be overclocked but not really) for a Mediatek 6577 soc, as the PLL timer was unchangeabe. Wondered Qualcomm might be really overclockable but concludes with same.

Squid I doubt about offlining of cores too to be really being offline (no power consumption). I suspect Motorola have had hotplug implemented in moto g 1st gen but dropped in 3rd gen. And other latest smartphones too are suspected running with all cores online. Wondering whether the regulators are really powering down upon offlining core. Try to confirm on this too :)
[Moto G 2015 Original Android Development] squid2:
All four cores on MSM8916 are powered off a single regulator. On MSM8939, there is one regulator for the little cluster and one for the big clusters. When individual cores are offlined, they are gated but no regulator is shut off. An offline core should consume less power than an idle one (mainly due to periodic work scheduled for the core by the OS being stopped) but the savings would be fairly small. When a full cluster is shut off (as can be done on MSM8939), the regulator for the cluster is shut off.

Having one big regulator for a cluster isn't necessarily bad - it is usually more efficient than having four little regulators running simultaneously (in terms of leakage, switching losses etc). However, it does prevent running different cores at different frequencies (as voltage scaling is used along with frequency scaling).

The leakage of the one big regulator may be slightly greater than the leakage of one small regulator. But that's small potatoes - your battery's self discharge rate is significantly higher than the leakage current of the regulator. Though to be honest, the savings from hotplug are small too.

There are many layers of clock and power gating in these chips. The question lies in how much is stopped for an idle CPU, and offline CPU (in an online cluster), and for a full offline cluster. What would be interesting to see is comparing the idle current of all four cores online to the idle current of one core online (with three offline) to the current in deep sleep. This is not something that can be easily measured on our devices, though an engineering board for MSM8916 would shed some more light on this.
[Moto G 2015 Original Android Development] bubbyj:
I appreciate your view on this, and while no expert myself... I can still yet interpret results. Geekbench will be my standard.

Single Core performance: The top 26 scores on Geekbench3 = 1612mhz. And 41 of the top 50 are 1612mhz. Take a look at this attached graphic, for confirmation.

Ive ran, over and over 1612 vs 1365, and my results show a consistent 8-9% gain in performance. Mine, which is all I can speak for, is the current geekbench3 record holder for both single core and multi-core in regards to the motog3. Both were attained using blu-spark 1612mhz. 569 single core, and 1689 multi-core. Switching to your kernel, and using 1365mhz - with similiar settings otherwise = The scores drop to 530-535 and 1570-1580. A gain of about 120 points on the multicore side, and 39 on the single core side.

While the evidence above doesn't conclusively prove that 1612mhz runs better than 1365.... it certainly is difficult to defend the position based upon available evidence.

I would love to have the 1612mhz freq on marshmallow. And tons of others would too. It absolutely performs better on my end, and 41 out of 50 others. ;)
[Moto G 2015 Original Android Development] SirSoviet:
The increased rate of battery drain and power usage isn't worth it.
[Moto G 2015 Original Android Development] bubbyj:
I'm guessing that's your personal opinion. For me, its entirely worth it. But just to be clear, tweaking governors will give you whatever it is you are looking for. I will state emphatically that bluspark kernel is the best, smoothest, and fastest I've used on this device. Interestingly enough, thanks to its undervolting mixed with my parameters, im actually running faster and longer than stock.

Its absolutely worth it in my opinion. Personally I don't see the obsession with battery backup as worthy of my time. I'm lucky I guess.. I have a charger in the car, at work, at my laptop, and at home. If I have 100%, it takes all day to run it down. Never am I away from a charger for more than a few hours.. :) but in all seriousness, proper tuning of doze, wakelocks, governors, screen brightness, and turning off WiFi & data when possible, with greenify and a good services Disabler, will increase your battery life by 40-50%.

With my current setup, I use around 3.1-3.3% per 12 hours of standby. Stock, it will drain at about 7-8% per 12 hours. So before you jump to conclusions, try it.

I've already shown that it performs much better through hard numbers and graphs. And personal experience solidifies this...

But hey, what do I know?
[Moto G 2015 Original Android Development] Hedied4me:
Well said.

sent from my CDMA Virgin Mobile Moto G3
[Moto G 2015 Original Android Development] squid2:
Hmm, interesting. When I had tried it back 4 or 5 months ago, the average scores for three tries on my device appeared within 1% of each other for blu_spark capped at 1365 vs 1612 and mine had an average score around 2% higher. That matched my experience with surnia earlier that year. I'll check again when I get time. To avoid confounding factors (different ROM and Kernel), could you try benchmarking blu_spark 3 times and averaging at 1612 MHz, and then reducing the max frequency to 1365 on the same kernel and benchmarking again? I'll try that too when I get time after rolling back to CM12.1.
[Moto G 2015 Original Android Development] squid2:
Yikes... I decided to take another shot at overclocking. I didn't have my osprey or surnia at hand, so I tried on my lux. Not sure what I did, but I appear to have hard bricked my lux :crying: It goes into fastboot mode, but fails to boot anything now, overclocked or not. I suspect I may have misconfigured a regulator and made it fry something. This sucks :crying: :crying: :crying:

For the morbidly curious, here's the cursed branch that wrecked my lux: https://github.com/sultanqasim/android_kernel_motorola_msm8916/commits/hard_brick

EDIT: Phew, I brought it back to life after a hard reset via the PMIC. That was scary...
[Moto G 2015 Original Android Development] Causical:
Okay Soooo, here's my results

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

Blu_sparks 1.6xx #1

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

Blu_sparks 1.3xx #1

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

Blu_sparks 1.6xx #2

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

Blu_sparks 1.3xx #2

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

SquidLP build 1.3xx #1

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

SquidLP build 1.3xx #2

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

Pure_Stock 1.3xx #1

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

Pure_Stock 1.3xx #2
[Moto G 2015 Original Android Development] squid2:
Thanks for taking the time to test. The score on my kernel would probably improve if you turn off intelliplug (and then turn on all cores).

The blu_spark results for overclock (553/1657) and non-overclock (540/1621) are close but the 18% overclock did speed it up 2% it seems.

I will have to eat crow in that there is a (small) but measurable improvement that I probably missed when I tried last time as the speeds are quite close.

In other news, I managed to successfully overclock my lux. I can consistently beat the all time high for both single and multicore performance. I overclocked the 1651 MHz cluster to 1709 MHz and the 1113 MHz cluster to 1209 MHz. The average single core performance in Geekbench increased 4% (from 745 to 775) and average multicore also increased 4% (from 3060 to 3180). Given the modest overclock, the effect on lux is quite clear.

I will take another look at overclocking. The lux OC I'm very pleased with and will be keeping and making default (as it's quite mild but has a very measurable impact).

[MENTION=7177715]bubbyj[/MENTION] Thanks for prompting me to take a second look at this.
[Moto G 2015 Original Android Development] HTCDreamOn:
[MENTION=6485916]squid2[/MENTION] this seems odd bearing in mind the evidence from the code that this can't be done which you explained to us a few pages back.

Is it possible that overclocking doesn't actually physically overclock the cores, but because those hgher values are now hardcoded into the code the governor logic will take those into account and force the CPU up to 1.3GHz far more than usual? (In the case of osprey, because clearly your lux oc does work very well)
[Moto G 2015 Original Android Development] squid2:
I'll reserve my judgement till I try again and experiment with OC some more. My earlier statement was based purely on empirical experience. What could have happened is that there was actually a 1 or 2% speed up that was too small for me to notice last time. The Lux results clearly indicate that some form of overlock is possible. However, the frequencies that I overclocked my Lux to were already listed in the frequency tables and technically supported by on of the speed bins of MSM8939. All I did was enable additional frequencies already in the tables.

Now, for a larger overclock (1.36 to 1.61), there should be a bigger difference than 2%, so there does appear to be something amiss. Just a completely wild guess that's probably wrong could be that that certain overclocked frequencies are working but the 1.61 GHz step isn't. That could explain why there is a benefit but it is much smaller than expected.
[Moto G 2015 Original Android Development] Causical:
I know back on my previous phone we had over clocking capabilities, but the frequency tables weren't correct. It would actually be clocked at a step or two lower when physically reading a higher one.
[Moto G 2015 Original Android Development] Stefano 99:
Hi [MENTION=6485916]squid2[/MENTION],

Yesterday evening I tried to flash your kernel on CAF r86 but the phone didn't boot.

It booted with x-infinity r04, that's based on an older version of your kernel.

Stefa99
[Moto G 2015 Original Android Development] Causical:
It's possible that you downloaded the [merlin] variant instead of the [osprey].... I did that once.
[Moto G 2015 Original Android Development] thinkfreedom:
I am on stock marshmallow xt1550 indian edition and I faced the OS not booting after flashing the osprey zip.
[Moto G 2015 Original Android Development] Stefano 99:
Thank you for the suggestion but I'm sure I've downloaded the osprey version ;

It isn't corrupted because with es file explorer I can open the .zip

This kernel supports AOSP ROMs or only CyanogenMod?

Thanks,

Stefano 99
[Moto G 2015 Original Android Development] squid2:
It should work on all ROMs, but I haven't tested recent versions of the CAF ROM with this. I've only tested CM13 and the stock ROM. I'll look into it when I get time.
[Moto G 2015 Original Android Development] krsmit0:
i had some trouble with the newest build on the stock MM rom. i tried twice and restored to a backup each time. i ended up with boot loops both times.
[Moto G 2015 Original Android Development] Punraz_:
Which Version i need to flash on DominionOS (CM 13)? [MENTION=6485916]squid2[/MENTION]

Edit:I figured it out. I have flashed and it works perfectly, Great Work!

Sent from my Toilet using Moto G3.....?
[Moto G 2015 Original Android Development] truevision:
is there a possibility to have led notification for XT1541 ?
[Moto G 2015 Original Android Development] Hedied4me:
Moto G 2015 has no led notification

sent from my CDMA Virgin Mobile Moto G3
[Moto G 2015 Original Android Development] truevision:
thanx.

I have think to use the battery led, but if is not possible, no notification :)
[Moto G 2015 Original Android Development] sabarishsab:
How to choose proper kernel

How to find proper kernel for custom rom.Also how to get back to stock kernel,as im new to this forum.Please help me
[Moto G 2015 Original Android Development] sabarishsab:
On download section "Merlin" & "Osprey" R15 is there.Which one should I select for custom ROMs?.confused need help surely?.New to this
[Moto G 2015 Original Android Development] HTCDreamOn:
Merlin is for Moto G Turbo.

Osprey is normal Moto G.

R15 is for marshmallow, if you're on lollipop you must flash R11e ("_stock" if on stock, the other if CM).

By searching the thread you'd fine squid2's explanations of all this though, so please try searching first in future.
[Moto G 2015 Original Android Development] TVD1903:
If you want to go back to the kernel that came with your ROM, just reflash the ROM in your recovery. If you want to go back to the stock kernel on the stock ROM, reflash the appropriate boot.img for you device using fastboot.
[Moto G 2015 Original Android Development] spiked_mistborn:
The easiest way to go back to your stock current kernel is to make a backup of just the boot partition in TWRP before you flash the new kernel. Add "stock kernel" or something similar to the name of the backup so you will know what it is. Then if you want to go back, just restore the backup. You will probably need to wipe dalvik/cache after any kernel changes also.
[Moto G 2015 Original Android Development] hekomat:
If you do it like this, your wifi won't work. If you want everything working as it should it's best to make a full backup and restore that.
[Moto G 2015 Original Android Development] cesarXP:
Governor

Hey thanks alot, in my Moto G Turbo (latinamerica retail) Works perfect, but i have a issue the governor scaling doesn't work in Lionfish is still in interactive by default
[Moto G 2015 Original Android Development] TVD1903:
Does anyone (or [MENTION=6485916]squid2[/MENTION] himself) know the voltages that are used in this kernel, or where to find them? I would like to use these for a project of mine.
[Moto G 2015 Original Android Development] squid2:
The relevant configuration is here: https://github.com/sultanqasim/andr...arch/arm/boot/dts/qcom/msm8916-regulator.dtsi

I had adjusted the voltage floor and reference values. The actual voltages are calculated from the references, additional per frequency offsets, device-specific values blown into fuses by Qualcomm, and bounded by the floor and ceiling values.
[Moto G 2015 Original Android Development] OtavioMalzone:
How you folks are tweaking this magnific kernel?

Freqs, volts, virtual memory etc

share your dirty little secrets haha

maybe we can create a post just to discuss that(?)
[Moto G 2015 Original Android Development] charutl:
Does this KERNEL support usb fast charge? if this support usb fast charge means it is the best kernel ever
[Moto G 2015 Original Android Development] TVD1903:
Awesome, thanks! I honestly expected it to be a bit more simple, but I appreciate your quick reply.
[Moto G 2015 Original Android Development] thinkfreedom:
[MENTION=6485916]squid2[/MENTION] I am currently using X-Infinity R04 kernel in stock marshmallow rom with latest twrp 3.0.0 r2 and I am able to flash the latest squid r15 kernel but I am not able to boot the kernel successfully; it gets stuck while booting. Is there any special procedure to follow other than mentioned in the installation?
[Moto G 2015 Original Android Development] Gingernut78:
You need to restore stock kernel first then flash Squid's.
[Moto G 2015 Original Android Development] coolizard:
I'm using this kernel in stock MM with no problems at all.

But I don't know what to customize in kernel auditor to make it better.

Thank you very much!
[Moto G 2015 Original Android Development] Gravemind2015:
Well i only use the lionfish governor for battery improvements but you can control the min and max frequency of the processor for example.Just google the setting name which interests you :)

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] sabarishsab:
Which one are you using currently powersave?
[Moto G 2015 Original Android Development] Gravemind2015:
Yes i generally use powersave.I use cm 13 though so more options. [emoji39]

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] sabarishsab:
What about the performance?.Does it lag much?

If itz on powersave.
[Moto G 2015 Original Android Development] Stefano 99:
Hi,

There's the NTFS support to read HDDs, in this kernel?

Thanks,

Stefano 99

Inviato dal mio MotoG3 utilizzando Tapatalk
[Moto G 2015 Original Android Development] Gravemind2015:
Actually when sufficient battery is available,the phone does not lag *but* in case of a low battery,the status bar and nav bar turn orange and then the phone slows down.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] squid2:
Squid Kernel r15b

This is a maintenance release for the r15 series. I've merged in Linux 3.10.98, bringing with it associated security and stability fixes. I've also corrected an issue that prevented the ARMv8 crypto features I added in the last release from working properly. I have raised the priority of ARMv8 crypto in the kernel so that it is now the preferred crypto engine for use by the Marshmallow adopted storage feature. Regular full disk encryption will continue to use Qualcomm's (slower) hardware encryption engine as that is dictated by the configuration of the ROM.
[Moto G 2015 Original Android Development] Gingernut78:
Squid2,

Any kernel setting recomendations to use on stock Marshmallow?

Same as you made for Surnia?

Cheers for all the hard work btw
[Moto G 2015 Original Android Development] Gravemind2015:
Hi,

Does flashing this kernel changes selinux into permissive?I just noticed that it has been changed to permissive in settings.Can i just use SELinux_Mode_Changer app to revert it to Enforcing?Thank you :)

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] cesarXP:
Moto G Turbo (Merlin) Latin America Retail

This new versión of kernel r15b is not working, the cell phone doesnt start and is restarting in the unlocked bootloader alert (sorry for my bad english)
[Moto G 2015 Original Android Development] squid2:
Which ROM and version are you running? Did the previous r15 build work on your device?
[Moto G 2015 Original Android Development] squid2:
This kernel enforces SELinux by default. Something else must have made it permissive.
[Moto G 2015 Original Android Development] cesarXP:
Stock ROM and yes, i see in the TWRP console when installing i get a message that says its only compatible with the msm8916 processor (osprey) and not with the msm8939 (merlin)
[Moto G 2015 Original Android Development] squid2:
By stock ROM, do you mean Lollipop or Marshmallow? Recent kernel versions are Marshmallow only. If you are on a suitable Marshmallow build, did r15 work on your device? Is this something that r15b broke? The message saying "Squid Kernel for MSM8916" is just a generic message my installer script says on all devices.
[Moto G 2015 Original Android Development] cesarXP:
Marshmallow and yes r15 works very fine but with the r15b the cell phone always restart in the unlocked bootloader alert
[Moto G 2015 Original Android Development] squid2:
OK, thanks for the clarification. Could you do me a favour and test this new build:

http://www.mediafire.com/download/bfwdkqgstq1qiqs/squid_kernel_r15b-merlin-b2.zip
[Moto G 2015 Original Android Development] cesarXP:
Yes !!

---------- Post added at 04:29 AM ---------- Previous post was at 04:24 AM ----------

Is still not working i have the same error
[Moto G 2015 Original Android Development] squid2:
OK, I've uploaded five test builds contained within a tar gz archive: http://www.mediafire.com/download/ztqkn6vbp23rhyp/merlin_test.tar.gz

Try the five revisions in there and let me know which ones work and which ones don't.