yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] joojoobee666:
Hey guys, sorry for the slight delay. New kernels up to patch CVE-2016-5195. :cool:
[Motorola Droid 4] Bobcus Leper:
[MENTION=1070688]joojoobee666[/MENTION],

What's with the N-Patches.zip? ;)
[Motorola Droid 4] zys52712:
Is it possible to overclock the gpu as well?
[Motorola Droid 4] joojoobee666:
It is and I've had it running here. Unfortunately, the very SMALL benefits gained by doing it outweighed the stability issued it caused. My time is limited, so I didn't delve any further. :(

It's a WIP. A lot of changes went in to 7.0 so the kernel needs a lot of backporting of features to support it. Hopefully, we'll have one booting soon.:good:

And an FYI to all, new kernels up; just a few more security related patches.:cool:
[Motorola Droid 4] chuchipando:
Hi [MENTION=1070688]joojoobee666[/MENTION], the kernel download links are giving a 404 not found.

edit:

Not anymore :D. Thank you :good:
[Motorola Droid 4] joojoobee666:
OOPS! Fixed :)

Thanks for pointing out my blatantly obvious mistake :cyclops:
[Motorola Droid 4] Bobcus Leper:
Thanks for the post! I have had similar kernel panics due to excessive downloading over wi-fi. Maybe this could also be the reason for wi-fi breaking after a soft reboot?
[Motorola Droid 4] joojoobee666:
Definitely not wifi related. It looks to me like OOM possibly ran amok, told the kernel to free some virtual RAM that was no longer allocated. Not sure what the exact cause of that was but I haven't seen the issue here. It may possibly be a bug from the CM side? Your error log shows that it came from user space and crashed on "shmem_truncate_range". I'll keep my eyes on things here and let you know if I see anything else.
[Motorola Droid 4] u.b.o.o.t:
Bad news: the kmsg-log I posted is outdated!

I just had another crash and wanted to extract last kmsg and it turned out to be _exactly the same as the previous one_!

The thing is - the crashes happend with my phone in the pocket. I didn't watch the red boot logo indicating a full reboot. All I got was pin entry for the SIM card. But this normally comes after a full reboot. If just the Android framework crashed, the SIM would be still unlocked, hence no SIM pin entry.

This is why I concluded a kernel crash... but maybe it was something in between....

Another possibility would be that apanic was not configured or initialized properly:

I found some info on apanic logging here: http://www.xuebuyuan.com/1362689.html

Question: is apanic configured properly on CM13? There is a dedicated mmc partition for it: mmcblk1p19 but according to the link above, some processing should be done to it in init.rc, i.e. copying contents to /data/dontpanic

I ran 'echo 1 > /proc/apanic_console' for now to flush it... Let's see if it get's populated on next crash...

EDIT: ok, my phone rebooted several times today while just sitting on my desk. But /proc/apanic_console stood empty after flushing, so nothing else to report here.... I then reverted to stock kernel. Let's see....
[Motorola Droid 4] joojoobee666:
It is enabled in the kernel config and set in the init.rc to go to data/panicreports. Indeed there are things there but a lot of the items look rather old here on mine (from September). It may depend on the severity of the crash? Not sure at this point.
[Motorola Droid 4] Bowen Miao:
this is incredible! didn't believe there were still people working on these 2 old phones
[Motorola Droid 4] rabinhood:
That's the last usable qwerty keyboard phone. Newer are unrootable (i.e. Blackberry Priv and Passport). So despite age, for people like myself, who need qwerty, it's still the best phone in the market. I'm happy that there are still people keeping it alive. Thanks guys!
[Motorola Droid 4] joojoobee666:
Hey all, new kernels are up along with a new SDCard Swap. Check the first post for details. Also, for those playing around with CM14.1, keep an eye on the kernel downloads folder on the FTP ;)
[Motorola Droid 4] chuchipando:
the kernel filenames in the cm14 folder start with cm-13. are those the right ones?
[Motorola Droid 4] joojoobee666:
Nope. Uploaded the wrong folder. It's fixed now. :good:
[Motorola Droid 4] maserati1972:
Hi!

