yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] zwliew:
I don't recommend tuning as I have already tried my best to tweak for a better experience.

If you really have to, try using Device Control. However take note that some tunables aren't shown in that app.

Can anyone confirm this works without quirks? If yes, I will add this to OP. Thanks!
[Moto X Android Development] adm1jtg:
Been running since I downloaded it when you changed links for final time and no issues so far even using ultimate battery script
[Moto X Android Development] Makarovi:
Would this work on a 4.4 Moto X?
[Moto X Android Development] rebretz000:
Thanks man
[Moto X Android Development] Kittiesoncrack:
I have X1056 (Sprint), installed r1.9 and am getting a com.android.phone has stopped.

EDIT: if i take out the sim, the error goes away but i cant use my phone without a sim obviously. just a note
[Moto X Android Development] zwliew:
dmesg and logcat please. I can't do anything just by knowing you got an FC.

In terminal emulator,

$ su

$ dmesg > /sdcard/dmesg.txt

$ logcat > /sdcard/logcat.txt

Then attach them in the thread.
[Moto X Android Development] Kittiesoncrack:
got them

EDIT: flashed stock kernel, same problem. it wasnt happening before flashing r1.9. although my phone works without a sim card actually. i beleive its just a place holder so apps to give errors
[Moto X Android Development] ConstantHero:
Went to r1.9 all seems well as before. Everything working no force closing. Zippy so far. x1060
[Moto X Android Development] zwliew:
It doesn't seem like a problem caused by the kernel.
[Moto X Android Development] Kittiesoncrack:
yeah, it might of been something else. i did a cache and dalvik wipe and im flashed again. now its on "android is upgrading, optimazing app 177 of 221" are you suppose to be on Dalvik? because i was on ART
[Moto X Android Development] s5610:
Well, flashed again r6.12, and sweep2sleep works now flawlessly. Don't know what happened. Maybe I've mixed up with previous build... Not a surprise that It last on battery so long, undervolted in r6... ))

Sorry for misinformation, guys.
[Moto X Android Development] ss12108:
Yea I know I was asking what the default UV was on r5 but if r6.12 can't be undervolted anyway it's irrelevant for why I asked lol.
[Moto X Android Development] Travisdroidx2:
Okay so this morning reboot led to a freeze during start up. However, I thought it was rebooting before. But actually the screen freezes and then just shuts off when screen times out. I did not touch power button and it stayed off. Once I hold power button it starts up again with no issues. This is the only issue I am getting. Once it boots and does not freeze all is well. Stock r6.12 test build xt1060. Still using it as my daily driver. Thanks for all your hard work!!
[Moto X Android Development] iSecks:
Any reason not to use v6 on CM12? It seems to be working okay for me.
[Moto X Android Development] zwliew:
R6 AOSP Lollipop version works fine for CM 12, just that the AOSP version has been discontinued. R6 is the last release for it.
[Moto X Android Development] rolberding:
Kit Kat AOSP roms

So from my knowledge the stock version of the kernel will not work with something like CM11, for example. Is there any chance we could get a KK AOSP version of this kernel? Currently I am using the stock X firmware with the 6.12 build of your kernel and I absolutely love it but I've been wanting to get away from stock for a little while now and I'm just curious if there's a possibility of that happening. Granted in due time KK roms will be outdated and more or less forgotten about, so I'd understand if the answer is no, but I have to ask.
[Moto X Android Development] zwliew:
No, sorry. I don't want to mess with two different versions of the kernel when I can't test them properly. I'm staying on purely stock.
[Moto X Android Development] IonAphis-:
Flashing Kernel

Sorry I've been flashing ROMs and stuff for the better part of 6 years but I've never ever flashed a Kernel before (F**k me right?)

But I wanted to try this kernel, and there aren't many instructions on the front page.

I gather flashing the kernel is the same as flashing other zips: wipe dalvik / wipe cache / flash zip.

But there's a warning on the front page saying:

Notice for stock OTAs:

Restore stock /system/lib/modules folder

Rename /system/lib/hw/power.msm8960.so.bak to /system/lib/hw/power.msm8960.so

And now I'm lost as to why I need to do this or at what point in the flashing process.

I'm running stock Android 4.4.4, with TWRP and rooted.

Another question: To restore a kernel (in case I have problems) I just do a selective nandroid restore of the boot.img right?

Thanks!
[Moto X Android Development] zwliew:
The modules are replaced when flashing my kernel to prevent incompatibilities. I renamed the PowerHAL as I have in-kernel replacements for them. These are only useful is you plan to be able to update through the OTAs as system modifications will halt the update process.
[Moto X Android Development] IonAphis-:
Cool, so if I'm just planing to do nandroid restores, I just flash away right?

