yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] EB20XY:
are there newer drivers in 7 and 7b (LA.BR.1.1.3_rb1.24) than in 7c (LA.BR.1.1.3_rb1.23)?

:confused:

I use 7b and have no issues sofar.
[E 2015 Original Android Development] squid2:
The main part of the kernel is LA.BR.1.1.3_rb1.24 in all r7x releases. However, r7 and r7b, the WiFi driver is based off LA.BR.1.1.2_rb1.17. In r7c, I updated the WiFi driver to LA.BR.1.1.3_rb1.23, since that is what I'm using in the latest osprey build for which people have been reporting good things about WiFi. Sorry about the confusing version number scheme, it's Qualcomm's fault.

Anyway, the old driver in r7b worked fine for me too, and I only updated the WiFi driver as a shot in the dark in case it might fix something for someone on CM.
[E 2015 Original Android Development] EB20XY:
Thanks for the explanation. There is no need for any excuse, I believe. :)

So, if still someone has problems with wifi anyway it would help to get logs, right ?
[E 2015 Original Android Development] dwane3:
1524,after install version 7c,dhcp working,but no set memory region wifi and sometimes when toggle wifi tel random restart,also is not sheduler in setting of the kernel..
[E 2015 Original Android Development] squid2:
What do you mean by "no set memory region wifi"?

I tried toggling WiFi on and off a dozen times (on stock ROM right now) and didn't encounter any reboots. Could you post a last_kmsg after your phone does a random reboot?

The scheduler can be changed. Just use an app like No Frills CPU control, or your favourite alternative.
[E 2015 Original Android Development] thrasher194com:
Switch to no frills and got back lionfish/fiops, thanks!!!

---------- Post added at 08:31 PM ---------- Previous post was at 08:05 PM ----------

---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------
[E 2015 Original Android Development] dwane3:
wifi region toggle set to usa mode,restart and settings are not saved,also,setcpu app does not show sheduler mode.
[E 2015 Original Android Development] yelupic:
Settings > Wi-Fi > Tap menu > Advanced > Wi-Fi region code