i have a strange issue:

after have found my perfect Kernel ( CM13 OC 1.4Ghz Kernel LV) i'm trying to make Spirit FM work again...(worked perfectly on CM11) and here's what i've got:

Spirit 1 - no sound

SpiritF - ERROR:Tuner API did not start or stop.

This device may need a kernel with a working FM driver.

it may be a CM13 kernel issue in general or related to this OCs ?

Thanks!
[Motorola Droid 4] RikuKawai:
You need to use the Permissive Mode version of that kernel, and the older version of Spirit FM (the one that says it won't work on Android 5.0 or above). Older version (SpiritUL), plus SELinux permissive kernel worked for me in CM13, and continues to work in CM14.1.
[Motorola Droid 4] joojoobee666:
Hey all, new kernels up today. Just single security fix, nothing major. Enjoy :D
[Motorola Droid 4] joojoobee666:
Hey guys, another update. This one is a couple of security patches. Most notably, this addresses CVE-2016-8655. :good:
[Motorola Droid 4] JLPDA:
Going to give MoKee MK60.1 a test drive on my "spare" Droid4 - https://download.mokeedev.com/?device=maserati . Do you think you're OC Kernels work with this ROM? I'm currently running CM12.1 Run 'n Gun LV with good results (kinda' laggy) and want to try your CM13 RNG LV on MoKee.
[Motorola Droid 4] Bobcus Leper:
Marshmallow has "better" performance on our old phones than does Lollipop. Yes, these custom kernels work on all 6.0.1 ROMs.
[Motorola Droid 4] joojoobee666:
Hey all,

New kernels are up. Just some security updates and renaming. Enjoy :D
[Motorola Droid 4] chuchipando:
I am getting a failed while trying to flash the 2017-02-19 lineage 13 OC full scale lite. right after skipping the md5 check it says error flashing. I am on the spyder with stargo's lineage-13.0-20170219-UNOFFICIAL. I've not tried any other kernels.
[Motorola Droid 4] OGdroidster:
Hello, it didnt flash becuase there is no meta inf folder for the install so I made my own meta inf folder and it flashed if you do not know how to do that than just extract the the one from the previous build and then extract this build and and zip them both into the same folder and the flash will go through. I flashed the one i used kitchen to make and then I flashed another one with by the method I told you and they both worked. ;)
[Motorola Droid 4] joojoobee666:
Strange, thanks for the info. I missed that when I tested but clearly they are broken. I'll have some new ones up in a bit. :eek:
[Motorola Droid 4] joojoobee666:
Issue is now resolved. New kernels/links are up (links/files from yesterday are pulled).:good:
[Motorola Droid 4] OGdroidster:
Your welcome, thanks for the kernel I was able to use it to get rid of a memory leak in a rebuild I did of resurrection remix to satisfy my particular needs. Thanks to your kernel I just flash it and I don't have to deal with my mistake. It fixes everything :). I'm so lazy :D.
[Motorola Droid 4] schmatzler:
This custom kernel causes a bootloop with the latest lineage-13.0-20170603-nightly.

20170527 still works fine.
[Motorola Droid 4] OGdroidster:
Are you using the one with voltage or without?
[Motorola Droid 4] schmatzler:
I'm using the Full Scale ULV kernel.
[Motorola Droid 4] chuchipando:
Same happened to me on the xt912 with the full scale lite from 02/20.
[Motorola Droid 4] OGdroidster:
try using full scale lite that has no voltage it worked for me.
[Motorola Droid 4] belrei:
Same for me with the latest ROM (10 June), bootloops, none of the kernels works, not even the NON-OC kernel.
[Motorola Droid 4] joojoobee666:
Yeah, I haven't built anything for the Droid 4 in a while. It's in a drawer. However, seeing there is still interest I can blow off the dust and see about getting some updates made this weekend.
[Motorola Droid 4] joojoobee666:
Hey guys, new kernels up, new SD Swap as well. Booted fine here on a new build.:good:
[Motorola Droid 4] joojoobee666:
Hey all, updated once again. I left out f2fs module on last build.:eek:
[Motorola Droid 4] belrei:
tested on slot 1, works fine, but:

Crashes completely on stock slot, screen goes black, phone not responding at all, :crying: could boot into recovery with VOL UP + VOL DOWN + POWER keys :D

Had backed up before, could restore. :good:

Would like to use your custom kernel, but my working system is on the stock slot, any suggestions?
[Motorola Droid 4] Ryav:
Hello. Could you add full iptables support? Thanks!
[Motorola Droid 4] joojoobee666:
Flash a new ROM build or reflash the current one you are running. This needs installed every time you install a new rom as it replaces the ramdisk.img in /system/etc/kexec. Alternatively, you can extract the ramdisk.img from the ROM zip and manually overwrite, your choice.:good:
[Motorola Droid 4] demonshouter:
Just asking....is this kernel change se linux to permissive? Mine is always permissive now....idk what change it...so is it probably this kernel?

Edit: ignore this...has been explained in op...so it is permissive....thanks...

Sent from my Motobot XT910
[Motorola Droid 4] Septfox:
I applied it using Kernel Aduitor, which I believe sets everything itself post-boot (due to official CM and most custom ROMS not having init.d enabled). You're probably right as far as Lionheart goes, but man, what perfect timing.

No rush on the "safe boot" thing, certainly there are more important tasks at hand.

Also, did you ever try overclocking what passes for the FSB? Even if you can only squeeze a few megahertz out of it, that should be a tad more performance to everything...provided something (probably the memory if anything) doesn't destabilize and cause it to all go pear-shaped. As I understand the JBX folks couldn't get much out of the Razr going this way, but every little bit helps.

Keep doing what you're doing, it is good :good:
[Motorola Droid 4] frankonia:
Same here. I think the majority of the RAZRs are not able to run with 1,4 GHz.
[Motorola Droid 4] LuH:
1.4 ULV working fine on my D4. Which governors do you guys use to get the most performance when not considering battery life too much? I always carry a small external charger on me (it fits in my jacket's pocket unnoticeably) so I prefer performance - but don't want to drain the battery unnecessarily with the Performance governor.

I'm using the Interactive governor now, is it the best performance-friendly choice?
[Motorola Droid 4] Bobcus Leper:
I have the DROID RAZR. I like to use the ktoonservative governor because it gives me great battery life and performance. The ktoonservative governor even turns off all but one core while in deep sleep. Pair that with MM's DOZE, any you'll have extremely solid battery life. The ktoonservative governor also has some nifty GPU tweaks that boost the GPU when needed, but idling the GPU when preforming simple operations.
[Motorola Droid 4] LuH:
That's actually why I didn't want to use it - I usually listen to music from it when out and don't want it to stutter. But it probably won't go to deep sleep while playing music, right?
[Motorola Droid 4] joojoobee666:
ALL governors will shutdown CPU1 (second core) when the screen is off if the load is low enough. This is happening from the Intelliplug driver and is independent of the governor you choose.

No, it should not.
[Motorola Droid 4] Shobai:
[MENTION=1070688]joojoobee666[/MENTION],

These kernel patches [MENTION=3457922]stargo[/MENTION] mentions, are they compatible with your kernel? If I flash the latest ROM then your kernel over the top, will anything be rolled back?
[Motorola Droid 4] joojoobee666:
All of those patches (and many other still not in the official CM) have been applied to both of my kernels (cm12.1 and cm13) since July, 2015. So I guess technically, [MENTION=3457922]stargo[/MENTION] was just catching up with me. ;)
[Motorola Droid 4] joojoobee666:
And technically, to answer your question: Undoubtedly. If the CM mainline kernel gets updated and you flash a new rom, If I don't already have the change, it will get reverted if you flash my kernel. I need to recompile, which I'm usually pretty quick to stay on top of as [MENTION=3457922]stargo[/MENTION] is typically kind enough to warn me in advance.
[Motorola Droid 4] Shobai:
Cheers [MENTION=1070688]joojoobee666[/MENTION],