Thanks for the fast response
[Moto X Android Development] zwliew:
Yes.
[Moto X Android Development] gambiarraweb1:
Working on CM12 5.0.1?
[Moto X Android Development] tmimaesk:
Nope, he said this serveral times already that he dropped support for any aosp roms.

You can try R6 AOSP but it may work, it may not, back up and try it out for yourself.

He will only support Moto X Stock Roms which is 4.4.4.
[Moto X Android Development] gambiarraweb1:
Ohhh... Ok thks :))
[Moto X Android Development] rolberding:
Not a problem! I decided I'd rather stick to stock anyway, that's basically what happens every single time I think of going to CM or anything else. ?
[Moto X Android Development] Schaweet:
To take an OTA can I just flash system.img from the stock rom (I know I need to do recovery and kernel as well) to override your changes?

Sent from my Dev Edition Moto X

---------- Post added at 10:33 PM ---------- Previous post was at 10:31 PM ----------

Sent from my Dev Edition Moto X
[Moto X Android Development] zwliew:
Yes. You basically just have to revert your system to stock.
[Moto X Android Development] Schaweet:
Cool thanks!

Also thanks for this kernel. Standby times are insane! Love it.

Sent from my Dev Edition Moto X
[Moto X Android Development] sruel3216:
hello this is my first kernel flash since galaxy nexus days. what is the proper way to flash kernels these days in twrp? as in what do i wipe? ex. cache, dalvik, etc?

Thanks
[Moto X Android Development] zwliew:
1. Download latest version from OP.

2. Boot into TWRP.

3. Flash zip file.

4. Reboot.

5. ???

6. Profit.

I'll post these instructions in OP soon.
[Moto X Android Development] sruel3216:
ok so people dont wipe the cache anymore before flashing the zip? that was the "thing" back during gnex flashing
[Moto X Android Development] zwliew:
Wiping cache is not necessary 99% of the time unless you encounter incompatibilities like FCs.
[Moto X Android Development] rolberding:
Not a problem. I changed my mind about trying out AOSP again as I usually do on my X. :p

Instead, I took a stock flashable build from my carrier and I debloated it, flashed it, and flashed r6.12 and it's running nice and smoooooooth. :victory:

Great work! :good:
[Moto X Android Development] kicker22004:
Any more progress on the Republic Wireless version?
[Moto X Android Development] zwliew:
r7

Pushed r7 to AFH.

Download:

https://www.androidfilehost.com/?fid=95832962473399001

Changelog:

1. Actually fixed Sprint compatibility

2. SWEEP2SLEEP FTW MLG PRO 420 BLAZE IT

3. Undervolted by 50mV instead of 75mV for better stability

4. Interactive governor is more conservative and also uses frequencies with lower voltages

5. Added 189 MHz frequency step (you need to set it as minimum yourself, default is still 384 MHz)

I recommend to use the 189 MHz frequency step, just that I haven't found a way to set it as default yet. It will give you better battery savings on idle use cases like MP3 decoding, as it uses a lower L2 b/w with lower voltages.

Enjoy! :fingers-crossed:
[Moto X Android Development] adm1jtg:
Loading now... As always will report back with results
[Moto X Android Development] Schaweet:
Fast charge is enabled by default, correct? How can we tell if it's working? It doesn't seem to be for me. What voltage am I looking for while charging?

Sent from my Dev Edition Moto X
[Moto X Android Development] zwliew:
Fast charge is disabled by default now. You need to enable it at /sys/kernel/force_fast_charge/fast_charge_level.

Fast charge works differently from previous implementations on other kernels. It doesn't force input current to AC, instead it extends the limitation of the input current to whatever level you set it to. The input current still depends on how much your USB port can output.
[Moto X Android Development] adm1jtg:
Looks like the folder is just called fast_charge. You then edit the fast_charge_level file. The value in it is currently zero. There is another file in the same folder available_charge_levels that will list all the valid numbers to use. Use one of those numbers in the fast_charge_level file. I BELIEVE a usb 2.0 port can usually put out a max of 500ma and a usb 3.0 port goes to like 900ma max

Update: Just tried setting it to 900. Saved file and rebooted. Files value is reset to 0 after a reboot
[Moto X Android Development] Schaweet:
Ok, so sorry to ask such a most likely easy question. I go to that file in root Explorer and it won't let me save a changed value? Do I need to edit it in terminal or adb or something? I see you have the echo command in the second post, but I'm not familiar with how to use that. Thanks in advance for helping!

