yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] DarkElf:
Guyss i am new to moto g 2015 forum...anypne please suggest me which kernel version i hould flash on my stock 5.1.1 asian retail rom?? Thanks
[Moto G 2015 Original Android Development] JackSparrow17:
Latest with stock mentioned....
[Moto G 2015 Original Android Development] jmadotme:
[MENTION=3873953]eng.stk[/MENTION] Very thanks for your job. I have your kernel since r92 release and it's awesome. Better performance and battery.
[Moto G 2015 Original Android Development] romy25:
Ohh that's quite interesting to know.

Reporting issues about your work is become reason for your annoyance.

Seems you want to hear only good feedback.
[Moto G 2015 Original Android Development] eng.stk:
Let's see if you understand plain english:

I made this project to improve my phone and I decided to share it. I'm not here to make your phone perform like a 600 euros phone.

Bugs about my work? Sure, provide logs or issues than can be replicated. We had a couple.

But if it's a limitation of the HW and of a GIANT hack, I can't do miracles.

Sorry, I don't do HW and I don't do client support. Go cry to Motorola.

My code is public, if you're a genius and you can fix the touchscreen hack, feel free to gitpull fixes. But we all know the answer to that.

Don't like, don't use it.

I don't even have the device anymore and I continue to push builds.

That kind of disrespect towards people like me that burn hours for free to make devices better is not welcome here.

Take your rudeness and demanding tone elsewhere.
[Moto G 2015 Original Android Development] romy25:
Thanks for the plain English.

It was simply an observation after few days of use of this kernel. In plain English obviously.

Miracle... Rudeness.. Demanding.. Disrespect.. See where are you heading dude.

Anyway. Thanks for sharing your work.
[Moto G 2015 Original Android Development] kaustubh_lipare:
SuperSU not working ?
[Moto G 2015 Original Android Development] eng.stk:
I don't know if CM13 is ready for SuperSU systemless, v2.56 worked fine on on the CAF 6.0 build.

You can try v2.52.

edit: btw I made a mistake in the order:

it's Format /system and reflash the CM 13 ROM+Gapps 6.0+blu_spark_r92-CM13_osprey_1562e7b.zip+SuperSU v2.56 in this exact order

SuperSU is last, system must be formated prior to flash annything to use systemless.
[Moto G 2015 Original Android Development] ==vj==:
Ummm in my case, the last flash of SuperSU 2.56 also states that there are no binaries found and the inbuilt cm13 root stops working. Am on CM13 build of 03-Dec-2015. The rest was smoother on flashing kernel.
[Moto G 2015 Original Android Development] eng.stk:
Yeh Ithink the supersu install derps with cm superuser, maybe cf launches a fix for it.

In AOSP and the CAF builds it works fine, but in other devices it also derps on CM13.
[Moto G 2015 Original Android Development] FPThatea:
Many many Thanks to hardworking developer...
[Moto G 2015 Original Android Development] eng.stk:
blu_spark r92_ r2 CM13

I uploaded a r2 for r92 on CM13, to match changes needed by new SuperSU 2.60.

Maybe it fixes your supersu installs on CM13, try it.

Format /system and reflash the CM 13 ROM+Gapps 6.0+blu_spark_r92_r2-CM13_osprey_1562e7b.zip+SuperSU v2.60 in this exact order.

You can find new SuperSU 2.60 in http://xdaforums.com/showpost.php?p=64161125&postcount=3
[Moto G 2015 Original Android Development] kaustubh_lipare:
Finally supersu problem solved.... Everything is working..

Root.

Xposed..
[Moto G 2015 Original Android Development] HelpMeruth:
I'm going to test it now, will report back later!

Report:: Confirmd working! Everything works (for now)
[Moto G 2015 Original Android Development] ==vj==:
Now works perfectly on dual sim as well with proper root privileges. Thank you..! :)
[Moto G 2015 Original Android Development] eng.stk:
CF heard me talking yesterday and released the fix ;p