That's helpful info - much obliged! I think I'll be putting your Run n Gun Lite back on, once the latest CM13 ROM finished flashing.
[Motorola Droid 4] Bobcus Leper:
Those are not kernel patches. Those are omap-4 common patches. Those will only be updated if you update your ROM. The only time that you need to update your kernel is if three are omap-4 kernel patches. Stargo PMs joojoobee666 when new builds are released, so that OC kernels can be updated. If you flash the latest kernel with the latest built, everything will be fine, since there haven't been any omap-4 kernel commits.
[Motorola Droid 4] joojoobee666:
I don't currently have an uninstaller. There are three methods to remove it;

Boot to recovery and simply reinstall the ROM you are running do NOT reinstall.

Upgrade to the latest ROM and do NOT reinstall.

Extract the the ramdisk.img file from the current ROM zip from /system/etc/kexec and overwrite the ramdisk.img on your device while either booted in recovery (mount /system first) or booted in the ROM, then reboot.

I've updated the project information with this as well for future reference and for any other users with the same question.
[Motorola Droid 4] Shobai:
Yeah, I guess I didn't word my question very well - perhaps if I'd used 'included' rather than 'compatible'? I'm not sure. I definitely appreciate your response, but when you have stargo saying he's updated the ROM with kernel patches and you saying stargo's patches are not kernel patches, I can only conclude that [unless one of you is wrong] perhaps the same term is being used in different contexts - I just don't have the knowledge required to discern which usage fits what context :)

All the same, I wanted to be sure that the latest ROM would play nicely with the latest OC kernel, and vice versa, and between [MENTION=1070688]joojoobee666[/MENTION] and yourself I've gotten an answer I can move forward with - thank you both.
[Motorola Droid 4] joojoobee666:
No problem. Just to clarify further; if you see changes here: https://github.com/CyanogenMod/android_kernel_motorola_omap4-common/commits/cm-13.0

or [MENTION=3457922]stargo[/MENTION] specifically mentions kernel changes in his update log, then I may have to recompile (usually but not always).

Also, most of the time, if [MENTION=3457922]stargo[/MENTION] makes kernel changes and you are still running an older version of mine, things will just continue operating as they were on my older kernel (i.e. if a feature was broken before the update [MENTION=3457922]stargo[/MENTION] made, it will still be broken on my older kernel). RARELY, is a change made that requires an updated kernel of mine in order to restore functionality.
[Motorola Droid 4] joojoobee666:
Hey guys, just an FYI; SDSwap was updated today (2015-01-08) to include the changes [MENTION=3457922]stargo[/MENTION] pushed (allows USB storage devices). Not necessary if you don't need that ability.
[Motorola Droid 4] joojoobee666:
Hey all. Just a heads up: New Kernel and SDSwap. Check the first post for details. Enjoy.:good:
[Motorola Droid 4] Careless_:
so compared to cm12.1... is this rom just as reliable/stable?
[Motorola Droid 4] 3Dota:
this is just kernel not a whole rom ... and yes ... a lot better than lollipop
[Motorola Droid 4] joojoobee666:
I concur. Lollipop is no longer even in the rear-view mirror. CM13 runs that much better. :D
[Motorola Droid 4] Careless_:
My bad, had both tabs open- didn't realize which one I was replying to. Lol.

good to hear! will update next weekend... or maybe tomorrow if I gots some time.
[Motorola Droid 4] joojoobee666:
Hey, just another small update posted for the kernels and SDSwap. As usual, check the first post for details.:cool:
[Motorola Droid 4] welder73:
Does your kernels (MM,LP) support scaling?