Sent from my Dev Edition Moto X
[Moto X Android Development] zwliew:
Values are all reset after boot. You need to use a script or something else to change it every reboot. Instead, I'll change the default value to AC (1100mA) in the next release.

Try using ES File Explorer instead.
[Moto X Android Development] Schaweet:
Ok, so I was doing it correctly it just won't stick Root Explorer. I tried ES also and it actually sticks and survives a save, but still not a reboot.

No worries, just wanted to make sure I wasn't doing something wrong. Thanks for being so responsive and thanks for the kernel.

Sent from my Dev Edition Moto X
[Moto X Android Development] crisout:
Has been a couple of weeks since I stopped reading this thread, I just want to ask why did you change of idea, you stop to develop for stock and now it's on the contrary, what happened? (By the way I'm happy for it, I use stock :P )

PD: Great job man, Thanks again!
[Moto X Android Development] zwliew:
Because I realised that stock > AOSP
[Moto X Android Development] Travisdroidx2:
R7 is running great here so far. No more freeze up after a reboot. I changed the min to the 189 like suggested. Great work and thanks!!!

Eclipse

4.4.2

XT1060 dev edition

p.s I never did get the fast charge to stick even with ES file explorer. Not a big deal for me though since I usually have a factory charger close by.
[Moto X Android Development] xQuestx:
Been using r7 for 24 hours great so far. thanks.
[Moto X Android Development] Travisdroidx2:
All thanks goes to the Dev [MENTION=5604178]zwliew[/MENTION] :)
[Moto X Android Development] MCJD:
I only have Wi-Fi when i am with the screen on beacause when i was with the screen off the Wi-FI is off. Sorry for my bad english. This is a Bug?
[Moto X Android Development] zwliew:
Sorry can you further explain what you mean/are experiencing?
[Moto X Android Development] MCJD:
It Solved. This had a conflict with the App Cenesys. Uninstalling this it was resolved but can you explain me Why this happened?
[Moto X Android Development] zwliew:
I have no idea what happened or what Cenesys is. If anything, Cenesys is probably the one that caused whatever you were experiencing.
[Moto X Android Development] mac1996:
Hey I love your rom.. Smooth.. Faster and great battery life... I want to know can you use sweep2sleep feature from status bar or any other place.. As the feature is built into the kernel.. I just want to know..
[Moto X Android Development] zwliew:
I hardcoded it to detect the nav bar only since it is the easiest place to reach. Why do you want it to the the status bar?
[Moto X Android Development] mac1996:
Just wanted to know if we can use sweep2sleep feature from alternative places.. If it was available I would like to try from status bar.. As I use it to control brightness.. Anyway thanks for sharing with me
[Moto X Android Development] ConstantHero:
I use double tap to sleep on the status bar and sweep on nav, leaving the status bar open for brightness adjustment.
[Moto X Android Development] zwliew:
Updater functionality done

FTP hosting server? Check.

Updater functionality in app? Check.

Backwards-compatibility with KitKat? Check.

Stupidly, I didn't think of backwards-compatibility with KitKat as I was confident Motorola would've released Lollipop before I completed the updater functionality.

SIGH.

On the bright side, this gives me more time to create the app icon and graphic designs (which I suck at), to get ready for Play Store release. Some more kinks have to be ironed out but the basic functionality is working as it should.

Meanwhile, here are some screenshots:
[Moto X Android Development] ss12108:
Nice!

Just an FYI, not sure if others have the same problem, but UV -50 unfortunately seems to be too much for my device. Had some random reboots on r7, bumped up the voltage +25, and have been stable since. I guess -25 is the max for me.
[Moto X Android Development] crisout:
When are you going to release the app for this kernel? I'm waiting for it :D
[Moto X Android Development] adm1jtg:
been running r7 for a little while now and definitely seeing some lag. Changed lowest freq step back to 384 will see if that resolves the issue

Update:

The issue was how i was setting the min frequency. I used both Performance profile module in xposed and also tried using ultimate battery script. These were the causing the issue. just to be clear THE KERNEL WAS NOT THE ISSUE AT ALL.

I am now using faux clock to set the min frequency and everything so far is perfect
[Moto X Android Development] Travisdroidx2:
R7 is running great here with the 189 min setting. But I know all devices react different. I have had zero lag also.
[Moto X Android Development] zwliew:
That's possibly because I removed input boost. I've also noticed slight UI lag and in my personal builds I've re-added input boosting.

