yashsingh1/xdaforums huggingface dataset:
[Moto E Original Android Development] vinay001:
[MENTION=5822936]corphish[/MENTION] tested Asphalt 8 v1.0 is smooth little lag than stock and loads faster too i think its okay, but v1.1 lagging alot stuttering and even Loading Times also high.....

---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------

Yes Aggressive Power Save Mode yes disabled and i set to performance still lagging...
[Moto E Original Android Development] piyushkashyap216:
Is screen freeze is fixed?
[Moto E Original Android Development] corphish:
Test build 3

Link : Removed as confirmed its not booting.

See if it fixes gaming performance or not.

Also check your CPU frequency table.

Thanks,
[Moto E Original Android Development] Adarsh1998:
Device won't boot, stuck at bootloader warning.
[Moto E Original Android Development] corphish:
Damn!

Thanks for trying anyway

You recovered your device?
[Moto E Original Android Development] Adarsh1998:
Yup, i hv backup recovery, and u replying from nokia 1100 really lol.
[Moto E Original Android Development] piyushkashyap216:
Is test 3 is stable
[Moto E Original Android Development] Adarsh1998:
Lol, u cant scroll to my Asnwer? I told it struck with Bootloader warning message
[Moto E Original Android Development] piyushkashyap216:
Sorry for my question and which kernel currently ur using
[Moto E Original Android Development] Adarsh1998:
Stock CM kernel
[Moto E Original Android Development] zeeshanhussain12:
Powersaving profile lagging

My phn battery was 30% before I changed profile to Powersaving nd then after changing my phone started lagging , after rebooting my battery dropped from 30 to 5?
[Moto E Original Android Development] Gilmar Mess:
Work On AOSP ?
[Moto E Original Android Development] zeeshanhussain12:
Yes
[Moto E Original Android Development] Gilmar Mess:
This Kernel have a Drain Battery ?

Or it is Stable ?
[Moto E Original Android Development] Simomaster1:
Recently i found a problem...on blisspop and now also on AOSP...when i try to open the camera i see a mex that tell me that impossible to connect to the camera:(
[Moto E Original Android Development] corphish:
Will be fixed in next update :)
[Moto E Original Android Development] piyushkashyap216:
[MENTION=5822936]corphish[/MENTION] pls fix also screen freeze issue
[Moto E Original Android Development] animesh1558:
Please fix it ASAP as without this kernel device is waste!! Also camera is equally important!!

Currently no camera on my device!!

Please release an update to fix this issue, afterwards u can take your time for adding any extra features!! :)
[Moto E Original Android Development] corphish:
Its really great to see many people are trying to help in getting the screen freeze issue fixed in anyway they can. :good:

Anyways, I need some confirmations, it will require PC to interact when screen is freezed, in PC, adb must be configured properly.

As always, keep USB Debugging on in your phone, and Root Access enabled to adb atleast.

So when, screen freezes, connect Phone to PC, open adb and type:

su
echo 0 > sys/android_touch/doubletap2wake

As soon as you execute the above commands, see if it fixes the freeze or not, you can use the touch.

If it is fixed, I may have a permanent solution for this in kernel level.
[Moto E Original Android Development] piyushkashyap216:
Which kernel should i test 1.6 or 1.6 test 2
[Moto E Original Android Development] corphish:
Any which feels suitable for you. Must have dt2w enabled in kernel though :p
[Moto E Original Android Development] piyushkashyap216:
using test 2
[Moto E Original Android Development] piyushkashyap216:
Your kernel app is getting uninstalled automatically in random time don't know why
[Moto E Original Android Development] piyushkashyap216:
i am testing 1.6 test 2 and found that whenever screen freezes and when i plug my device to pc to run that command that u given, screen freeze issue gets resolved only by connecting device to pc via data cable so unable to run your commands in adb.
[Moto E Original Android Development] corphish:
v1.7 will be released today.

CM is undergoing changes lately, and v1.7 will come up to date to it.

I am not getting much time to see to the bugs and add features. But to cope with latest ROMs, updated kernel is necessary.

And a good news for you guys, gaming issues has been fixed in v1.7

Night (GMT +5:30) [emoji14]
[Moto E Original Android Development] vinay001:
[MENTION=5822936]corphish[/MENTION] Thnks man waiting, in CM latest Nightly stock kernel also takes time to turn display on when call comes so much delay any idea??? Camera Fixed ???
[Moto E Original Android Development] ankshious:
Thanks [MENTION=5822936]corphish[/MENTION] for cosider our reviews.

One question, will it support fast charging?

Sent from JARVIS'S server
[Moto E Original Android Development] corphish:
Update v1.7

