yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] DroidFreak32:
It did seem to detect the network faster but the connection took a lot of time anyways.. the performance was too choppy without your kernel so I usually flash your kernel along with the rom and gapps

---------- Post added 10th September 2015 at 12:14 AM ---------- Previous post was 9th September 2015 at 11:57 PM ----------

But the stock 5.0.2 had no problems! Wifi worked flawlessly. Maybe using those exact drivers/firmware for the moto e's with older modems might solve the issue??:confused:

I tried flashing the stock 5.0.2 kernel but that caused bootloops. Had no choice but to use the r7f kernel
[E 2015 Original Android Development] atomomega:
For what is worth, I have absolutely no Wifi issues with r7f and stock 5.1

XT1527 here.
[E 2015 Original Android Development] yelupic:
Some impressions

I can confirm this on XT1524 with all combinations (see below). - In my opinion it has got to do with some parameters in the environment (router/its firmware/the near-by APs/strength of overlaying signals and the like).

Setups used for testing (the W-LAN with WPA/WPA2, with/without SIM - mobile data ON/OFF):

Stock 5.0.2 (retde)

Stock 5.1 (retus flashed over a clean retde, only boot and system, to keep the baseband etc.)

CM 12.1 by scritch007 (builds 39, 42, 43, 44) without squid kernel

CM 12.1 by scritch007 (builds 39, 42, 43, 44) with squid kernels r7f|e|d

In all cases the (very stable) connection took place within 5 secs. to 2 minutes, but more often under 30 secs.

(some combinations (older custom ROMs) needed a static IP, others worked also with DHCP)

I tested it in combination with/without automatic IP provisioning and also with/without fixed channels on the AP/router side, using the following (old stuff/firmware) devices (as the gateway):

AVM Fritzbox 7170 (router)

Intel(R) Centrino(R) Advanced-N 6200 AGN (laptop wifi card, as ICS access point , Linux and Windows)

Linksys WRT610N (router)

Sphairon <Unknown> (router)

The (overseeable) list of W-LANs (3 to 19) shows up relative quickly, the connects are a little slower with the custom ROMs/kernels.

Setting the Wi-Fi country to a specific value had no impact on the behaviour.

Nailing the channel and the (static) IP to defined values quickens the procedure.

(all setups were usually accompanied by flushing the DNS cache = reboot of phone and AP the first time)

On the stock ROM (XT1524, 5.0.2 retde) you can not use forced channels higher than 11 (= 12, 13, 14), but the custom ROM is able to handle those.

