yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] squid2:
I tried to do so a couple weeks ago by modifying the device tree, but it didn't seem to work properly. Linux would report that it is running at 1.4 GHz, but the performance was the same as 1.2 GHz, so it was evident that it wasn't actually running at 1.4 GHz. I may try to overclock it again at some point.
[E 2015 Original Android Development] pixiebob:
removed
[E 2015 Original Android Development] squid2:
Version r3c

I've just posted a new build of my kernel (r3c) that fixes an issue with taking still pictures with the front-facing camera. Download links are in the first post, since the DevDB Downloads section is not letting me upload anything right now.
[E 2015 Original Android Development] pixiebob:
your kernel working great, cool to have latest kernel commit 3.10.73

may i ask you a favor can you build same kernel with original voltage frequencies.

i ask you this because i remenber when i compiling kernel with modification voltage , i had bad behaviour about cpu too much high.

i insist because i notice a different with same settings (ondemand,up to 95, etc..) between original kernel and this kernel.in deep sleep we don't care, but when we listen music it will take more juice.
[E 2015 Original Android Development] tattooedgod:
Quick ?

I'm on Boost Mobile are you boost guys using twrp from the one said in this thread or another just saw on that thread not for cdma varient. So wanted to ask before I screwed something. Thanks
[E 2015 Original Android Development] squid2:
The TWRP linked in this thread works for both GSM and CDMA variants of the Moto E LTE. Only the kernel needs to be different for cellular connectivity to work on the CDMA model.
[E 2015 Original Android Development] squid2:
Squid Kernel based TWRP is up

I've made a TWRP build that uses a stripped down version of my kernel instead of the prebuilt stock kernel (used in the Cybojenix TWRP). It's available on the downloads tab. Source for the device tree is on GitHub, linked in the second post.

Since the DevDB downloads section is working again, I've also posted the current r3c builds to the downloads tab for this thread.
[E 2015 Original Android Development] torch2424:
Dude Squid you are killing it! Thank you very much for all this! I was kind of interested into getting back into devin'g myself. What knowledge do you need really? back when I deved I just moved files into zips and changed build.prop files, but now I can code alost of stuff for android, as I know alot of java and a bit of C++. Any tips or insight into all of this dude?
[E 2015 Original Android Development] squid2:
I've been a software developer for years, though I'm fairly new to Android development. If you want to get into "real" development, I first suggest familiarizing yourself with the tools you'll be using. You'll want a solid understanding of creating and fixing Makefiles, and you should be proficient with git. These things can give you trouble, even with years of experience. Once you have those things down, I'd suggest setting up a build machine, syncing a full Android source tree (perhaps Cyanogenmod), and building a ROM for a supported device. Once you have your build system set up and working, you'll be ready to start trying to port things. The wikis for CyanogenMod, OmniROM, and such are good sources of information.
[E 2015 Original Android Development] pixiebob:
thank you i'm a big fan of your work
[E 2015 Original Android Development] squid2:
Squid Kernel r4

I've posted a new release of my kernel, version r4. Downloads are up on the downloads tab of this thread. Beyond updating to Linux 3.10.74, I've made the undervolt milder to better suit the less undervolt-friendly devices out there. I've also removed a few unnecessary dtbs from the device tree, and cleaned up a few options in the defconfig.

Due to various reasons, I haven't been able to test this new release myself. Let me know if you encounter any issues.

Be aware that the posted binaries are for the stock ROM only, and will probably not work on CM12. CyanogenMod will likely need a different ramdisk. I may publish a CM compatible version of my kernel at some point once development settles down.
[E 2015 Original Android Development] pixiebob:
thanks for the update.

installed , i have no issue you can install in your phone it's safe:laugh:
[E 2015 Original Android Development] torch2424:
Thanks for this dude, If I decide to get back into rom development soon, I'll definitely be referring to this. thank you!
[E 2015 Original Android Development] crazynapkinman:
I tried flashing this kernel on the Boost Mobile variant and it caused a bootloop. It would boot into android but would reboot when trying to start services (cell data)

I tried simply letting it reboot but that didn't work. I had to flash the stock kernel.

Thanks for the return to stock option. At least I didn't have to restore. Lol
[E 2015 Original Android Development] squid2:
Ah, so it boot and runs fine until you try to turn on mobile data. Turning on mobile data caused it to crash and bootloop? Is anyone else having the same problem?