It should work good for now on, there's no need to kernel changes, supersu does it auto (like on nexus devices).
[Moto G 2015 Original Android Development] sudbht:
gravity box works or giving bootloop??
[Moto G 2015 Original Android Development] eng.stk:
Stay in topic, this is not a xposed thread.
[Moto G 2015 Original Android Development] Moto G User:
Uber Toolchain

[MENTION=3873953]eng.stk[/MENTION] chet kerner has released an updated uber toolchain ,which he claims, can improve battery life up to 25%.

https://plus.google.com/+ChetKener/posts/bPbuU5686DA

Can a toolchain increase battery life this much?
[Moto G 2015 Original Android Development] ravollmer:
Try it !
[Moto G 2015 Original Android Development] Moto G User:
I would but I have no clue how to compile kernels using different toolchains. I'm a windows user :)
[Moto G 2015 Original Android Development] marf28101995:
We already tried it and ...

Lets say linaro still the one ;)
[Moto G 2015 Original Android Development] eng.stk:
The end

Hi guys.

I don't have access to this device anymore, so this thread will not be updated.

Thanks!
[Moto G 2015 Original Android Development] Bangbang_cannon:
Every time I flashed the kernel my wifi turns off and it can't turn back on anymore, until I flash a new rom or go to a backup made earlier.
[Moto G 2015 Original Android Development] nelsonw:
Is stated on the OP. Some phones/ROMs won't work properly
[Moto G 2015 Original Android Development] christopherrrg:
Yes, we are still in Beta phase. :)
[Moto G 2015 Original Android Development] Gondya bhau:
hey guys..i had one question

if i am not mistaken, with lollipop, qualcomm released new drivers for the 410 CPU..by default all cores are set to run on 800Mhz at idle and also none of the cores sleep anymore when inactive...

this is compared to kitkat on which, the 410 was more battery friendly

does this kernel also use the same drivers ?
[Moto G 2015 Original Android Development] ela1103:
Hi [MENTION=3873953]eng.stk[/MENTION]

Your kernel Give Full Power To MOTO G3 .Its an really nice & stablity optmize

Feature Req for upcoming build

1.Cpu UC MHZ & OC 2.1 GHZ

2.Charger Control

3.Voltage Control

4.Sound Control

5.Colour Profile

Qualcomm 2.0 Quick Charge is possible to our Moto G3
[Moto G 2015 Original Android Development] eng.stk:
You have custom hotplug blu_plug in place that will be mor efficient that any qualcomm closed binaries.

1. 200 is low enough, you never see OC in my kernels

2. I tried to force ac faster charge in usb mode with no luck

3. I don't know any HMP voltage control implementation, we'll see in th future

4. faux sound is funky in lollipop because os dynamic gain and other stuff that mess with low level dricer levels. I removed it from all my kernels

5.you have kcal available to tweak color interface to your liking
[Moto G 2015 Original Android Development] Gondya bhau:
thanks for that...i dont have a motoG...i have a Xiaomi Redmi 2 which uses the same processor as yours...

the sources for our kernel arent released and our devs "kumajaya" and "zwliew" recently developed CM12.1 by creating our own kernel....they both however, use qualcomms drivers in their builds....

https://github.com/kumajaya/android_device_wingtech_wt88047/tree/cm-12.1

kumajaya is new to this hot plugging and i was wondering if you could share your Custom hotplug which I could forward to him...

could you post your github commits links here which relate to hotplugging please...that would be a great help :good:
[Moto G 2015 Original Android Development] eng.stk:
blu_spark r38

All right crew!

New build is up, enjoy :good:

edit: I uploaded r37 by mistake, dl r38 ;p
[Moto G 2015 Original Android Development] theShadow800:
Hey, the kernel works great but can you add DT2W to it? It makes using the phone really handy.