(Usually not set to any value per default - in scritch's cm-12.1-surnia rom)

___

Edit:

Regarding the changelog:

Is this true yet?

Post #1
[E 2015 Original Android Development] squid2:
The disclaimer is outdated, I forgot to remove it. The recent r7b and r7c versions should work on any variant and rom that supports enforcing SELinux.
[E 2015 Original Android Development] squid2:
Squid Kernel r7d

I've posted a new build where I updated both the WiFi driver and kernel with Qualcomm's latest changes in LA.BR.1.1.3_rb1.25. I saw some interesting changes in the WiFi driver that changed timeouts when unloading the WiFi driver and addressed a race condition. Maybe these changes will solve the WiFi bootloop issues that some were reporting with the previous release. I've never had any of these WiFi issues myself on surnia, so I can't confirm if it fixes anything. Try it out and let me know.
[E 2015 Original Android Development] Filz0r:
Got a random soft reboot after flashing version 7d but its stable now, if anything happens again I'll let you know
[E 2015 Original Android Development] starkly_raving:
Haven't experienced the reboot using the included kernel or 7d all's well here.
[E 2015 Original Android Development] kraftmaschine:
No reboots here. Great kernel, thanks for your work.

I tried cm12.1 today and noticed that the notification light is working there. I didn't know the moto e 2015 even has a notification light.

But I was wondering if this is rom or kernel related?
[E 2015 Original Android Development] Fedray:
Is working all the time or only when phone is connected to charger?
[E 2015 Original Android Development] squid2:
There is a notification light that was disabled in the kernel. Scritch reverted the commit disabling the LED, and added in things required to get LED notifcations working on CyanogenMod. I haven't yet included the revert, so the notification LED won't work on this kernel right now.
[E 2015 Original Android Development] dwane3:
Sorry,r7d when push the toggle wifi also i get bootloop reboot..
[E 2015 Original Android Development] squid2:
Could you try capturing a log? See this post:

http://xdaforums.com/showpost.php?p=62476636&postcount=74
[E 2015 Original Android Development] yelupic:
pstore after bootloop

http://xdaforums.com/showpost.php?p=62479012&postcount=75
[E 2015 Original Android Development] thrasher194com:
Flashed cm12.1-8/22/15 with r7d lionfish / fiops
[E 2015 Original Android Development] squid2:
Squid Kernel r7e

Let's try yet another WiFi driver. This time I upgraded it to LA.BR.1.2.4_rb1.14. Hopefully this one won't cause bootloops. As with all previous versions, this driver works fine for me, but that doesn't mean anything, because every driver seems to work fine on mine but nothing seems to work for everyone :(. Let me know if this driver works for you.

This build also adds support for LED notifications on recent CyanogenMod versions (scritch's build 39 and newer).
[E 2015 Original Android Development] Filz0r:
Just flashed this one, WiFi works fine and no bootloops so far and LED is working fine, thanks a lot for your work!
[E 2015 Original Android Development] yelupic:
Lucky me. - I'm sorry being the messenger of bad news.

(Clean install/all wipes, installed build 40 zip via adb sideload, immediately followed by sideloading supersu and squid's brand new r7e kernel, then booted up.)

_
[E 2015 Original Android Development] squid2:
Squid Kernel r7f

That sucks :crying:

Here's another try with downgraded WiFi drivers this time (LA.BR.1.1.2_rb1.18). Thanks for taking the time to test.

I wonder what is different between your device and mine. It is evident that only some users are affected by this bug, but it must be a significant number as several people have reported it. My device is an XT1527 and yours is an XT1524, but I'm not sure if all XT1524s are affected or no XT1527s affected.
[E 2015 Original Android Development] PriPhaze:
Ehm i tried too using the last Kernel Version ... still reboots when turning off wifi

(When you trigger the bug it will keep rebooting by itself)

Im using XT1527

EDIT: That was for r7e version, just installed the f version and it seems to be working good!
[E 2015 Original Android Development] squid2:
Had you tried r7e, r7f, or both?
[E 2015 Original Android Development] PriPhaze:
Yea just did, check the edit :3 thanks for the work also and the effort :)
[E 2015 Original Android Development] yelupic:
Thank you, I will test and report back my findings. - For a possible difference. - If I recall correctly, you gave us Moto E 2015 owners a clear warning regarding re-locking the bootloader (BTW: Thank you again for your explanation). - Did you alter your device with another firmware to revive your device (I guess, it was soft-bricked that time)?

You know that already for sure, but for some others here:

Via fastboot getvars all you can see the date of manufacture and a bunch of other key/value pairs. - Or within the fastboot menu step down to Barcodes with Volume down then press Power button to display device specific values; e. g. Production Date.

Mine is March, 2nd 2015 (03-02-2015).

Downloading ...
[E 2015 Original Android Development] Fedray:
For me phone was restarting when turning wi-fi off too with r7e version, r7f working fine! XT1527
[E 2015 Original Android Development] yelupic:
Germany. 2 o'clock in the morning. A lonely guy is switching off his W-LAN connection after installing SMK r7f (squid's magic kernel r7f) ... Drumroll ... It works! :D

Well done, @squid2 ! - What did you see/change in the code?

(I installed r7f over r7e after wiping caches. - Connections/reconnects work fast.)

_
[E 2015 Original Android Development] squid2:
Hooray! :D Thank you very much for testing.

I went out for an hour long walk and pondered what could be the difference between our devices. You mentioned the time I had bricked and revived my device, and recalled that I used unconventional means to bring it back to life. That got me thinking. My device is running a newer bootloader, trustzone, and modem than what anyone here has. It's similar to what osprey (2015 Moto G) shipped with. Moto G users haven't reported any issues with the same WiFi drivers. I also recalled that here, the only people who said it worked fine were in North America. The 5.1 upgrade has only been released in North America. The 5.1 upgrade includes newer modem software in addition to newer Android. Only North American users would have upgraded their the modem, everyone else would still be running the old 5.0 modems. Also, some North American users may have upgraded Android but not upgraded their modem. The modem has tie-ins to WCNSS, the WLAN subsystems. The WiFi drivers that were current when the 5.0 modems came out were from the LA.BR.1.12 series. The LA.BR.1.1.3 series came out along with newer modems. The 5.1 modems for surnia and osprey are from the LA.BR.1.1.3 era.

What am I leading to? I think there was a bug in the 5.0 modems that the LA.BR.1.1.2 series drivers didn't trigger. Changes Qualcomm made for the LA.BR.1.1.3 series would have started to trigger the bug, and so Qualcomm fixed it in the newer modems. I want to find out if my theory is correct.

So as a bug post-mortem survey:

Users who didn't experience crashes turning off WiFi - did you upgrade your modem software at some point?

Users who were having crashes turning off WiFi - were you running the original (5.0) modem for your device?
[E 2015 Original Android Development] Fedray:
What do you mean with "modem"? Is the NON-HLOS.bin archive? I'm from Argentina and I have USA 5.1, but with my old 5.0.2 Latin America modem because with 5.1 modem my phone will lost signal (or something like that, I don't remember)
[E 2015 Original Android Development] squid2:
Yes, NON-HLOS.bin is the modem software.
[E 2015 Original Android Development] Fedray:
Then the answer of "Users who were having crashes turning off WiFi - were you running the original (5.0) modem for your device?" is yes, at least in my case.
[E 2015 Original Android Development] PriPhaze:
Ok im one of those running the original 5.0 modem, when i upgraded to 5.1 i made sure to not overwrite the modem file.
[E 2015 Original Android Development] thrasher194com:
Running r7d with cm12.1-8/22