I had encountered issues with this kernel sometimes dying ~20 seconds after trying to boot. It would always boot on the by the second or third try though. It's something peculiar about the stock 5.0.2 ROM that causes this; I get the same problems even when using a self-compiled stock kernel built from Motorola's sources.
[E 2015 Original Android Development] crazynapkinman:
Well it boots and gets to the "starting services" dialogue and it reboots
[E 2015 Original Android Development] crazynapkinman:
Confirm CDMA r3 version working on Boost Mobile variant. Camera working perfectly. After a few reboots the startup is back to stock speed. App transitioning and home screen transition seems a little slower than stock. Cause?

Otherwise no problems at all. Amazing work!

r4 CDMA causes bootloop on Boost Mobile variant. Anyone else having this issue?
[E 2015 Original Android Development] squid2:
Bizarre... I didn't touch anything related to CDMA between r3 and r4.
[E 2015 Original Android Development] crazynapkinman:
Idk either. The phone boots but won't start cell service. Hangs on "starting services" dialogue and just reboots when using r4 kernel.

As previously stated, r3 works flawlessly on Boost Mobile variant.

I am using your version of TWRP. Excellent work on that, BTW.
[E 2015 Original Android Development] PriPhaze:
I have timmer coalescing on using PAC Man Rom last build from September 23 and is working good, Theres no major battery drain or whatsoever from grennify.
[E 2015 Original Android Development] hehk1234:
People, my settings is on CM12.1, kernel R8 (Squid2), and latest build from cm12.1. Clock Min 200, Max 1,21ghz, interactive governor and fiops. Battery have nice duration, 6:30h with screen on, with Hardcore daily use, I can get 4:50 with screen on.
[E 2015 Original Android Development] fix-this!:
Seemed to cause a lot of overheating and reboots on the surnia cm12.1 rom. Had to flash the stock kernel back.
[E 2015 Original Android Development] squid2:
RAM Usage

On osprey, once we went from unofficial builds (with this kernel) to official builds with the stock CM kernel, I started receiving countless complaints of low RAM and lag that I wasn't seeing earlier on unofficial builds. I hadn't tried the official osprey builds until today, so I hadn't realized the nature of the issue until a few hours ago. An observant osprey user [MENTION=6923959]nanopp[/MENTION] pointed out a few days ago that the memory usage on the unofficial osprey builds with my kernel was much lower than the memory usage on the stock CM kernel.

A few hours ago, I tried for the first time an official CM nightly for osprey just to see what was going on, and was very disappointed by the performance, given what I was used to seeing on my unofficial builds. I also found that free RAM on the official builds was half of what it was on the unofficial ones (that used my kernel).

I then tried [MENTION=3445372]scritch007[/MENTION] 's latest CM12.1 build 54 without my kernel. While not quite as bad as official CM for osprey, I also encountered low RAM and lag. I then flashed my r8 kernel and the free RAM went back up and performance became much better again.

Here's a comparison of RAM usage when playing music with the CM music player on surnia and not running any other apps:

[IMG="CM12.1 ram usage comparison"]http://i.imgur.com/dyQGhA9.png[/IMG]

This massive difference in free RAM explains the performance issues that people have been grumbling about on the stock CM kernel that go away when flashing this kernel. I had incorporated a bunch of CodeAurora changes pertaining to memory management, and it's evident that some of these changes are having a big impact. I now need to figure out which commits in particular are responsible for the big reduction in memory consumption and incorporate them into the official CM kernel for osprey/surnia.
[E 2015 Original Android Development] rokban:
Must say this kernel did wonders ! Am on EOS ROM and had about 199-220 mb free RAM , flashed R8 Squid kernel and free ram shoot up to 388-405 mb. Great job!
[E 2015 Original Android Development] thrasher194com:
Dirty flashed 9/29 w/ squid's R8 wiped caches... All seems good.
[E 2015 Original Android Development] squid2:
Squid Kernel r9e

Today's new build includes the latest updates from the Motorola lux kernel, CodeAurora, and Kernel.org. I also did a little cleanup to slightly reduce kernel size. Thank the Moto X Play (lux) users for reporting the bugs in the r9 series. I've fixed all the issues they reported, so this build should be stable.
[E 2015 Original Android Development] atomomega:
Thank you dev!

Is it just me or it's normal that I feel my phone quite smoother compared to your previous release? :D
[E 2015 Original Android Development] EB20XY:
thanks for the effort.

But thought Moto X Play (lux) has different CPU ?:eek:

Well, flashed it and it seems to work nice like v8 :)
[E 2015 Original Android Development] Kenny13554:
ZRAM