Thanks a lot
[Moto G 2015 Original Android Development] Harry551:
I want DT2W too.. +1 for your request
[Moto G 2015 Original Android Development] ==vj==:
Am just missing ZRAM support in the kernel. Would like to have it if convenient :)
[Moto G 2015 Original Android Development] eng.stk:
Moto just throws swap and zram to every device, even 3GB like the Nexus 6.

I prefer not to use it and have a nicely done LMK in place.

Well I don't know, seems like the panel doesn't support low power modes, so it would use some juice (like on the nexus 5).

We already have CMactions in most ROMs, ambient display works nicely on pick up and with prox sensor wich have both low power mode from stml0xx

I have some nice (and large) updates from upstream and CAF to several stuff and alrady implemented usb fast charge.

Next version will be awesome :)
[Moto G 2015 Original Android Development] Moto G User:
NEON Mode

Is neon mode enabled in this kernel?
[Moto G 2015 Original Android Development] eng.stk:
Yes neon extensions are enabled
[Moto G 2015 Original Android Development] theShadow800:
Wow! :D So will this be in the next update?
[Moto G 2015 Original Android Development] Mennooo:
Cant wait :)

Skickat från min MotoG3 via Tapatalk
[Moto G 2015 Original Android Development] eng.stk:
Still testing, we'll see...

Tried to hack around with LPM, but panel didn't respond too well.

Also, it needs to be on in order to dt2w work. And most ofnthe time is mor like triple tapbto wake than double tap.

But usb fast charge works nicely, that will be in for sure :)
[Moto G 2015 Original Android Development] ==vj==:
[MENTION=4525074]alin.p[/MENTION] had some great idea wrt dt2w feature on 1st gen. It had worked well without causing idle drain issues.

Hopefully he may respond to my tag and share his insights.
[Moto G 2015 Original Android Development] eng.stk:
Driver is similar and mine is newer.

There's no fix to th efact that the touch panel needs to be on line, he probably uses the prox sensor to disable the touch panel which I will not use because we already have ambient display and CMactions that use those hacks to work.

In case of wanting low power usage stick to that.
[Moto G 2015 Original Android Development] christopherrrg:
WiFi still burnt on me. :( I wanna use this so bad lol

Sent from my MotoG3
[Moto G 2015 Original Android Development] ==vj==:
OK..

I am willing to share one more strange thing I noticed about g3. It's that when we set min freq below 800MHz the cpu freq are found dancing towards higher freqs the most and also cpu temps varies high low abruptly. Besides they never stick idle at min freq upon idling.

But if I set min as 800MHz then cpu freq is observed idling for most times at this freq. And cpu temps are less varying. But the cpu load is always running between 10%-30% even after idling.

Another thing I noticed is wrt offlining, that the cpu temps are raising high often. But if I turn off offlining in your hotplug then cpu temps are gradually raising high low.

My concern now has come to CPU TEMPS on priority followed by BATTERY BACKUP. Phone goes really very warm in foreground usage. For some reason temps are going very high with offlining concept and not so high with all cores running parallely. Besides battery backup is also found poor with offling, which shouldn't had been logically. I am just feeling whether these 64 bit chipsets are really saving power on offlining or is it like the power across offlined cores continues to run. The older 32bit chipsets definitely did as I had better backup with offlining concept on those phones.

Would like to highlight I easily get 7:15-7:30hrs of screen on time on stock rom with stock kernel which runs all cores online and most used freqs are 800-998MHz. But the same on aosp/cm roms has been a dream for me :D Max achieved is 6:20hrs of screen on time under my usage pattern and most used freq is 998-1363MHz

Just shared my experience so that you can take a look in these areas and betterment the cons :) [MENTION=6485916]squid2[/MENTION] you too may take a look as i had similar experience with your kernel as well.