https://github.com/zwliew/ghost/commit/0db44b5057f5dde43af3a644fd6233def6c0fb3c
[Moto X Android Development] icerebro:
Hey it seems a nice Kernel, I wanna try it but I have a doubt, How can I return to stock Kernel without flashing the whole ROM 4.4.4 stock? Is there any File for Stock Kernel 4.4.4?

Thanks!
[Moto X Android Development] zwliew:
1. Back up your stock /system/lib/modules folder.

2. Back up your stock /dev/block/platform/msm_sdcc.1/by-name/boot file (boot.img).

When restoring to stock, restore these two files/folders. Also remember to rename /system/lib/hw/power.msm8960.so.bak to /system/lib/hw/power.msm8960.so
[Moto X Android Development] St.Noigel:
What about just backup stock boot on TWRP?
[Moto X Android Development] adm1jtg:
Wanted to make sure this got seen
[Moto X Android Development] Travisdroidx2:
Yup, it has been mentioned before in the thread not to use the ultimate battery script.
[Moto X Android Development] s5610:
MCJD zwliew Kernel is self-sufficient solution. I think, you should not use any of energy saving utilities or scripts or other "magic" apps, unless zwliew clearly recommends to use such. I asked about Infinite Battery and knew that I would have got worse battery life, not better.

zwliew

r7 - rock solid, just as r6.12 did. No reboots, no unexplained behaviour, battery friendly. Did have not a reason to tweak. Perfect, as for me )
[Moto X Android Development] kenosis:
May I know how to change Frequency to 189 MHz?
[Moto X Android Development] jakereeves31:
Use the force
[Moto X Android Development] kenosis:
Can I know the steps?
[Moto X Android Development] Travisdroidx2:
I use faux clock or trickster would probably work also.
[Moto X Android Development] interista4e:
ehi zwliew, maybe this can be an interesting function for your kernel :D

http://xdaforums.com/android/software-hacking/kernel-tap2unlock-tap2wake-feature-t2965344
[Moto X Android Development] mac1996:
That's a good idea.. In my opinion I thinks apps like gravity box have feature like double tap2sleep..whats new to see would be swipe2wake/double to wake..))
[Moto X Android Development] adm1jtg:
Personally I would rather see a very good battery friendly kernel with no frills. Each feature you ask to add in adds bloat and makes for a less efficient kernel. Thats my opinion anyway
[Moto X Android Development] Hasuris:
What for? We already have active display. Seems redundant and will drain the battery.
[Moto X Android Development] interista4e:
Well, maybe with the possibility to choose if activate or not... It's cool :D
[Moto X Android Development] Travisdroidx2:
My phone has been running great. Idled off the charger overnight and only dropped 3%. Your work is fantastic!
[Moto X Android Development] CrisLorD:
I think, that will make the kernel HEAVY...just think to make it battery friendly...that kind of things in my opinion just drain battery..and are useless...
[Moto X Android Development] DaRkRhiNe:
r7 is a bit laggy as compared to r6. Rest all is rock solid
[Moto X Android Development] zwliew:
r8

I've just pushed r8 to the servers Go get it!

And speaking of server, I've set up my own cloud file-sharing server right at http://128.199.239.125. Future downloads as well as this one will be hosted there. This is in preparation of the updater app I'm making.

Download:

http://128.199.239.125/ghost/zips/zwliew_Kernel-ghost-r8.zip

Changelog:

Additions

- Enabled conservative and powersave CPU governors

Improvements

- Boosting CPU frequency for 250ms on touch input to get rid of any UI microlags

- Max CPU frequency limited to 1 GHZ on suspend

- Using my custom thermal driver instead of the thermald binary

Note:

I still recommend 189 MHz but I forgot to set it as the default minimum.
[Moto X Android Development] s5610:
Have installed r8, and it works as described. On touch CPU1 quickly goes at 1GHz, and back, but CPU2 remains shut down. Even with active tossing around the screen. I think it's good - don't pay much attention to lags, until it's getting really jerking. Firstly, It's phone on limit energy accu, not gaming gadget )
[Moto X Android Development] kenosis:
Do you recommend 189MHz or is it already default value?

I just saw a note to set 189MHz. Thank you.
[Moto X Android Development] mac1996:
What apps do you guys use to change the values of cpu and other stuff
[Moto X Android Development] Travisdroidx2:
I use faux clock. Believe trickster works also.
[Moto X Android Development] CsR0501:
When i charge my phone off, reboots in the "charge mode" (i can't explain well... It's that screen of the battery charge level) over and over again... Is this an error or I do something wrong? :/