Hey,

I'm having trouble changing the size of the zram (using both Kernel Adiutor and manual change via /sys/block/zram0/disksize). Whenever changing the value the zram sort of crashes and I have to restart my phone. I'm not sure if it is related to Squid's Kernel, however. Does anyone else have the same issue?

Best,

Kenny
[E 2015 Original Android Development] sfermat:
Sorry but what how can i install the kernel if i've already have 5.1 stock??
[E 2015 Original Android Development] squid2:
zRAM shouldn't crash when you do that, it should only refuse to do what you are requesting. zRAM size can't be set after it is initialized. It must be set only once at boot time, and that can only be done by modifying the fstab in the ramdisk.
[E 2015 Original Android Development] squid2:
Just flash it with recovery as usual.
[E 2015 Original Android Development] ahjee:
Great work on the latest kernel (r9e)!! I'm running it coupled with the latest unofficial PAC build and it's beastly...it also ran extremely well with the CrDroid test build for Surnia. Thank god for this kernel, or thank god for Squid for making this kernel rather. Keep up the awesome work you been killing it for our devices brotha
[E 2015 Original Android Development] squid2:
Squid Kernel r10

Today's release is a pretty nice one I think. As usual, I updated to the latest 3.10 series Linux from Kernel.org (3.10.90 in this case). On the new features front, I added the MDP5 KCAL colour control by [MENTION=4316709]savoca[/MENTION] and I incorporated optimized ARM crypto routines. On the optimization front, I cleaned up the defconfig to reduce size, and changed some configuration to significantly improve the performance of the virtual memory subsystem.

If you run a benchmarking tool like Antutu, you'll notice that the "RAM Speed" value will be higher on this build than on previous builds. If you're coming from r8, you may also notice that the "Storage IO" performance is higher than before, thanks to some optimizations (brought in from the lux kernel) that I added earlier in r9c.
[E 2015 Original Android Development] PriPhaze:
Very nice, thanks for all your effort
[E 2015 Original Android Development] rokban:
Currently on R9 , to flash the r10 do I need to dirty flash ROM+ kernel or do wipe cache+dalvik and flash the kernel?

Thanks for the awesome kernel !!
[E 2015 Original Android Development] squid2:
Just flashing the kernel should be fine. Be aware that a bug has been reported on r10 where moving apps to SD card is broken. I'm investigating the issue and will be posting a new build soon to fix the issue.
[E 2015 Original Android Development] sfermat:
Edit: installed and testing. Great work and thanks

Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk
[E 2015 Original Android Development] rokban:
R9e is perfect for me with EOS, stable as rock. So will stay with it.
[E 2015 Original Android Development] starkly_raving:
[MENTION=6485916]squid2[/MENTION] the kernel is brilliant...and nearly universal. Great work, look forward to seeing what you'll do in the future. [emoji106]
[E 2015 Original Android Development] Fedray:
Last kernel is just amazing. Greatest performance ever! Good job squid2 ^.^

Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk
[E 2015 Original Android Development] yelupic:
You're right ... just love it! - Thank you so much for your constant, inexhaustible efforts & all the hard work.
[E 2015 Original Android Development] squid2:
Squid Kernel r10b

Thank you everyone for all the compliments and encouragement.

This new build should fix the r10 regression regarding moving apps to the SD card. If you encounter any other bugs please let me know and I'll fix them when I can.
[E 2015 Original Android Development] EB20XY:
Thanks a lot for the new kernel and all the effort concerning our device !

It works great. :highfive:
[E 2015 Original Android Development] yelupic:
Do you ever sleep?

Thank you.
[E 2015 Original Android Development] DanHutchins:
Have tried all arm packages for 5.1 android but for some reason play store and google + don't work unless data is set to 1x on CyanogenMod 12.1 for moto e 2015 build 57 it didn't work for me on any of the cm builds and the devs say its not a ROM or data issue could someone give some guidance I have cleared data cache and factory reset the phone also tried deleting the host file with no success any help would be great
[E 2015 Original Android Development] DanHutchins:
Last I knew cm was configured to delvek I have never used art but yes I have tried that and nothing has worked
[E 2015 Original Android Development] starkly_raving:
All 5.X ROMs run ART exclusively. Some of the later 4.4.4 ROMs ran dalvik and had ART as an experimental option.
[E 2015 Original Android Development] DanHutchins:
How do I clear art? There is only wipe dalvek option in twrp
[E 2015 Original Android Development] starkly_raving:
That does clear Art/dalvik. There just hasn't been a dialogue change in the recoveries because over a third of Android ecosystem is still on 4.4.X ... Got to love fragmentation.
[E 2015 Original Android Development] DanHutchins:
I see. I'm actually going to try updating prl on stock ROM that's really the only thing I haven't tried. Not sure how to get log uploaded never had to do it so I will try that first
[E 2015 Original Android Development] Niflheim_:
You are the best. r10 works perfectly in AOSP rom
[E 2015 Original Android Development] ahjee:
Yeah r10 is absolutely incredible. Every ROM I run with it seems to be smoother and more responsive than ever
[E 2015 Original Android Development] adrianocolvero:
Awesome job, so smooth and snap!