But the kernels by you'll are definitely better than the default kernel equipped within CM/AOSP roms. Because default kernel plainly runs 2 cpu states for the most (1.3Ghz and deep sleep). All other cpu freq are least touched or untouched. Here your Kernels are way better utilising other cpu freq and temps are cooler compared to default kernel equipped within ROMs. But not great as Motorola stock kernel yet.

Thanks in advance..!
[Moto G 2015 Original Android Development] HelpMeruth:
If you manage to put the doubletap2wake future on our moto g 2015,

You are my hero!
[Moto G 2015 Original Android Development] eng.stk:
You can test also with simulation to moto default behavior.

Just make your min freq 800 like stock and set min cores to 4 on the hotplug.
[Moto G 2015 Original Android Development] eng.stk:
Stock users rejoice :)

Unified build will work with any ROM

Well, can't find a nice way to build them together, a zip for each version it is.
[Moto G 2015 Original Android Development] grtsarav:
Does the WiFi work with the Indian models of this phone?....
[Moto G 2015 Original Android Development] ==vj==:
Yup I tested already and so I came up with that post after analysing the differences thouroughly for 4 days.

Besides I tested the backup pattern too, I just compared the backup and cpu temps with offlining and all_online in each charge cycle. Results were close to same but yet with all_online was few mins more and cpu temps were lower. Logically, the offlining backup must had been at least an 30mins more than all_online and cpu temps must had been lower than all_onlined cores. But results been reverse and made me think as described in earlier post.

As on yesterday, here are my CPU TEMPS and CPU FREQ stats record with following changes in kernel to simulate as Moto Stock. The idle drain control is fabulous.

Min CPU freq: 800MHz

IO scheduler : cfq with 128kb cache for both int-ext storages

CPU governor: interactive

All_Cores running online paralelly.

My CPU freq stats and temps in foreground usage in attachment. Now, most used freq is min 800 and 998. And rarely goes to 1.3GHz just as in Moto stock. But the backup is not yet fabulous as moto stock. Its close by though trailing by ~40mins backup difference.
[Moto G 2015 Original Android Development] HelpMeruth:
New Build is up! what is the changelog?

Edit: just flashed it: It has double tap to wake!!! thanks eng.stk! you are my hero
[Moto G 2015 Original Android Development] eng.stk:
blu_spark r47

All right crew!

New build is up, now with support for CM/AOSP and also stock ROM, choose the zip accordingly.

Lot's of goodies inside, enjoy.
[Moto G 2015 Original Android Development] christopherrrg:
Hehe flashed this before the log got posted. All working here, glad to be sparked blu again. ;)

Sent from my MotoG3
[Moto G 2015 Original Android Development] JackSparrow17:
For BlissPop rom zip should be flashed?
[Moto G 2015 Original Android Development] Mennooo:
With this kernel i have like 120mb free ram from start and with squids i have 300mb... CM12.1, dirty flashed before i flashed kernel.

Skickat från min MotoG3
[Moto G 2015 Original Android Development] nelsonw:
Everything seems to works except

SIM/RIL
[Moto G 2015 Original Android Development] eng.stk:
There's one zip for stock and one zip for all the others.

What's the doubt?

RAM not used is RAM wasted.

LMK and other memory tweaks are what matter for better user experience.

Works normal on EU osprey.
[Moto G 2015 Original Android Development] nelsonw:
I guess you tested on single Sim. Maybe on doubble Sim is different. Don't know.
[Moto G 2015 Original Android Development] eng.stk:
Yep mine is single SIM.

I think CM uses wrapper to start second RIL and I use the same. Do you have the file /system/etc/init.qcom.ril.sh?

Flash the attached zip, see if it works.
[Moto G 2015 Original Android Development] nelsonw:
I was running and now charging! will try in a few minutes. I'm back to stock and RIL is working. I don´t have that file you mention...