No bootloops for me.
[E 2015 Original Android Development] rokban:
R7f is working fine for me finally.

Also I have old modem 5.0.2 ..
[E 2015 Original Android Development] JobSup:
Running the d version of your kernel at the moment, also still with the original 5.0x modem (Germany). I updated to 5.1retus, but without flashing the modem (just flashed boot and system according to http://www.android-hilfe.de/thema/e...-1-mit-original-us-firmware-5-1-retus.710133/)

Toggle Wifi works with d version of kernel, but Airplane mode bootloops :/ Will try the new e version now.
[E 2015 Original Android Development] dwane3:
1524,v. F,no restart and bootloops,but very low level of wifi,why?older drivers?can fix this?thanks squid2.
[E 2015 Original Android Development] squid2:
Had you upgraded your modem to the version that came with 5.1? If you took an OTA update to 5.1, your modem will be the new version. Or you could manually update it with fastboot or a flashable zip containing the modem.
[E 2015 Original Android Development] thrasher194com:
I'm on 5.1 radio's and updated PRL...
[E 2015 Original Android Development] squid2:
WiFi Bootloop Verdict

Thanks for the reports everyone. It sounds like everyone running 5.0 modems had issues with the upgraded WiFi drivers, but they worked fine for everyone on 5.1 modems. So my theory about modem versions was correct. The older LA.BR.1.1.2 series drivers featured in r7f work for everyone.

One last question: [MENTION=1695532]dwane3[/MENTION] reported weak WiFi signal strength on r7f. Is anyone else having this issue, or are the r7f drivers fine for most people?
[E 2015 Original Android Development] dwane3:
Only on r7f weak signal,on r7d the best level from all kernels for my 1524..
[E 2015 Original Android Development] Fedray:
I have Wi-Fi signal problems too! With f version

Enviado desde mi XT1527 mediante Tapatalk
[E 2015 Original Android Development] rokban:
I too confirm that in f version WiFi is weaker.
[E 2015 Original Android Development] yelupic:
r7f - WiFi signal is strong and the quality is high here. - Scan connects and re-connects happen in 5 to 15 secs. after switching the W-LAN on/the Airplane mode off. - I adjusted the W-LAN to fixed channel 13.

Edit:

Running no Google Apps (pure ROM with squid kernel).

Captive portal login disabled (the app) and also switched it off in terminal:

su
pm disable com.android.captiveportallogin
settings put global captive_portal_detection_enabled 0
settings put global captive_portal_server 127.0.0.1
reboot

Revert (re-activate) this to default with:

su
pm enable com.android.captiveportallogin
settings put global captive_portal_detection_enabled null
settings put global captive_portal_server null
reboot

_
[E 2015 Original Android Development] dwane3:
squid2,for 1524 is not stock firmware 5.1,i can flash modem from another model,for exampe your 1527 or will be bugs?If yes,please add correct modem file,my M8916_200602.03.02.58.05R.
[E 2015 Original Android Development] thrasher194com:
WiFi and mobile 3G/4G are working.
[E 2015 Original Android Development] Fedray:
I went back to stock 5.1, going to test f version of kernel and see if I have wifi signal problems too

Edit: atm all seems to work fine! Amazing work squid2
[E 2015 Original Android Development] PriPhaze:
I have been testing it and the wifi is working alright and the signal is just like it was before. At least for me that didnt change
[E 2015 Original Android Development] Fedray:
I'm mentioning that led (at least for me) also works in stock 5.1 too!

Hey, I have a question, WhatsApp isn't working right, not sure why but not receiving messages until I open the app or messages are late like two hours, is that something about WiFi? Because with mobile data doesn't seem to fail
[E 2015 Original Android Development] dwane3:
Yes,for me too..! On stock 5.1.
[E 2015 Original Android Development] kraftmaschine:
No wifi problems at all, using latest kernel version on xt1524 (Germany).

Thanks for led support on stock rom, [MENTION=6485916]squid2[/MENTION].

Why would Motorola not support led notification even if there's a led inside? I don't get it.
[E 2015 Original Android Development] Humoxxx:
Hi Squid! Just a question.... Did you removed the link of your CM build with this kernel? I am running the 20150808 build and works like a charm. Only a thing with the whatsapp audio sometimes not hearing or stranger sounds in the audio messages.

I want to know if you updated the build but cannot find the link.

Thanks!
[E 2015 Original Android Development] thrasher194com:
Flash cm12.1-8/27

https://builds.hubdroid.com/cm12.1/surnia/#modalDownload

Flash r7f

Profit

---------- Post added at 11:42 PM ---------- Previous post was at 11:38 PM ----------

But if you are 8/8 you'll need to flash clean.
[E 2015 Original Android Development] rokban:
Latest cm12.1 + squid kernel ,sensors are working?
[E 2015 Original Android Development] DroidFreak32:
Using 8/27 PAC-man ROM based on cm12.1 build 40. Flashed the latest kernel and all sensors work ! Dhcp is still slow. Other than that it's fine!

-xt1521-
[E 2015 Original Android Development] tattooedgod:
I'm on boost Mobile variant wondering if I can only use CDMA version or the f like the rest
[E 2015 Original Android Development] squid2:
The newer versions (r7b and up) are universal and work on any 5.1 ROM and variant (including CDMA).
[E 2015 Original Android Development] ahjee:
Great work on the kernel. Runs great coupled with the latest PAC Man Build
[E 2015 Original Android Development] tattooedgod:
Been trying to use kernel on pac but just get boot loop on boost mobile variant
[E 2015 Original Android Development] PriPhaze:
Ok i figured out that the buzzing sound which sometimes was really bad was due to the FIOPS scheduler... I changed to cfq and it seems to be solved and i can reduce the frecuency of the CPU to 400MHz minimun with no problem.
[E 2015 Original Android Development] thrasher194com:
I'm using lionfish/fiops 400mhz/1.21ghz my phones not running hot or making any funny sounds.
[E 2015 Original Android Development] PriPhaze:
Everyone is experiencing different problems. The fact that you didn't have that problem doesn't mean anything actually. Anyways I didn't say anything about headphones getting hot, just a buzzing noise. It was worse while playing videos and I could easily go back to fiops and try record the problem with scr, just to show you.
[E 2015 Original Android Development] thrasher194com:
Well I'm having no LED charging light.
[E 2015 Original Android Development] adrianocolvero:
Not working on Xt1523, stuck on boot logo.
[E 2015 Original Android Development] Kenny13554:
Hey,

maybe you wanna try this: https://play.google.com/store/apps/details?id=cyb.satheesh.lednotify

Kind regards,

Kenny
[E 2015 Original Android Development] Android_noob17:
How do you control the led like if I want it to stay on continuously instead of it blinking when I get a notification? I love the kernel btw, no problems so far.
[E 2015 Original Android Development] Kenny13554:
Hey,

you might want to try this app to control you LED (not entirely sure if it works with this phone, though): https://play.google.com/store/apps/details?id=com.rageconsulting.android.lightflowlite

Kind regards,

Kenny
[E 2015 Original Android Development] adrianocolvero:
[MENTION=6485916]squid2[/MENTION] can u please compile a XT1523 5.0 stock kernel with SElinux set to permissive? I'm without camera after root and your kernel v5 got stuck at boot logo and v7 (i know its for 5.1) got boot looping. Thank you bro.
[E 2015 Original Android Development] thrasher194com:
I did have a reboot when I toggle WiFi off and on

---------- Post added at 01:28 AM ---------- Previous post was at 01:23 AM ----------
[E 2015 Original Android Development] squid2:
Which version are you running? r7f ? There isn't anything relevant in the screenshot you posted, The relevant logs are the in /sys/fs/pstore. You can pull the contents of that folder when ADB is running as root.
[E 2015 Original Android Development] atomomega:
Is there any chance of overclocking in next releases?
[E 2015 Original Android Development] xukashi:
With smartphones overclock absolute bull****. First of all, it does not really bring much, then comes to the CPU nor GPU neither be cooled and, from a certain temperature overclock back down. Overclocking is also only be realized with overvoltage which in turn shortens the battery life.
[E 2015 Original Android Development] DanHutchins:
im trying to flash the CDMA version but keep getting (signature verification failed 1) im using the squid twrp and cyanogenmod build 43 on xt1526 plese help

---------- Post added at 06:31 PM ---------- Previous post was at 06:22 PM ----------

do i need to turn signature verification off to flash this kernel???
[E 2015 Original Android Development] PriPhaze:
Of course you need to turn the signature verification off, im also using the v 43 and squid kernel and its working good so far
[E 2015 Original Android Development] atomomega:
I don't know what you mean. I have used overclocked kernels on my other devices and there's a noticeable difference, no bullsh*t.
[E 2015 Original Android Development] DanHutchins:
Sorry for the bother again but how long should I wait when booting after flashing this kernel its been about 5 minutes and still at boot animation
[E 2015 Original Android Development] squid2:
Shouldn't take that long. Which ROM are you running and which kernel version are you flashing? I recommend using version r7f with either the 5.1 stock ROM or a recent custom ROM build.
[E 2015 Original Android Development] DanHutchins:
On built 43 cyanogenmod (latest build) and trying for the CDMA version kernel will the one you recommend work on CDMA???
[E 2015 Original Android Development] squid2:
The newer kernels (r7b and up) are universal. They work on all variants, and support both the stock 5.1 ROM and custom ROMs. The old GSM and CDMA specific kernels were stock ROM only.

Installing the old stock ROM CDMA kernel would have overwritten your ramdisk. Reflash CM12.1, then flash the r7f zip.
[E 2015 Original Android Development] PriPhaze:
Clear cache and dalvik and itshould start optamizing the apps in like around 2 mins or so?

Im also in 43 cm 12.1 like a said with r7f squid kernel and everything is alright
[E 2015 Original Android Development] thrasher194com:
I'm on 9/06 cm12.1 and r7f
[E 2015 Original Android Development] squid2:
Feature Requests

I'm running low on ideas for things to add to the kernel. I like to keep the kernel clean and avoid redundant or unnecessary things as well as features that I find uninteresting, but I'm looking for suggestions on things you want added. I'm not interested in double-tap to wake, or adding in additional (redundant) hotplug implementations. However, please share any other things you'd be interested in seeing. Things that already support 3.10 series kernels are preferred, as porting features from earlier kernel versions often takes a couple hours of work, so I'll only do that for features I find particularly interesting.

If there are any neat additions you want me to backport from newer kernels (up to and including Linux 4.3), I could look into that as well. I recently backported zRAM from Linux 4.1, which adds support for parallel compression and decompression for increased zRAM performance, and also allows specifying a physical memory limit. I'll be including it in the next release.
[E 2015 Original Android Development] DroidFreak32:
If only the dhcp issue is fixed, I'll be totally satisfied ! The Wi-Fi strength is low and it takes a really long time to detect and connect to a Wi-Fi network :/ other than that there's no other issue. Battery life and performance is buttery smooth with lionfish+ deadline. Using the r7f with PAC Rom latest build
[E 2015 Original Android Development] squid2:
WiFi seems to vary from router to router and country to country. It has had good signal strength and connects quickly for every router I've tried, though it sounds like it doesn't like your router. Is the slow DHCP on every network you try to connect to or just your home network? If you go under advanced WiFi settings and change your region code, does that change performance in any way? Do the WiFi drivers that come with the latest PAC and CM builds work well for you?
[E 2015 Original Android Development] DroidFreak32:
The Wi-Fi region code is set to India. Didn't notice any improvements. The SSID of most of the networks takes at least a minute or two to show up, and when it does, if the signal strength is less than two bars, it won't connect..it'll just show "saved" .So it's not just my home Wi-Fi. I didn't have these problems with the stock 5.0.2 Rom for xt1521. The connections were strong and remained connected for a longer distance. The ssids showed up instantly too! After changing any networks to static ip, it connects fast but it's still weak.
[E 2015 Original Android Development] jpmaster:
Same wish here. I'm on a XT1524 with cm-12.1 build 44 and squid kernel r7f.

Code region Europe. Only with static IP, a decent connection is obtained. With DHCP, definitely to slow and weak. I think the problem is with the old 5.0.2 modem firmware. An update of firmware by Motorola to 5.1 should solve the problem.
[E 2015 Original Android Development] squid2:
Do the drivers bundled with with CM or PAC (when not using my kernel) work properly on your devices?