Thank u for your efforts squid, you're the best!
[E 2015 Original Android Development] atomomega:
Squid my hero, thank you for giving a strong soul to our neglected phone!!
[E 2015 Original Android Development] DroidFreak32:
Amazing work! The latest version is just awesome! ! :D
[E 2015 Original Android Development] starkly_raving:
Yeah it is getting better and staying clean and current. You can't ask for more than that. Good job [MENTION=6485916]squid2[/MENTION]
[E 2015 Original Android Development] starkly_raving:
[MENTION=6485916]squid2[/MENTION] your kernel in let's say ...AOSPA would be amazing... (Subliminal Message Sent) lol... [emoji106] [emoji12]
[E 2015 Original Android Development] starkly_raving:
No doubt, especially now that the E 2015 has officially EOL'd and is NOT slated to receive official Android 6.0/Marshmallow. Glad we have some good development.
[E 2015 Original Android Development] Scar.6ix:
Hey i flashed the latest kernel r10b and my camera is still not working . Any help ?
[E 2015 Original Android Development] -FuFu-:
no problem here, cam works fine...

maybe bug not related to the kernel?

afaik, there was a bug with supersu, to try if its the problem, open supersu, go to Options and change the state of the Option called "Namespace separation" (i think this it, what it called in english). maybe reboot after change the option.
[E 2015 Original Android Development] squid2:
Which ROM and version are you on? This supports the 5.1 stock ROM and recent builds of 5.1 custom ROMs.
[E 2015 Original Android Development] sfermat:
Change from 5.0 to 5.1 with this kernel... Like a new cell, amazing.

Aosp 6.0 + moto app + this kernel, my dream jajja.

Can i ask why tap to wake its a no? I think i readed 43 pages and no reason... Dont know if its usefull, im just curious

Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk
[E 2015 Original Android Development] ahjee:
I don't think that's a kernel issue... I'm using the same kernel and have used it on various ROMs and the camera hasn't been an issue on any. I'm not sure which ROM you are running but maybe it's just that... Try a clean install of the ROM and be sure to flash the kernel before booting the phone
[E 2015 Original Android Development] sfermat:
One more question, i've installed kernel and select lionfish and fiops in no frill CPU so i think im using squid, but un kernel versión it say sultan@sprocket... I install zip like 6 times from squid twrp bit still same. Its correct?

Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk
[E 2015 Original Android Development] -FuFu-:
yes, its correct ;)
[E 2015 Original Android Development] till22:
But we'll still get unofficcial 6.0 ROMs and kernels, I hope :)

Going to install r10b now, thanks, [MENTION=6485916]squid2[/MENTION]!

EDIT: Thanks a lot for KCAL support. The app says "KCAL is not supported" though (this one: http://downloads.codefi.re/savoca/kcal/re.codefi.savoca.kcal-v1.2.apk ).

Do I have to change SELinux? I'm going to try that now..

EDIT2: Set SELinux to "permissive", it now works! You just made my Moto E screen awesome, thanks!!! :)
[E 2015 Original Android Development] DarkKn8:
Hi, I've been using this kernal and I'm really happy with the performance. There is one issue with my phone which is call quality due to faulty noise cancelling mic. Is it possible to have a disable option for the mic in your kernal?
[E 2015 Original Android Development] Droid187:
Link2sd is kernel or rom related? I partitioned my SD card to ext4, link2sd still not working. Thank you advance. Running Pac-Man rom and your latest kernel.
[E 2015 Original Android Development] Android_noob17:
I have the same set up as you and link2sd is working fine. Are you getting any errors?
[E 2015 Original Android Development] Droid187:
Mount script error

Mount script cannot be created.