Edit: still don't works. File is there tho
[Moto G 2015 Original Android Development] JackSparrow17:
I flashed the kernel, but in blisspop wifi is not working, but in CM it's working....I have indian version....Anyway thanks for DT2W
[Moto G 2015 Original Android Development] umeshxda:
Quick charge doesn't affect hardware ?
[Moto G 2015 Original Android Development] ==vj==:
I am a dual sim user of Asian variant. There are no issues in RIL with latest kernel build. Everything works fine. I use PAC ROM odexed.

Try following:

1. Format system (without data wipe)

2. Wipe Dalvik cache and Cache

3. Flash your ROM zip

4. Flash the kernel zip.

I think this should solve the RIL issue you been facing :fingers-crossed:
[Moto G 2015 Original Android Development] JackSparrow17:
Fast charging and battery life got just amazing after your kernel.....Thanks Bro for really amazing work.....:D
[Moto G 2015 Original Android Development] eng.stk:
It just force the use of max mA permitted by the PMIC, doesn't change the hw limits.
[Moto G 2015 Original Android Development] abhijeetc9762:
Noob question...

I am on stock. Can i flash kernel directly from twrp.

How can i control settings of kernel.is there any app for that???
[Moto G 2015 Original Android Development] JackSparrow17:
Yes u can flash directly, and the app is 'Kernel Adiutor' from that u can control the kernel....Happy Flashing
[Moto G 2015 Original Android Development] nelsonw:
Thanks! I'm on stock and the latest OTA isn't available for re-flashing on FWs thread. I know that steps are on the OP. I'll flash CM and test. I'm guessing you aren't on stock?
[Moto G 2015 Original Android Development] eng.stk:
If you open terminal or make adb shell and type:

start ril-daemon2

what happens?

Make sure you have the entry persist.radio.multisim.config on your build.prop file.

It must have the value persist.radio.multisim.config=dsds or persist.radio.multisim.config=dsda

So put that build.prop entry, go to recovery flash kernel and flash fix zip, reboot

Other than that idk...
[Moto G 2015 Original Android Development] nelsonw:
In Stock I have dsds parameter
[Moto G 2015 Original Android Development] eng.stk:
No, try first persist.radio.multisim.config=dsds

if you type start ril-daemon2 on terminal emulator nothing happens?
[Moto G 2015 Original Android Development] nelsonw:
That parameter is already on build.prop. Will flash and try that command.

---------- Post added at 11:55 AM ---------- Previous post was at 11:43 AM ----------

Nothing happens. If I flash stock kernel back (restore TWRP boot partition) I have RIL back and lost wifi. Maybe it need stock RIL blobs?
[Moto G 2015 Original Android Development] eng.stk:
Well msim support is there, if it doesn't work nothing I can do.

blobs are the same provided from moto to all stuff out there, and this is not kernel related.

Even with stock if you have such issues like loosing wifi there's something wrong there.

As you can check msim works for other users, but with all model variations it can exist issues to some users.

Something that people will have to live with, I can only test and will support devices I own.
[Moto G 2015 Original Android Development] ==vj==:
Ohk for the stock. You didn't mention which ROM you faced ril issue in earlier post. I assumed you to be on cm based ROM.

For the stock, I am out of ideas. As I have moved to PAC ROM and continuing with it :)

Someone just clarify about stock.
[Moto G 2015 Original Android Development] nelsonw:
Thanks for the info about PAC Rom, will try it! Is good to know that works on others ROMS :o

---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------

No problem. Just wanted to help.
[Moto G 2015 Original Android Development] eng.stk:
Last test, try this.

Try on clean stock, don't forget to root and have busybox
[Moto G 2015 Original Android Development] nelsonw:
Thanks! I'll try later. I don't have my current build to re flash stock. And downgrade can go wrong. So, I prefer to flash CM based ROM :)

Thanks for your efforts.
[Moto G 2015 Original Android Development] abhijeetc9762:
Does anyone have stock kernel zip.?

I need if anything go wrong i will reflash stock.
[Moto G 2015 Original Android Development] abhijeetc9762:
I flashed the kernel but RIL not working.
[Moto G 2015 Original Android Development] eng.stk:
This kind of report is pointless.