I didn't test it in the wild (foreign hotspots, open W-LAN etc.)
[E 2015 Original Android Development] hehk1234:
[MENTION=6485916]squid2[/MENTION] Sir,Your kernel is awesome with CM12.1, but have a little problem, I don't know exatcly if this problem is on Build CM12.1 or on your kernel, but on benchmark antutu (I know It's just a base), the score on 3D GPU makes on CM12.1 with your kernel only 3987 (sometimes go for 4048), on stock rom 5.1.1 with default kernel, makes 4484 (sometimes 4289). CPU test the score decrease too. (Quadrant and antutu the score decrease). I just give a report or feedback about your work, you make nice work here, thanks. :o:)
[E 2015 Original Android Development] squid2:
I've noticed the slightly lower benchmark scores myself too. It isn't something I did that's causing it, as if you compile the Motorola stock kernel without modifications, performance stays about the same as it is with my kernel. Oh well, if I figure out why it happens I'll do something about it, but benchmark scores don't matter too much for user experience.
[E 2015 Original Android Development] hehk1234:
I understand, but the performance on games as the same than stock rom ? I've tested some games here, and the performance for me is good, I don't see lags or problems, and battery life is nice. Thanks.
[E 2015 Original Android Development] squid2:
Yes, real world performance should be around the same as stock.
[E 2015 Original Android Development] Filz0r:
Hello I've been trying out the latest 7f kernel on CM and PAC and I also have the weak WiFi connection reported by some users and I've experienced a random reboot once in a while when my battery is bellow 50% and I've got a lot of app's open. I'm using the European xt1524 purchased in Portugal. Thanks a lot for your work so far!
[E 2015 Original Android Development] squid2:
The random reboot you experienced - was it a hard reboot or a soft reboot? The visible difference is that for a soft reboot, it jumps straight to the boot animation, while for a hard reboot (caused by kernel panic), it goes to the bootloader splash screen first (unlocked warning if you haven't patched logo.bin). I had experienced a soft reboot on osprey once that seemed to be caused by a rogue system process allocating a ton of memory at one point that caused the low memory killer to kick in and kill a bunch of important things, triggering the soft reboot.
[E 2015 Original Android Development] Filz0r:
Soft reboots always, one of the times after the reboot it even had the app I was using open, after the reboot.

I also have Grenify installed to keep apps like messenger and Facebook from waking up while in deep sleep
[E 2015 Original Android Development] squid2:
WiFi connection quality

While WiFi has been working fine for myself and many other users, some have been reporting poor signal strength and slow DHCP. For those who are having issues with WiFi, I want you to try flashing this zip. It will replace a binary containing WLAN radio configuration with one taken from the 5.1 stock ROM. WiFi works fine for me both with and without this patch, but maybe it will fix something for those of you who are having WiFi issues. Please let me know if it makes a difference.
[E 2015 Original Android Development] Hirsch2k:
Audio Offload issues

I'm experiencing issues with the audio playback. I'm on scritchs unofficial CM12.1. On XT1524.

Flashing your kernel (5f) breaks my audio playback. No audio output when playing mp3 or aac through standard cm player or shuttle player. Only workaround so far is disabling audio offload in build.prop completely.
[E 2015 Original Android Development] Filz0r:
Has I had to update my device to PAC latest build I gave it a shot and flashed this zip after reflashing the kernel after the update, and without moving my phone from the room I went from 2 bars on WiFi to 4... So far I can tell it has improved but not how much, in a day or two I'll give an more accurate review

Thanks a lot for your work again!
[E 2015 Original Android Development] DroidFreak32:
I too found the wifi strength being stronger after flashing the zip :D I hope the dhcp is also fixed. Right now i'm not able to notice it but in a few days I might be able to notice accurately. Thank you[emoji1]

-----XT1521-----
[E 2015 Original Android Development] dwane3:
Signal wifi stronger with this zip,thanks!
[E 2015 Original Android Development] yelupic:
Squid, your kernel r7f is pure joy to me (perfomance, smoothness, battery life), thank you :good:

_
[E 2015 Original Android Development] pamplinas:
Flashable zip

Really helped with the wifi. Before it would take 5+ minutes to see the router, now as soon as I click the wifi toggle it conects to my router in seconds. Thanks for the fix.
[E 2015 Original Android Development] Fedray:
Fix working! Thanks squid
[E 2015 Original Android Development] TechnoAnder:
Good work this Kernel! the best for surnia. :D
[E 2015 Original Android Development] jpmaster:
Xt1524 with cm12.1-44 and kernel r7f

So far I think that you hit Bullseye. Very rapid scan of available networks. Very rapid connection with static IP (2-3 seconds). With DHCP, 5-8 seconds to connect. Also signal quality is better.

If anything changes, I'll report it. Good work!
[E 2015 Original Android Development] yelupic:
XT1524 - scritch's ROM 2015-09-08, build 44 + squid's kernel r7f here (no GApps, some background messaging with Conversations).

Not having problems with WiFi, just out of curiosity, I flashed the suggested file and there are two observations I'd like to share:

The range/strength ratio (radius within you get a connection) is slightly higher

Using my private LAN-based Owncloud is much faster heading into a consecutive chain of sub directories (showing the contents almost without delays, which hasn't been the case before)

(Is it a coincidence? - Who knows ... I'll keep the changed file.)

Edit:

Forgot to tell, that I always have this situation on the device:

su

settings put global captive_portal_detection_enabled 0

settings put global captive_portal_server 127.0.0.1

pm disable com.android.captiveportallogin

reboot
[E 2015 Original Android Development] calculate:
Sorry for this question, but where could I find the settings for governor and scheduler?
[E 2015 Original Android Development] Android_noob17:
You need to download a kernel editor like kernel adiutor
[E 2015 Original Android Development] DroidFreak32:
With this the problem is definitely gone! Finally! Wi-Fi is no longer slow in connecting and it's strong too. Other Wi-Fi networks are detected much faster than before. No DHCP issues either. Thank you [MENTION=6485916]squid2[/MENTION] . [emoji16]
[E 2015 Original Android Development] atomomega:
Is there a way to uninstall the zip?
[E 2015 Original Android Development] starkly_raving:
If you mean the kernel...no. You can always restore your boot.img from your nandroid backup that I'm sure you made. [emoji12] [emoji106]
[E 2015 Original Android Development] atomomega:
Thanks. No, I mean the WiFi fix
[E 2015 Original Android Development] JobSup:
The fix just replaces /system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin

(dirty) flash your preferred rom or just replace the file with the version from the rom to revert the fix.
[E 2015 Original Android Development] Fedray:
Hey Squid, any way to have led notification in 5.0.2? Maybe you can make some kernel for 5.0.2 with some of the features that u added in last kernels build? Sorry if this is not the way to ask
[E 2015 Original Android Development] squid2:
Squid Kernel r8

Today's build is a fairly minor update. It merges in the latest upstream changes and has a few small tweaks here and there. The noteworthy new features are improved zRAM backported from Linux 4.1, and the adaptive low memory killer.

Apart from minor performance improvements, the new zRAM adds support for parallel compression/decompression and limiting the size of the compressed data. Neither of these options are enabled by default and must be configured yourself if you want to use them. I had a patch to support multistream (parallel) zRAM incorporated in to CyanogenMod, so you can enable it yourself by modifying the fstab in your ramdisk. This is not an easy modification for those without adequate experience, but you can look at my branch of the osprey CyanogenMod if you want to see how it's used. To be honest, the performance benefit of parallel zRAM mainly just helps zRAM benchmarks and doesn't visibly affect the user experience much for normal tasks. Still if you're curious, you can try it if you're interested.

The adaptive low memory killer is a slightly more useful feature. It preemptively kills tasks before minfree thresholds are met when thrashing is detected. This allows setting lower minfree values and reduces lag in low memory situations. This feature is not enabled by default, so you will need to enable it yourself if you are interested. You can look in my osprey or otus CyanogenMod device trees to see how it is activated.

I also incorporated a couple Motorola patches in the WiFi driver for background scanning of WiFi networks. Maybe it will fix something. I haven't ever paid attention to suspend mode network scanning or tested this patch, so I don't know if I fixed anything. For those who are bothered by the WiFi drivers in the previous kernels, let me know if the patched drivers are any better for you in this regard.

Finally, I included in the kernel zip the WLAN NV patch from last week that everyone has been saying good things about. You shouldn't need to flash the old patch zip after installing this kernel version.
[E 2015 Original Android Development] Fedray:
So, is it worth or not to use adaptive low memory killer? And I'm searching for how to enable it ^.^ good job Squid2.
[E 2015 Original Android Development] squid2:
To enable adaptive LMK, run the following commands as root:

echo 1 >/sys/module/lowmemorykiller/parameters/enable_adaptive_lmk
echo 49152 >/sys/module/lowmemorykiller/parameters/vmpressure_file_min

It has to be re-enabled every time you reboot the phone.

Will it make a noticeable difference? In low memory situations with a lot of apps open in the background, it may improve performance. In normal operation, it doesn't make much of a difference.
[E 2015 Original Android Development] Fedray:
I have this in Kernel Adiutor, do this work for something?
[E 2015 Original Android Development] thrasher194com:
Restored my nadroid back up of stock 5.1 and flashed r8 ... Great work...
[E 2015 Original Android Development] yelupic:
Or automate it with an init.d-script in /system/etc/init.d/

Example:

#!/system/bin/sh
#
# /system/etc/init.d/99lmk (root:root 0755 | -rwxr-xr-x)
#
# activate low memory killer (LMK) at start-up in squid kernel r8
#
echo 1 >/sys/module/lowmemorykiller/parameters/enable_adaptive_lmk
echo 49152 >/sys/module/lowmemorykiller/parameters/vmpressure_file_min
[E 2015 Original Android Development] dwane3:
Please upload script in zip for install.Thanks.
[E 2015 Original Android Development] yelupic:
This would be too simple, because you want to learn, right? ... (kidding)

First off, Kernel Adiutor is capable of doing this tweak without init.d-support and the example script for you (for the lazy ones here around).

For people not running Kernel Adiutor there are different methods:

If you are on stock ROM (not with CM ROM) there is no init.d for you (many stock ROMs don't have it, CM does).

With Kernel Adiutor (rooted stock ROM) you can mimic (emulate) the concept of init.d start scripts (there is a setting in the app for it).

For this you must create the folder init.d in /system/etc/ yourself and set permissions to owner/user=root (1000) group=root (1000) and the folder permissions to 0755 = -rwxr-xr-x

To create folders and files you could use a file explorer capable of root access like ES File Explorer (see settings in the app).

Then you will be able to place my example file /system/etc/init.d/99lmk (any start-up script) into this folder.

Then for

Stock ROM and/or CM custom ROM (the part above isn't needed for CM because it has already init.d support and the folder)

Create and name the file (99lmk) in the init.d folder and set its permissions to owner/user=root (1000) group=root(1000), file permissions to 0755 = -rwxr-xr-x

Copy&paste the example lines from my posting above into this new file (edit mode), save the file and you are all set.

(Don't create the file in a Windows Editor or at least take care to use UNIX line delimiters; use Notepad++ for instance to achieve this and create a final empty last line in the file before saving.)
[E 2015 Original Android Development] thrasher194com:
Stock rom, performance / bfq
[E 2015 Original Android Development] Android_noob17:
How do i remove the "android is starting" message when I reboot my phone? my phone boots up normally but is shows the message for about 10 sec before showing the lock screen. I'm using the latest version of pac man rom btw.

Edit: I fixed it myself by wiping the dalvik cache
[E 2015 Original Android Development] TechnoAnder:
Very well, your work with this Kernel is awesome, thanks Dev!
[E 2015 Original Android Development] hehk1234:
[MENTION=6485916]squid2[/MENTION] a little problem on install :(. When I select to flash on trwp, I got this error "error binary...." "your model is uds_surnia". My model is XT1514 dual sim.

---------- Post added at 11:05 PM ---------- Previous post was at 11:05 PM ----------

new kernel you released.
[E 2015 Original Android Development] yelupic:
If it was squid's intention, don't flash the r8 kernel on your umts double sim (uds). There is a reason for it. Maybe squid will comment this release?

updater-script in r7f

ui_print("Squid Kernel for Moto E LTE (surnia)");

assert(
getprop("ro.product.device") == "surnia" ||
getprop("ro.product.device") == "surnia_umts" ||
getprop("ro.product.device") == "surnia_udstv" ||
getprop("ro.product.device") == "[B]surnia_uds[/B]" ||

abort("This package is for device: surnia,surnia_umts,surnia_udstv,surnia_uds; this device is " + getprop("ro.product.device") + "."););

...

updater-script in r8 (not for surnia_uds - the entry is missing)

ui_print("Squid Kernel for Motorola MSM8916 Devices");

assert(
getprop("ro.product.device") == "surnia" ||
getprop("ro.product.device") == "osprey" ||
getprop("ro.product.device") == "lux" ||

abort("This package is for device: surnia,osprey,lux; this device is " + getprop("ro.product.device") + "."););

...

If it has been a little mischief, you could change the line with "surnia" to "surnia_uds" and install. - Not sure ...
[E 2015 Original Android Development] squid2:
Oh, sorry, I hadn't realized that TWRP also does indeed label the dual sim model as surnia_uds. Are you using my TWRP builds?

Anyway, the kernel should work on your dual sim device, it's just the assert preventing install. You can manually edit the updater script zip for now to make it install on your model.
[E 2015 Original Android Development] entony80:
r8 installed on Cm12.1 build 48 and work really great. Thanks for your work
[E 2015 Original Android Development] grofweg:
On build 50 as well. IMO its better/smoother than the build in osprey kernel.
[E 2015 Original Android Development] hehk1234:
[MENTION=6485916]squid2[/MENTION], here the fixes for dual sim models and TV. :) Good Job bro :highfive:

https://mega.nz/#!eZJmiAwJ!bazQfx1SSBUWOM-bnTPilfs7dvHnkaSZIIRk4HxRFjs
[E 2015 Original Android Development] squid2:
I'm genuinely curious as to which recovery you were using when you had the error. Were you using mine or some other one?
[E 2015 Original Android Development] P0PETIN:
[MENTION=6485916]squid2[/MENTION] What do you think about adding some governors? I don't know when you have time but would be greatly appreciated plus fast charge? Really tried testing that feature before in other devices but there was no support for them but if fast charging is not good for the battery life then never mind it but thanks [MENTION=6485916]squid2[/MENTION] for all the hard work ?
[E 2015 Original Android Development] thathtcguy:
The newest kernel r8 has the cpu at full load constantly, laggy af and terrible battery life
[E 2015 Original Android Development] Fedray:
Uhmmm I'm using it and its ok, maybe you have some process using all your power, for me battery life is ok and isn't laggy or something like that

Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk
[E 2015 Original Android Development] thathtcguy:
I checked and it showed the thing using the most power is settings, downgraded back to r7f and it works fine again

---------- Post added at 05:42 AM ---------- Previous post was at 05:40 AM ----------

Weird for me it's really laggy and eats up my battery super fast
[E 2015 Original Android Development] hehk1234:
Hahaha :p, [MENTION=6485916]squid2[/MENTION] I use this trwp with hardware encryption

http://xdaforums.com/moto-e-2015/orig-development/recovery-twrp-hardware-encryption-moto-t3118109
[E 2015 Original Android Development] PriPhaze:
i think you should be using the Squid TWRP

http://xdaforums.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649
[E 2015 Original Android Development] hehk1234:
[MENTION=6485916]squid2[/MENTION], your kernel on version R5, fixes the problem in a camera when I root the version 5.0.2 on moto E 2015, but sometimes When I reboot my device, It take two reboots to open the OS. I know, now you just build for 5.1.1, but have any chance to fix this problem ? :confused:. Thanks Sir.
[E 2015 Original Android Development] squid2:
The old r5 kernel is deprecated and I'm no longer supporting it. I'm only leaving it up for those who may need it.
[E 2015 Original Android Development] hehk1234:
Ok, here good news, almost close :D. Your latest Kernel with latest CM12.1. :highfive::cowboy:
[E 2015 Original Android Development] PriPhaze:
That looks good but how about the battery life?

And which governor and I/O are you using to achieve that score?
[E 2015 Original Android Development] starkly_raving:
I'm on lionfish and noop and battery life is as good if not better than stock. Performance is definitely better in real world use though bench marks are lower. I've found benching subjective at best anyways.
[E 2015 Original Android Development] TechnoAnder:
The improvements for zRAM it's very very good, the CPU governors have a good battery life! :D
[E 2015 Original Android Development] P0PETIN:
Awesome battery life, lasts from 6 A.M to 11 P.M ? using deadline with lionfish 998Mhz max freq 200 Min freq

---------- Post added at 07:44 PM ---------- Previous post was at 07:41 PM ----------

Using deadline with lionfish and 998 max freq and 200 min freq
[E 2015 Original Android Development] Sands207:
Just flashed this earlier with the TeamEOS AOSP 5.1 ROM and it's working great so far! How do I go about enabling zram or is it already enabled in the boot process? Either way,great work!
[E 2015 Original Android Development] atomomega:
Is it just my phone or does lionfish governor ignores freqs 1152 and 1094?

Is there a tunable parameter to make it scale through those 2 freqs?
[E 2015 Original Android Development] squid2:
It actually does end up skipping those two because it jumps in 30% increments rather than going through each step. Reason being that if 998 MHz is too slow for the load, then 1094 and 1152 will probably be too slow as well, so it will jump straight to full speed at 1209 MHz. Also, when scaling down, if 1209 is too fast, 1152 and 1094 will probably also be too fast, so it will jump straight to a lower frequency.
[E 2015 Original Android Development] Android_noob17:
For some reason version r8 of your kernel doesn't want to go into deep sleep. I started to notice this problem when I flashed r8 but r7f worked perfectly. Does anyone else have this problem?

CPU: Max 1209, min 200

CPU Governor: lionfish

I/O scheduler: fiops
[E 2015 Original Android Development] squid2:
Haven't had any such issues myself. Which ROM are you running? Have you checked for wakelocks? Does the issue persist if you reboot your device?
[E 2015 Original Android Development] Android_noob17:
I'm using Pac rom (the latest version) and no I haven't checked for wakelocks. When I reboot my phone it would going to deep sleep for a few seconds ( sometimes minutes) then I'll go to the lowest set frequency. I'll reboot again and let you know if goes into deep sleep in the morning.
[E 2015 Original Android Development] xukashi:
Same setup but cm12.1 here. No problems for me
[E 2015 Original Android Development] Filz0r:
I think I also have this problem with the PAC man ROM, the only difference is that I hava min freq set to 400 mhz, this screenshot is taken after my phone not having it's battery drained till 0% for the last 3-4 days, I think it's a rather low the deepsleep time...

Edit: https://drive.google.com/file/d/0B-X6n6ML6m_Jc0JlOWFfX3RGcUE/view?usp=docslist_api couldn't post the screenshot, here's a link to it
[E 2015 Original Android Development] Android_noob17:
I figured out what the problem was and ironically it was greenify that was keeping my phone from going into deep sleep. Once I change some settings in the app I stopped have problems :) . thanks for the help.
[E 2015 Original Android Development] Filz0r:
What settings did you change, I also have grenify installed
[E 2015 Original Android Development] Android_noob17:
I gave it device administrator and accessibility permissions and I made sure that telephony wakeup and the don't remove notification options were checked ( disable wakeup timer coalescing if on) In greenify settings
[E 2015 Original Android Development] pixiebob:
squid2: don't know if it was already been asked but can you add feature usb fast charging ?
[E 2015 Original Android Development] mykenyc:
are you going to overclock it?