mount: Invalid argument
[E 2015 Original Android Development] Android_noob17:
Make sure that link2sd has root permissions and/or repartition your sd card
[E 2015 Original Android Development] Droid187:
I partitioned my sdcard to 1: fat32 2: ext2 Can I make ext2 10gb or smaller?
[E 2015 Original Android Development] Android_noob17:
Yes, I made mine's about 10gb and make sure you make your second partition ext4 and then create the mount script for it in link2sd
[E 2015 Original Android Development] P0PETIN:
Hey I have been experiencing problems with calls after flashing r10b. I always have to put it on speaker phone so I can hear the other person.
[E 2015 Original Android Development] spiked_mistborn:
r10b: October 4, 2015
- Fixed move app to SD card issue

I got excited for a minute and thought maybe this was a fix for the move app to sd size limit bug https://code.google.com/p/android/issues/detail?id=182253&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars https://forums.motorola.com/posts/3d368e6b75

Alas, it looks like it's an issue in the ROM as I suspected. I guess it's an issue in AOSP that made its way into both stock and CM.

Anyway, nice work [MENTION=6485916]squid2[/MENTION] and thanks for your efforts! The only issue that I've run into is an occasional blue and black flashing screen when switching between tabs of the official Twitter app. I've been running stock 5.1 with the r9e kernel. I haven't had enough time with r10b yet to see if there are any issues.
[E 2015 Original Android Development] atomomega:
Wait a minute. Is it like a short circuit? I experience the same with the 3-dot menu in Chrome. When pressed, the screen turns all navy-blue and flickers as long as I don't touch the screen again. I thought it was just a hardware issue with my phone
[E 2015 Original Android Development] DarkKn8:
I've had this navy blue flicker with previous builds, but nothing so far with 10b. I have rebooted my phone a few times, maybe that has something to do with it.
[E 2015 Original Android Development] spiked_mistborn:
That's what I was experiencing. It may be related to dynamic video memory allocation by the kernel when creating a new surface. I believe it's been done that way since JB or Kit Kat.
[E 2015 Original Android Development] expra:
I had to revert commit 34a6472 for the camera to work on the XT1526.

Notification LED still doesn't work.

Other than that, it's flawless so far. A "thank you" hardly conveys my gratitude, but, thank you.
[E 2015 Original Android Development] squid2:
Hint: use the "squid_backport_mr1" branch for surnia. The "squid_linux_mr1" branch is for osprey and lux.
[E 2015 Original Android Development] expra:
Is the cm-12.1 branch also for osprey/lux?
[E 2015 Original Android Development] squid2:
At present, yes, the cm-12.1 branch is meant for osprey/lux and not surnia. However, it should work on surnia if you revert the camera commit you mentioned. LED notifications should work too.
[E 2015 Original Android Development] EB20XY:
Is the sentence on the first page still correct ?

"This is for the 2015 Moto E LTE only!"

This would be for surnia only, or not ? :eek:
[E 2015 Original Android Development] expra:
https://en.wikipedia.org/wiki/List_of_Qualcomm_Snapdragon_devices#Snapdragon_410_and_412

msm8916 is the shared hardware platform behind the Moto E 2015 4G and the Moto G 2015. I'm still not sure what "Lux" is, even after much googling.

---------- Post added at 08:30 AM ---------- Previous post was at 08:29 AM ----------

I tried cm-12.1 (with the camera commit reverted), scritch007's kernel, and squid_kernel_r10b-surnia.zip, and the notification light didn't function under any of them.

dmesg and logcat aren't very helpful. /sys/class/leds shows this:

$ grep -H "" /sys/class/leds/*/brightness
/sys/class/leds/charging/brightness:0
/sys/class/leds/lcd-backlight/brightness:12
/sys/class/leds/mmc0::/brightness:0
/sys/class/leds/mmc1::/brightness:0
/sys/class/leds/rgb/brightness:127
/sys/class/leds/wled:backlight/brightness:12

I'm guessing there's a missing sysfs entry there.

Edit:

I see from https://github.com/sultanqasim/andr...uid_backport_mr1/include/linux/stml0xx.h#L455 that /sys/class/leds/rgb is for the notification LED.

The odd thing is that "echo 0 > /sys/class/leds/rgb/brightness" turns off the battery LED. Am I just an idiot, and this device shares a single LED for both charging and notifications?

CM 12.1 settings for "Notification light" do nothing. "Battery light" settings affect /sys/class/leds/rgb.

Edit 2:

It seems the notification settings do work, unless it's set to "always on", in which case it acts like "nearly always off."

Well, mystery solved, I guess.