What ROM? what model? msim? 1 sim on msim or both sims?

What zip you flashed, the one I posted nelsonw to try?
[Moto G 2015 Original Android Development] AmyClaraRose:
i thought id test your stock rom kernel test on my device but it doesnt detect my simcards im going back to custom roms anyway i have supersu and busybox installed as well
[Moto G 2015 Original Android Development] abhijeetc9762:
I am on stock rom. XT1550 indian 2gb model.

I flashed stock kernel but both sim cards are not detecting.

After that i flashed test 1 kernel you provided but no luck.
[Moto G 2015 Original Android Development] androidbaba:
Flashed on cr droid on Indian version

RIL working OK

WiFi disappeared which was working earlier..
[Moto G 2015 Original Android Development] HelpMeruth:
Little question, Is it normal that the D2TW only works good 10 sec's after turning off the device. after that it takes like 3/4 x2 trys before it works

is that normal or is it just buggy and not fully developed yet?

Xt1542 1GB

Edit: changing the governor to performance fixes the problem, Pleas improve the blu_active governor to fix this :)

thanks
[Moto G 2015 Original Android Development] eng.stk:
No, its pegged to the specs of the panel, when device goes into lower power stages.

Of course its buggy, were you especting Lg G4 touch panel quality?

If you have the phone at full throttle you won't notice that obviously ;p

You can make 4 cores online on screenoff or raise min freq, can improve that. But you will feel the bat drop.

And even then is more 3 taps to wake.

Be happy that at least you can use it.
[Moto G 2015 Original Android Development] eng.stk:
Powa!
[Moto G 2015 Original Android Development] JackSparrow17:
Will be eagerly waiting for this powerhouse kernel.....Thanks in advance[emoji6]
[Moto G 2015 Original Android Development] ==vj==:
Friend, great to see POWA. But please take care of Battery_backup and Thermal aspect under consideration. In current build, backup and performance looks fairly balanced :)
[Moto G 2015 Original Android Development] eng.stk:
Stock values are loaded by default, you only get to OC if you want ;)

cortex-a53 has this values available in other devices, the BW, voltages and so on are the same used on the stock max values, so nothing really changes that much on the thermal and energy side.

If you want to stay "safe", even keeping the gpu at 400 and the cpu at 1400 is normal qualcomm reference in our PVS binning.
[Moto G 2015 Original Android Development] HelpMeruth:
I will leave it on performance, im not that big power user :)

and im realy happy with that feature!
[Moto G 2015 Original Android Development] aSuperSaiyanG0D:
Anyone else having touch screen issues after flashing ?

Well to be more specific, I think it's something with kernel auditor, cuz once it says "applying changes on boot" is when it messes up my touch screen and I gotta hold the power for 10-15 seconds to reboot.

I'm on the moto g3 1 gb ram US variant
[Moto G 2015 Original Android Development] ==vj==:
No touchscreen issues faced here. The customized settings by me applies fine on boot without touch issues. Check back with your modded settings OR use the kernel as is without modding ;)
[Moto G 2015 Original Android Development] eng.stk:
blu_spark r55

All right crew!

New build is up, enjoy :)
[Moto G 2015 Original Android Development] abhijeetc9762:
Does this work on stock rom.? Because previous build is not detecting sim cards
[Moto G 2015 Original Android Development] eng.stk:
Works on stock ROM? yes

Works in every variant of device ou there? Probably not.

Read the thread. Backup and test it out.

This is a development thread, not a QA one.
[Moto G 2015 Original Android Development] aSuperSaiyanG0D:
Trying your second suggestion since all I had enabled was the dt2w, thanks btw ?

Oh and if I'm correct, to restore to stock kernal all I have to do is go into twrp, format boot then restore boot from my backup?

I'd rather just restore boot then the whole nandroid aha