Changelog

-Updated base to latest CM sources.

-Introducing Zapdos Charger Control, a mechanism to control charging current. (Min: 500 mA, Max: 2000mA)

-Implemented sysfs for pocket mode.

-Enabled F2FS.

-Fixed up gaming performance issues.

It is highly recommended to have a backup kernel, just in case.

Honorable Mentions

This guys had contributed in anyway they could, lately, like by testing, suggestions, valuable feedback etc etc.

Adarsh1998

dhruvmu

piyushkashyap216

And some others
[Moto E Original Android Development] Adarsh1998:
F2fs on cache only?
[Moto E Original Android Development] corphish:
That's ROM specific I guess.

Support for various file systems are defined in fstab in device tree.

What could be done in kernel is done :D
[Moto E Original Android Development] Simomaster1:
If i wipe the system partition with f2fs filesystem...can i install cyanogenmod 12.1...because when i install it there is a mex that say: detecting filesystem EXT4 on....
[Moto E Original Android Development] Adarsh1998:
Sorry for spamming, where that Zapdos Charging Control?
[Moto E Original Android Development] piyushkashyap216:
first thanks for new release :)

is screen freeze issue is fixed in this release?
[Moto E Original Android Development] corphish:
Almost forgot about that.

You can find those files under sys/kernel/zapdos_charger_control

There will be 3 files

custom_current

enabled

version

To tweak them, open terminal and type:

su

echo 1 > sys/kernel/zapdos_charger_control/enabled

echo x > sys/kernel/zapdos_charger_control/custom_current

Where x is any value between 500 and 2000.

Gesture Control app will be updated for it too.
[Moto E Original Android Development] Adarsh1998:
Anybody having lag/slowdown in latest version?
[Moto E Original Android Development] robsonsilva:
Me. I tried to change some settings but has some slowness especially when using graphics. The battery is also discharging a little fast compared to the stock and other kernels.
[Moto E Original Android Development] ankshious:
Thanks [MENTION=5822936]corphish[/MENTION].you are awesome.

Please update gesture control app

Sent from JARVIS'S server

---------- Post added at 05:58 PM ---------- Previous post was at 05:09 PM ----------

Can someone explain me that how can I execute the fast charging command in terminal?

Will I have to enter at every end line?

Sent from JARVIS'S server
[Moto E Original Android Development] nilanko:
How are we pulling out 2000ma from a 550ma charger? Sorry I'm a dumbo in electronics. If we are charging it at 2000ma, aren't we degrading the battery life?

Sent from my BSNL landline
[Moto E Original Android Development] piyushkashyap216:
till now no lag no screen freeze issue

my rom is very sappy may be because of cm12.1 earlier i was on aicp i am not clear but

this kernel+cm12.1=smooth experience.
[Moto E Original Android Development] corphish:
Its off USB.
[Moto E Original Android Development] ankshious:
Hey [MENTION=5822936]corphish[/MENTION] screen freeze is happening in this version.

If I put my phone in pocket for a long time i.e 2 hours, then double tap doesn't work.

I have to wake it by button.

Please do something.

Thanks in advance.

Sent from JARVIS'S server
[Moto E Original Android Development] piyushkashyap216:
[MENTION=5822936]corphish[/MENTION] in this version 1.7 some time lock button stops responding but it seems screen freeze is fixed for me as of now
[Moto E Original Android Development] Adarsh1998:
[MENTION=5822936]corphish[/MENTION] please look on performance if possible, im having heavy lag compared to 1.6, games have no issues, but on daily usage there has lot of device slowdowns. I tried every profiles on Gesture Control, but still has slowdowns.
[Moto E Original Android Development] mepsilon2:
This may help

http://apcmag.com/android-usb-charging-secrets.htm/
[Moto E Original Android Development] Dan_Jacques:
WOOOOOW! F2FS!

So, can we format /data and /data/media in F2FS? This is the "plus" of the Moto G over others S400 devices. The IO performance gains are great.

I'll test today.

EDIT:

encryption unsuccessful error after format /data in F2FS. So, /data is unaccessible. Formatting /cache in F2FS gave me a bootloop.

Reading this, I think the roms has to modify the fstab file to permit the F2FS works. OR a flashable zip with the fstab adapted to support this.
[Moto E Original Android Development] ashwin007:
Once [MENTION=5822936]corphish[/MENTION] gets his trees up with f2fs commits,I'll get a cm build with f2fs working.??
[Moto E Original Android Development] Simomaster1:
How did you do this? If i go to TWRP>wipe>advance wipe>data>repair or change file system>change file system I see only this:
[Moto E Original Android Development] Dan_Jacques:
Yep. The last TWRP version dont support this. But I used this version: http://xdaforums.com/moto-e/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2971601