Sent from my Razr XT910
[Motorola Droid 4] joojoobee666:
If you are referring to DVFS, yes it does, just as stock CM.
[Motorola Droid 4] joojoobee666:
Hey all, another kernel and SDSwap update for you. These include the fixes for the compass, but you will need the latest nightly as well, possibly tonight's. :silly:

Update: Confirmed. Tonight's nightly will have the rest of the compass fixes needed with this update.
[Motorola Droid 4] exxolon:
Excelent Kernel for XT912

Excelent Kernel for XT912:

My config for performace/battery is:

WIP KERNEL (BATERIA/RENDIMIENTO)

----------

CPU->ktoon

CPU

CPU BOOST->10000 20ms

INPUT BOOST->12000 40ms

CPU INTELLIHOTPLUG->DESACTIVADO

eco-rendimiento # Profiles to select: 0,1,2,3,4 ( Balanced-4, Performance-4, Conservative-4, Performance-2, Conservative-2)

hysteresis->0 (max respuesta)

valor limite->500

freq pantalla off->Deshabilitada

I/O->ROW->Estandar->4096

KSM->100 1500ms

LMK->no change

MEMORIA VIRTUAL->250Mb no change

TCP->cubic no change

---------------------------------------------------------------------------------------------------------------------------------

FRANCO RECOMENDADO (extremadamente fluido)

echo "row" > /sys/block/mmcblk0/queue/scheduler

echo 100 > /sys/block/mmcblk0/queue/iosched/hp_read_quantum

echo 75 > /sys/block/mmcblk0/queue/iosched/rp_read_quantum

echo 6 > /sys/block/mmcblk0/queue/iosched/hp_swrite_quantum

echo 5 > /sys/block/mmcblk0/queue/iosched/rp_swrite_quantum

echo 4 > /sys/block/mmcblk0/queue/iosched/rp_write_quantum

echo 1 > /sys/block/mmcblk0/queue/iosched/lp_read_quantum

echo 1 > /sys/block/mmcblk0/queue/iosched/lp_swrite_quantum

echo 15 > /sys/block/mmcblk0/queue/iosched/read_idle

echo 25 > /sys/block/mmcblk0/queue/iosched/read_idle_freq

I switched to the ROW tweaks this morning. malaroth made a slight adjustment, so use 100/75/6/5/4/1/1/15/25,

slight edit from values listed above. So far, so good.

Is my config, what is you config for you?
[Motorola Droid 4] Careless_:
Is there a way for us to post our Kernel Aduitor config files? Perhaps backup from one device and restore on another?

I just want to test some various profiles to see which one gives the best battery life and performance. I am currently running the LV FullScale 1.4, so we'll see how she goes.
[Motorola Droid 4] daniel_m:
Hi joojoobee :) Does your kernel support inid.d, or could you compile it with init.d support? Apps like Link2SD, AFWall+ or Live Boot depend on it and it is a very powerful toll otherwise. CM13 for the Droid 4 does not seem to have init.d support, even though the init.d folder is there.
[Motorola Droid 4] exxolon:
Hello, the profiles for kernel adiutor is locate in:

/data/data/com.grarak.kerneladiutor/files

commands.json

profiles.json
[Motorola Droid 4] Milp:
I'm very sorry, i posted in the wrong thread. Please delete this message.
[Motorola Droid 4] Careless_:
My CM13 install from the 01/25 nightly was running rather sluggish and somewhat of a downgrade from my last CM12 install...

After switching to the ULV Full Scale kernel for CM13, it's literally like a new phone. It responds extremely fast. Chrome actually works like a browser instead of a slideshow that changes every 10 seconds. Apps launch lighting fast, and overall OS response is "enjoyable" rather than "bearable".

Good job, joojoobee666!!!!
[Motorola Droid 4] Septfox:
[MENTION=1070688]joojoobee666[/MENTION], buddy, pal. A query.

SDswap, does it specifically force the external SD card to be treated as permanent storage, or is it a byproduct of something I did?