I use the r8 version...

Edit: Flash r7 (wiping cache/dalvik cache) and my phone can charge off without problems again...

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Android Development] zwliew:
I made some changes in the LPM mode that caused this. Will be fixed in r9
[Moto X Android Development] droids@m:
Bump ......!!!!!!no USB OTG on r8
[Moto X Android Development] Hasuris:
I second this. The stick isn't even powered up, it stays dead when connected.
[Moto X Android Development] Travisdroidx2:
Hopefully this gets fixed. I am enjoying this kernel too much to go back to stock.
[Moto X Android Development] zwliew:
Fixed.
[Moto X Android Development] Travisdroidx2:
You the man!
[Moto X Android Development] aneeshmbabu:
Will it work for droid maxx
[Moto X Android Development] zwliew:
I've received reports that it does.
[Moto X Android Development] aneeshmbabu:
Thanks
[Moto X Android Development] kicker22004:
Any update on republic wireless users?
[Moto X Android Development] kenosis:
Anyone using "powersave"? Phone becomes lag once I change to "powersave"
[Moto X Android Development] zwliew:
Not quite yet.

Power save governor shouldn't be used at all in userspace. It sets CPU frequency to minimum.
[Moto X Android Development] kenosis:
Thank you for quick reply. I change back to conservative which is smooth.
[Moto X Android Development] s5610:
Yeah, if it ain't broke, don't fix it )

I'm getting 2% battery drop overnight, and stock was 7-10% (WiFi is on both scenarios). Can you imagine this :cool:
[Moto X Android Development] kenosis:
IMO, it seems to have better battery life on r7.
[Moto X Android Development] Travisdroidx2:
I noticed the same.
[Moto X Android Development] kyzn:
Six hours on battery with light to moderate use, still at 90%. :D
[Moto X Android Development] adm1jtg:
I still get about 1% an hour drop in deep sleep. You doing anything special for that 2% overall drop
[Moto X Android Development] s5610:
I personally have Touchless Control disable. Other services left untouch, though I wanted to clean some but didn't had time to get into.
[Moto X Android Development] adm1jtg:
What about location and auto sync
[Moto X Android Development] Travisdroidx2:
I have location turned to device only. I get 2-3% drop overnight. I did not disable anything to achive this. The phone sleeps great.
[Moto X Android Development] s5610:
Nope. I check e-mail manually, no market updates, and also turn on GPS only by urge. Try to disable something, just to gain greater insight in. Wakelock Detector can help also.
[Moto X Android Development] kicker22004:
Thanks for at least looking at Republic wireless. If you make any headway on it I'm more then ready to test it privately. I've already made a backup and an easy stock kernel+module zip to restore. Anything else you need you just let me know
[Moto X Android Development] numanair:
I'm on Republic Wireless too. I guess I should have searched the thread before trying the kernel. I was having the wifi calls issue for both inbound and outbound calls. Also, trying to make a call with cellular off but wifi connected would give a message saying that airplane mode needed to be turned off. This was not an issue with the stock kernel. I too might be available for private testing if needed. Oh and I have only tried r7 so far.
[Moto X Android Development] droids@m:
I get at least 4 hours + sot on heavy use with which I am so satisfied and with fast charging too I have no regrets on battery anymore we love you zwliew....
[Moto X Android Development] crisout:
With the V8 for stock, got otg disabled, I was thinking all the day why would be the reason haha went back to v7
[Moto X Android Development] kenosis:
I thought otg is fixed
[Moto X Android Development] s5610:
Will appear in next version, most likely. I have OTG dead too.
[Moto X Android Development] dray_jr:
zwliew you have a great kernel here. i have enjoyed testing it for you over the last month. But i am currently running NeXus Experience ROM 1.0 - CM12 Based for alittle bit to full fill my 5.0 hole . keep up the great work on your kernel my friend and i will let you know when i come back to stock. But also let me know if you decide to switch back to working on your 5.0 kernel because i would be more then happy to help you test it out.

Thanks again for all your great work and keep it up my friend
[Moto X Android Development] adm1jtg:
Yeah I am sure v9 will have otg fixed
[Moto X Android Development] whisper13:
This is the 1st time i'll flash a kernel for a non nexus device

I was back reading then i saw something return to stock kernel? I already unlocked the bootloader but still in stock recovery and no root,meaning everything is in stock settings.

Long story short if i want to return to the stock kernel the Original moto x kernel

Can i just restore a backup to return to it or do i need to do something?

Just want to clarify things so that when the Android 5 OTA comes i wont have problems and just reflash the stock recovery