In 2.8.5.0 version all FS are avaliable.

I've tested to edit fstab.qcom with Moto G 'parts', adding F2FS access to /data, but it didnt work. Same error (encryption ununcessful), so /data continues inacessible.
[Moto E Original Android Development] corphish:
F2FS support must be mentioned within fstab for respective partitions.

I heard some BoardConfig.mk changes maybe required.
[Moto E Original Android Development] Phantom410:
Had to revert to 1.6 becuase on 1.7 system perfomance was really slow, and I couldnt play any of my songs, sometimes the player wouldnt detect them, and if I opened them with a file explorer nothing would play. Camera was working, unlike 1.6
[Moto E Original Android Development] piyushkashyap216:
reverting to stock kernel because of screen freeze if any fix comes out i will definitely test it.
[Moto E Original Android Development] AnkeshReborn:
Where can I get zapdos 1.6?
[Moto E Original Android Development] mepsilon2:
This was a thread created for f2fs by [MENTION=4188661]xperiafan13[/MENTION]

please refer here [MENTION=5426059]ashwin007[/MENTION] [MENTION=5822936]corphish[/MENTION]

http://xdaforums.com/moto-e/general/partitions-f2fs-support-moto-e-t3120159
[Moto E Original Android Development] @SidDev:
even small games like Clash of clan and Lasers are hanging a lot on this kernel,

and sometimes whole system hangs

everything else is awesome like the features

Great work going on with your kernel. [MENTION=5822936]corphish[/MENTION]
[Moto E Original Android Development] corphish:
Gaming performance should be fixed in 1.7. :eek:

And yeah I am already aware of lags in 1.7 in system, working on it.
[Moto E Original Android Development] @SidDev:
I think gaming performance is having issues due to system lag, i think if system lags it will directly effect everything else.
[Moto E Original Android Development] Adarsh1998:
Yeah, im about to post same reply, no lags in 1.0, so here is the only difference is system lag, maybe system lag is making lag on Games too
[Moto E Original Android Development] animesh1558:
Does anybody have v1.6?? Pls send me the link to get it!!
[Moto E Original Android Development] piyushkashyap216:
[MENTION=5822936]corphish[/MENTION] screen takes time to wake up in incoming call some time screen dont wake i need to use power button to wake screen and screen freezes when any notification comes.

thanks in advance