Further, do you suppose it's possible to get this result (external SD = "permanent"/usable for app2SD without adoption) without editing the RAMdisk image?
[Motorola Droid 4] daniel_m:
[MENTION=5521404]Septfox[/MENTION], sorry for putting my oar in, could you elaborate on how to edit the RAMdisk image and where it can be found? I am still hoping to get init.d to work (I rather rely on Link2SD than Android app2SD :) ).
[Motorola Droid 4] Septfox:
I can't elaborate on how to edit it, no. Generally speaking, for anything having to do with the kernel or things close to it, you'd make the changes you want and then compile a new copy. In the case of the ramdisk image, 7zip can view the contents of the ramdisk file, but I'm not sure whether it can safely pack things back into it or not.

As for ramdisk.img itself, it's included in every nightly in \system\etc\kexec\.

Edit: have you looked at L Speed Mod? Apparently it enables init.d somehow, assuming it does it as early as you need, you could simply run it with all options off.
[Motorola Droid 4] joojoobee666:
It is treated as permanent since we want to fool the system in to thinking it's the internal. I can possibly change it but figured that may cause issues with folks wanting to unmount it while running. I can bake you one up today if you want, if I have time. As far as achieving this without the RAMdisk edit? I can't think of anything that would work off-hand. :(
[Motorola Droid 4] joojoobee666:
init.d support IS enabled in the kernel last I checked, the problem is that CM disabled it. I believe there is a fix available to restore that functionality (not tested) but this is not something that can be done from the kernel as the modifications are made to files in the /system partition.
[Motorola Droid 4] Septfox:
Doesn't have to be today, no rush. It would be helpful to anyone wanting to reap the (still theoretical to be honest) performance benefits of app2SD without dealing with the swap, though. I personally find it a little awkward to have the storages switched like this.

As far as worrying about people wanting to unmount it while running, well...they'll only do it once.

And, that's a shame, but expected.
[Motorola Droid 4] daniel_m:
Thanks, I'll try to understand what the script does and get init.d to work. To me, it looks like init.d is disabled in CM13 because of the switch from busybox to toybox :(
[Motorola Droid 4] joojoobee666:
I believe you can still install busybox on top of toybox to restore any missing functionality.
[Motorola Droid 4] daniel_m:
Probably, but I am very afraid of all those scripts and apps out there that create symlinks to busybox commands and thereby potentially break toybox. I will try with just the busybox binary and change sysinit accordingly. I'll report when I got it working ... when ... "if" might be more appropriate :D
[Motorola Droid 4] Bobcus Leper:
Flash this to install busybox.

https://mega.nz/#!cQkR3bJI!DCguG4jW_ZUGJ5Tz6OBwpLl0rMqiMPOIBAp1TlNUoOQ
[Motorola Droid 4] daniel_m:
OK, after having spent many hours trying to get init.d to run on our Droid 4, I finally give up. :(

I got 'install-recovery.sh' (root:root, rwxr-x---) to call 'sysinit' (root:shell, rwxr-xr-x), which is supposed to execute 'run-parts' from my busybox binary (root:root, rwxr-xr-x) in '/system/bin'. All works well in the terminal and init.d scripts are executed.

Unfortunately, sysinit gets denied during boot. I assume this is due to SELinux being enforced:

155 155 W init : type=1400 audit(0.0:9): avc: denied { execute_no_trans } for path="/system/bin/sysinit" dev=mmcblk1p20 ino=259 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0

[MENTION=1070688]joojoobee666[/MENTION] Do you think a kernel with SELinux set to 'permissive' could solve this problem?

The original 'sysinit' in CM13 seems to do something with init.d ... or, more precisely, seems to be intended to do something. I assume someone is working on getting init.d to function? I was not able to find any information regarding init.d in CM13 or bug reports anywhere.

I was also not able to extract or edit 'ramdisk.img' on Windows and Linux. It seems to be a compressed 'safestrapped.cpio', but no archiver was able to extract it. All I get is a 1 kb file that only contains "garbage". (Although I am not sure what I would do with an extracted ramdisk ... probably try to change SELinux to 'permissive' myself?)