:(
[Moto E Original Android Development] vinay001:
Bro have u checked it with stock cm kernel coz im having screen wakeup problems in stock too....
[Moto E Original Android Development] piyushkashyap216:
yeah i have checked stock too there is screen wake issue too but in zapdos some times screen dont wake until i manually wake it by power button and that screen freeze issue only happens when any notification arrives and i dont check that notification (for example if a mail comes and i check that mail after 5 min or later screen freeze happens).
[Moto E Original Android Development] vinay001:
Set mProximity to PROXIMITY_UNKNOWN on screen off

In the case where the screen was already off do to the proximity

sensor and the user presses the power button, we need to set

mProximity to PROXIMITY_UNKNOWN so that when the screen comes back

on and the proximity sensor is re-enabled it will be able to pick

up the change in proximity.

[MENTION=5658203]piyushkashyap216[/MENTION] new CM commit may be this will fix the issue not sure....
[Moto E Original Android Development] piyushkashyap216:
then pocket mode will also disabled i guess correct me if i am wrong
[Moto E Original Android Development] vinay001:
not sure this is CM commit , latest cm builds wont turn off display when in pocket means when some one calls if phone is in pocket screen should not turn on but its happening.....
[Moto E Original Android Development] piyushkashyap216:
which latest cm can u specify buold no. currently i am on 25 aug build
[Moto E Original Android Development] vinay001:
no tat commit is not merged still.... Im on 26th build have problems.....
[Moto E Original Android Development] piyushkashyap216:
last thing how u set proximity to unknown?
[Moto E Original Android Development] vinay001:
tats commit bro i dont knw..... wait for the fix
[Moto E Original Android Development] Simomaster1:
@corphish I have found a bug with your kernel used on @ashwin007's today built of cyanogenmod with f2fs support. In this built wifi don't turn on
[Moto E Original Android Development] Adarsh1998:
Ashwin told in that build, kernel was updated, maybe that's the cause
[Moto E Original Android Development] vinay001:
Mostly mac id not available in wifi settings tats why wifi doesnt turn on, dirty flash or full wipe????
[Moto E Original Android Development] Simomaster1:
Full wipe
[Moto E Original Android Development] @SidDev:
yes it is due to the updated kernel
[Moto E Original Android Development] ashwin007:
My kernel runs CAF WiFi firmware.So that's the problem
[Moto E Original Android Development] piyushkashyap216:
hey buddy in todays cm update mProximity to PROXIMITY_UNKNOWN has been done will this fix call delay

see screenshot
[Moto E Original Android Development] vinay001:
tats not todays changelog its 29th build and i tried, unfortunately it didnt fix call delay.....
[Moto E Original Android Development] piyushkashyap216:
opps i forgot my country is 10 hours behind from india that's why this build is today's build for me :p
[Moto E Original Android Development] lexer98:
AICP + this kernel is working really good , for the first time i'm getting the same battery life than 5.0.2 soak test .... <0.6/h in Deep sleep.

Thanks for your work mate
[Moto E Original Android Development] NasiJagung:
not working on SOKP
[Moto E Original Android Development] iwana2109:
getting "can't connect to camera"

ROM Slimsaber with latest update
[Moto E Original Android Development] corphish:
App has been updated.

http://xdaforums.com/showpost.php?p=62627262&postcount=43

Charging Control now possible via app.

Note that the app uses generic limits of 100-1000mA, but max limit for condor is 2000mA.

Well its pretty high and it will be reduced in 1.8 to 1000mA.

So safe but faster charging.

And yeah, next up on plate is v1.8 of this kernel.
[Moto E Original Android Development] iTudorS:
Wifi not working on CM12.1 F2FS unofficial build.
[Moto E Original Android Development] @SidDev:
Thanks for taking my suggestion buddy.
[Moto E Original Android Development] corphish:
Poll

Do you want two versions of kernel, viz. with dt2w and without dt2w? Or will stick to one version with dt2w, because phone is pretty stable when used with dt2w off?
[Moto E Original Android Development] Adarsh1998:
Yeah make it one, we can easily disable dt2w in kernel apps
[Moto E Original Android Development] vinay001:
yes of course so no issues...
[Moto E Original Android Development] corphish:
Update 1.8

Changelog

-Reduced max and default current in charger control.

-Added and reverted some stuff as an attempt to bring back lagless life.

Note that this version uses single version of kernel.
[Moto E Original Android Development] @SidDev:
2 versions

In my opinion make 2 versions

We have Moto Doze feature so i dont use d2w and d2w causes lots of problem, like screen freeze

So 2 versions would be good [MENTION=5822936]corphish[/MENTION]
[Moto E Original Android Development] Adarsh1998:
Lagginess still here, not solved....
[Moto E Original Android Development] corphish:
o.O

Well that's really strange.

In next version I guess.
[Moto E Original Android Development] ankshious:
Downloading.....

Will review it.
[Moto E Original Android Development] Simomaster1:
@corphish have you updated the wifi driver? To solve wifi issue on lastest cyanogenmod
[Moto E Original Android Development] Adarsh1998:
Wifi was working
[Moto E Original Android Development] Simomaster1:
In 1.7 wifi wasn't working...i'm sure others users reported this
[Moto E Original Android Development] Adarsh1998:
You talking about non dt2w version then yes, if u talking about test build by ashwin then thats becouse ashwin's test build had wifi drivers from CAF,
[Moto E Original Android Development] Simomaster1:
Ok...but...wifi drivers aren't updated also on official cyanogenmod?
[Moto E Original Android Development] Adarsh1998:
No there's no update thing, ashwin used different drivers from CAF branch that's it.
[Moto E Original Android Development] Simomaster1:
Oh sorry...i was thinking something wrong:rolleyes:
[Moto E Original Android Development] Phantom410:
Just installed 1.8, at first it was really laggy. When I opened the cpu settings, max frequency was set to 300MHz by default, changing that to the regular value solved all lag issues.

Could someone please explain the charger control, I know that it makes charging faster, but does it have any bad side effect for the phone?
[Moto E Original Android Development] piyushkashyap216:
[MENTION=5822936]corphish[/MENTION] new kernel is smooth thanks for update and i have one suggestion/request for app, can u pls add a tasker function like when screen is off governor etc changes according to our preference by this way we can save lots of battery.

pls add this
[Moto E Original Android Development] Adarsh1998:
[MENTION=6542271]Phantom410[/MENTION] It only boost when u connect to pc/laptop, it'll disable usb mass storage and only uses all power to charge the phone

---------- Post added at 11:40 AM ---------- Previous post was at 11:11 AM ----------

Yeah after changing max frequency it become smooth, but lagginess was still there, like open/closing apps, Animations at lag, you'll find when using
[Moto E Original Android Development] ankshious:
I downloaded the kernel and app last night and come to the conclusion :

1-charging phone rapidly like Galaxy S6 edge.?

2-no lag at all.?

3-baterry drainage is normal. ?

Thanks [MENTION=5822936]corphish[/MENTION] for the awesome kernel and app.

Sent from JARVIS'S SERVER
[Moto E Original Android Development] booo159159:
2 versions..

and guys pls give me information about f2fs,,

can I use f2fs with this kernel and latest cm12.1

and how to enable f2fs

will it work at all
[Moto E Original Android Development] kunalchitara:
The gaming performance is too poor. Currently using blisspop ROM and games were running smooth. But after flashing this kernel, they're like hell.. Played asphalt 8 in low graphics but my phone hanged too much. Is it with everyone or I have to change kernel parameters to play heavy games properly?

Rest everything is just fine.
[Moto E Original Android Development] piyushkashyap216:
in starting system seems to b snappy but now system is little bit laggy
[Moto E Original Android Development] corphish:
Due to failed experiments in UC, CPU clock reverts to minimum after boot. Set it to normal clock (1.2Ghz) and it should be fine.

This will be fixed asap.

Thanks to [MENTION=6542271]Phantom410[/MENTION] for pointing
[Moto E Original Android Development] piyushkashyap216:
already on 1.2 GHz

small frame drops are noticeable
[Moto E Original Android Development] Adarsh1998:
That's not only small noticeable thing, when you receive call or when Multitasking you'll get system lag and leads to systemUI restart also sometimes soft reboots.
[Moto E Original Android Development] Adarsh1998:
Go to cm12.1 thread and search f2fs, many guys are written how to there.
[Moto E Original Android Development] @SidDev:
i think the root cause of problem is d2w , s2w

We can just wave a hand to wake your device, so why the need of d2w, it uses more battery than the Doze feature + the screen freeze and all lagging problems.
[Moto E Original Android Development] Adarsh1998:
Nope, dt2w is not the root cause, all the other kernel out here has dt2w and dont lag, issue is something different.
[Moto E Original Android Development] @SidDev:
all kernel Threads have screen freeze issues, and this is one of the things which conflicts with system.

not a single kernel is there where people don't complain of screen freeze,

For me Moto Doze is safe and simple.
[Moto E Original Android Development] Adarsh1998:
I told about system lag, not screen freeze.
[Moto E Original Android Development] @SidDev:
Both conflict with each other,

But you tell me which is better Moto Doze (completely integrated in system) or D2W ?
[Moto E Original Android Development] Adarsh1998:
I dunno how you saying dt2w causes system lag (i agree with screen freeze),

for last question, if we need only moto doze, we can always stay in stock kernel (CM), why we need "custom" kernel is for performance tweaks, "extra" features like dt2w, s2w, OC, UC, fast charge, HPs etc that Stock kernel dont provide, so without having "extra features" we cant enjoy Custom kernel fully.

P. S, about that lag, I'm sure dev will fix it soon, he need some time that's it.
[Moto E Original Android Development] iwana2109:
nice update,its much much less lag, BUT....

i still got issue "Cant Connect to camera" after flashing v1.8,

i have not face this issue while using v1.6,
[Moto E Original Android Development] Adarsh1998:
Update your ROM
[Moto E Original Android Development] nisu4717:
We should implement touch proximity senser to wake instead d2w.
[Moto E Original Android Development] ankshious:
Whatever [MENTION=5022617]nisu4717[/MENTION] said I agree with that, dt2w consumes more power than proximity sensor, correct me if I wrong.

If it's possible then work on dt2ps instead of dt2w.

It would be great.

Thanks. :thumbup:

Sent from JARVIS'S SERVER
[Moto E Original Android Development] @SidDev:
i dont know what you people say

if you want something related to proximity sensor then why not use Moto Doze its present in Cm12.1

just wave hand to wake the device.
[Moto E Original Android Development] booo159159:
I am facing random reboots...

is anyone else here experiencing the same
[Moto E Original Android Development] corphish:
When in pocket, i.e when proximity is covered and screen is off, dt2w will not work, just like it should, promoting battery life (relatively).
[Moto E Original Android Development] vinay001:
Great Battery Back and performance using default settings, Awsome Kernel..
[Moto E Original Android Development] gtsfreak:
Will this work on stock 4.4.4 ???????? Just wondering

Kernel looks amazing :)
[Moto E Original Android Development] smith44:
No this kernel is for android 5.x.x i.e lolipop and rom based on android 5.x.x can use this kernel
[Moto E Original Android Development] shilanjan:
Does this kernel have any CPU hotplugs?? And another question, the alucard governor is present in this one??