yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] Shobai:
A follow up from my earlier posts:

welder73, over in the custom kernel thread, suggested using L Speed Mod in conjunction with CM12.x and the kernel. I'm happy to report that it was a great suggestion.

I'm running the Run n Gun Lite kernel on a late April CM12.1 (apologies, I can't remember which date - the first one with 'check for updates' working again, I believe). I flashed the tweak and set up a few of the options, rebooted the phone and checked incoming calls. No issues, they are displayed quickly and can be answered. I haven't missed a call since installed the Mod.

If you're having issues with incoming calls, try L Speed Mod - there's a link in welder73's comment over in the kernel thread, don't forget to give him a Thank
[Motorola Droid 4] Careless_:
Hey, Sobai..

Can you link directly to the L Speed Mod.

Having users go through 3 different threads to get to a download is kind of redundant.

But I'm glad it worked out. The Droid 4 I received was a piece of garbage, so getting a refund on that now. Can't wait to get a proper D4 with this fix.

Hows the batt life?
[Motorola Droid 4] Puppymang:
http://xdaforums.com/showpost.php?p=60463970&postcount=229

heres his post with the link to L Speed Mod

calls certainly feel a little faster with the mod but there are still freezes here and there.

using the OC kernel with 1.4GHz i get about 3~hrs of screen time which seems pretty normal to me but the battery life is always gonna be bad on droid 4 so i just went ahead and bought a portable charger off amazon and now i never have to worry about battery life again.

does anyone else on VZW have the phone automatically switch network mode to LTE only after having a network drop? i also noticed that the phone gets stuck saying "no service" if youre traveling long distances but it still gets connection and functions normally

im using 05/02 nightly
[Motorola Droid 4] rblanca:
Right now i'm using 20150504 nightly and it's great... dont seems slow..i was using cm11 until today and again i dont feel it slow...it seems to use a little more ram but works great! Thanks stargo and everyone who makes this possible!

Enviado desde mi XT894 mediante Tapatalk
[Motorola Droid 4] joojoobee666:
You guys may want to try the next nightly. Stargo made some changes to help boost the CPU quicker on incoming calls: http://review.cyanogenmod.org/#/c/97215/. Seems to help as I been running it all day for a test, no L Speed mod (was never installed). All incoming phone calls popped up on screen within 2-3 seconds. Not perfect but I didn't miss any calls today so far. :good:
[Motorola Droid 4] Shobai:
I'll second this - I saw it was to be included in the next nightly so held off in order to download it this morning. I haven't installed the custom kernel or L Speed Mod, and it's been working fairly well. Have only had one call, and although the phone still locked up until the third ring, I was able to answer.
[Motorola Droid 4] LuH:
Thanks for testing, it seems maybe the run'n'gun works bad in combination with GSM? I completely reinstalled the phone this weekend with new 12.1 build WITHOUT changing kernel and

it seems my calling problems have gone away finally - hooray :)

L Speed Mod is interesting, trying now - not sure though how much an improvement it really is as I flashed it early in the restoring process (before all synchronized accounts were added) but love its hosts update to block ads :)

Will do, sounds good :) But now my calls are fast. I can answer in matter of seconds, compared to tens of seconds with month-old 12.0 build and run'n'gun lite oc kernel.

The only thing still bothering me are system lockups every once in a while. I suspect these lockups are connected with heavy network usage while synchronizing accounts - they never occur while offline or at 2g network.

I have five accounts for synchronization now - personal and work google account (both syncing contacts, calendars, drive, and keep, personal also used for Play store and phone backup), linkedin account (contacts only), haxsync syncing facebook contacts (no other heavy fb app installed), and dropbox for camera upload.

What bothers me the most about system lockups is there is no other way out than waiting (usually several minutes) or force reboot (holding Power+VolDn). Even if ANR dialog comes up, it doesn't respond either until system gets out of the lockup. How do you treat your lockups, did you find other way out?
[Motorola Droid 4] joojoobee666:
Along with the update [MENTION=3457922]stargo[/MENTION] made, there were some other changes to LowMemKiller that seemed to have helped some as well. Obviously, the goal is to get it working properly WITHOUT the need for a modified kernel ;)

I've noticed, however, that phone calls can still be laggy coming in if it has been a while since the last one was received (i.e. first call after sitting overnight) but in general with the above mentioned updates, things seem to have improved.
[Motorola Droid 4] rblanca:
Maybe tweaking governor's options we can have even better results... i will with that later...
[Motorola Droid 4] lucize:
I can second this, for me is the same and it seems that something went wrong in CM after the last CM11 snapshot it will newer be the same because none of core CM developers are having this problem.

Regards
[Motorola Droid 4] Careless_:
I have a feeling the lockups are directly related to ram or ram paging of some sort. or cached processes.

If my hunch with the CPU Speed tweaks was right because of my experiences with my Desire Z, then the lock-ups must be similar in nature to the ones that the Desire Z experiences, because they sound exactly the same.

Usually when it happens I am waaaaay low on ram. But... could have something to do with syncing.
[Motorola Droid 4] will5:
Guys, Im starting from scratch again.

It´s ok to let the partiton at 700MB, 10MB cache and 2GB system? Or it´s better to change this values? Isnt cache a little low?
[Motorola Droid 4] Jishkah:
I ended up increasing the System partition to the maximum allowance (1000MB), the Cache to the maximum allowance (1010MB), and the Data partition to 3300MB. Basically, I took the maximum number of increments that I could jack up the other partitions per press (3 and 10 presses, each, to get to the maximum), added them up, and then increased the increment of the Data partition 13 times.

It's an odd system, and it's moreso my weird mental habits than any specific "system", but it works for me, and I don't need to worry about running out of space. Give it a try. I definitely thought that 10MB was incredibly low, especially since the previous version of Safestrap had the default much higher, but I haven't had any issues jacking it up to the maximum allowance. Just don't make the Data partition any larger than 4000MB, since it eats away at your internal memory like crazy.

On an unrelated note, I'm gonna go back to CyanogenMod 12.1, today! I've been on CyanogenMod 11 for a while, after having switched from 12, and I can't wait to try the new version out and potentially help with development. I'll be using it without a custom kernel, too, so hopefully I can give some decent feedback on how the "vanilla" CM12.1 installation works. I'll try to update every Sunday, so hopefully I can add something worthwhile to the development process.
[Motorola Droid 4] stargo:
Cache is only used for a few very small files, as the real cache is now in /data/. Don't increase it, you are only wasting space!

Best regards,

Michael
[Motorola Droid 4] Freundschaft:
for me the ROM is significantly faster than any previous rom, I have the feeling again, after a long time, that I can actually use my droid 4 without headaches, thanks! :)

whats not working for me is: phone mute button, some issues with audio playback, some apps dont work properly (DB navigator)

Cheers
[Motorola Droid 4] Jishkah:
Got it. Is it safe to assume that CyanogenMod 11 will still need a larger Cache partition than 10MB?

Anyway. On an unrelated note, there's one thing that I noticed right off of the bat with today's Nightly:

-Google Now can't activate the microphone when setting up the "Access from Any Screen" feature.

I haven't tried to place a call, so I don't yet know if this also extends to the Phone app or not. Otherwise, from what I've seen (messing around with settings, specifically, so not much), it looks stable enough. The phone is pretty snappy. Seems like there's just a few kinks that need ironed out.

For now, would I be safe in installing the latest CyanogenMod 12 Nightly, and then upgrading to the Milestone when it's released? Or would that effectively be "downgrading"? I know that the Nightly-to-Milestone process is a bit convoluted in that the Milestone is usually based on a Nightly from a week before its release, but would that extend to CyanogenMod 12's latest Nightly, as well? Or will the Milestone be based on the latest CM12 Nightly?

EDIT: Speaking of which, does anybody have a mirror to the latest CM12 Nightly? Seems like it was pulled from the server... and I certainly don't want to go back to CyanogenMod 11 after using Lollipop.

UPDATE: The microphone works! Apparently, it's just a problem with Google Now's "Access From Any Screen" setup process hooking into the microphone; other than that, I was able to place a call, receive a call, do a Voice Search, and the microphone picked up my voice A-okay. It's just the "Access From Any Screen" setup process that can't enable the microphone. The phone's Mute button on the call screen doesn't work, but that's not too big a deal; so far, everything else seems to work, save for a few insignificant bugs.

So. To conclude, here are the issues that I've found so far, at least from a phone that has nothing but CM12.1 and the GApps package from CyanogenMod's Wiki installed:

-WiFi doesn't always work after rebooting, and I can't switch it back on. However, rebooting the phone does seem to fix it. Whether or not WiFi is enabled or disabled (and broken) upon boot seems to be a hit-or-miss, but it's not entirely broken.

-Google Now's "Access From Any Screen" setup process can't hook into the microphone.

-Call Screen's "Mute" button doesn't work.

-Auto-Brightness doesn't seem to work.

-Daydream Mode is bugged. In CyanogenMod 11, tapping on the phone's screen whilst in Daydream mode closed out of the Daydream and brought you back to the Lock Screen. In CyanogenMod 12 and above, tapping on the phone's screen whilst in Daydream mode closes the Daydream, but then immediately turns the screen off.
[Motorola Droid 4] Goodevil95:
Your kernel works with USB-OTG with External power?

I can not attach a link. USB Host Diagnostics tells me the following:

Kernel

Claims support - Yes

Device detected - No

Sorry for my bad English )
[Motorola Droid 4] maisdoiscorregos:
Somebody else realized that the compass does not work on CM12, CM11 but it works in.
[Motorola Droid 4] stargo:
No, it should not need it. Cache is already in /data/dalvik-cache/ there.

I would call that a feature as it regularly crashes our old audio-blob and kills the whole audio-subsystem in the process. ;)

There will be no cm-12.0 milestone for the Omap4 devices, as 12.0 doesn't have the performance I want to support in a snapshot. I've opted for CM-11.0 M13 instead, so yes, it would be a downgrade ;)

There will be snapshots based on 12.1

Snapshots will always be based on an older nightly with added fixes.

This hasn't happened to me at all on devices (maserati/umts_spyder).

Feature, see above.

Yes, I know. It's on my todo-list.

Didn't notice that so far, need to look at it.

Sounds like a base CM bug.

And don't even try livedisplay, our kernel-driver doesn't support it and I did not succeed in adding in the required functionality yet...

It should, because it supports the lapdock (somehow), but I can't test general device support...

Best regards,

Michael
[Motorola Droid 4] will5:
Thanks for all the info, guys.

BTW, skipping tracks with volume button is working fine since I tried latest builds.
[Motorola Droid 4] Puppymang:
i cant seem to be able to send pictures with cm 12.1. i can receive them but if i try sending them my mobile network drops and then it just gets stuck and never sends

on vzw using latest nightlies
[Motorola Droid 4] will5:
When a newer nightly is flashed, should also install gapps again?

And also mentor´s gsm patch?

Or only cm12.1 nightly zip?
[Motorola Droid 4] rblanca:
Yes, you have to flash gsm patch again

---------- Post added at 01:40 AM ---------- Previous post was at 01:30 AM ----------

Today's nightly, cm-12.1-20150509-NIGHTLY-maserati.zip, seems to work more smooth than previous

Last night...i was playing a little with my friend's Moto G witch also have 1gb of ram and stock android 5.0 and it has a loot more free ram.. I realized that Moto G had less system memory usage..it uses like 200 - 3XX mb when my droid 4 uses like 38X - 500...event when they have a lot more app installed than me...how it's posible? can we do the same?. Thanks!
[Motorola Droid 4] Puppymang:
if you use a custom kernel you have to reflash that as well

edit: rblanca already answered
[Motorola Droid 4] will5:
Thanks, gapps need to be reflashed too?

I think one time I forgot to reflash gapps and gapps were still there...
[Motorola Droid 4] Puppymang:
you dont need to reflash gapps only custom kernels and any mod for your system

i reflash the oc kernel and superSU every time i flash a nightly. i also have to reboot once more after replacing the keyboard files because i dont know how to make the keyboard layout mod into a flashable zip
[Motorola Droid 4] Mentor.37:
Patch cdma to gsm

You don't have to flesh the patch every time you flash a rom's update, the patch is persistent and everything is automatically done as for the gapps.

Remember that once that the patch is installed if you will flash it again then you will uninstall it.

Anyway everything is explained in the patch main thread and at every flash you can understand if you installed or uninstalled the patch simply reading the output that safestrap give you.
[Motorola Droid 4] will5:
Thanks guys, great info. Im ready to keep updating nightlies :D

[MENTION=5003013]Mentor.37[/MENTION] I´d read your explanation before, but wasnt sure if patch will stay on every custom rom. So, now I know. Thanks :D

I was looking at vibration settings, seems there is no way to change the vibration intensity, will be nice to have this feature. My phone scares me when vibrates on a table :eek:
[Motorola Droid 4] Jishkah:
I'd recommend wiping Cache/Dalvik Cache in your Recovery. I remember having issues with MMS on CyanogenMod 10/11, and it always happened when I reset the phone without wiping Cache/Dalvik. Odd, for sure, but it seems to fix the majority of problems... so it's a habit that's stuck with me, since. Anyway, besides that, make sure that you're using NV instead of RUIN/SIM in Network Settings, and keep in mind that it can take a minute or two to send an MMS. Personally, MMS seems to be handling fine, on my end, both sending and receiving, but that might be because I always wipe Cache/Dalvik Cache after rebooting, just to play it safe. Takes forever to reboot, but once it does, everything seems to work perfectly fine.

Sometimes, putting your phone into Airplane Mode and then taking it out of Airplane Mode fixes the problem.
[Motorola Droid 4] Puppymang:
i wipe cache/dalvik after flashing nightlies and LTE always drops as soon as i try sending mms. i also keep it on NV and tried airplane mode but it just gets stuck and never sends
[Motorola Droid 4] Jishkah:
Odd. I've never had that problem on my phone... it could be a bug that came up if you dirty-flashed a new Nightly on top of an old Nightly. Tbh, I don't really know what to say, unfortunately. :( You could try performing a clean wipe and starting over from scratch, but that does seem a bit extreme...

You could try using an alternate SMS/MMS app. I remember older versions of CyanogenMod having difficulties with MMS, but you could usually bypass that with a 3rd party SMS/MMS app. Try out Google's Messenger app on the Play Store. It might fix your problem.
[Motorola Droid 4] Puppymang:
thats a shame it seems i cant even receive pictures. hitting the download button drops lte and i have to use airplane mode to bring it back

if possible i wanted to avoid using google's messenger app because their stuff tends to be bloated but i can try
[Motorola Droid 4] LuH:
150513 nightly caused infinite loop of System UI crashing upon boot when upgrading from 150503. After several crashes wallpaper defaulted for some reason, nothing else started (not even lock screen).

150514 works fine though, nothing but the wallpaper was broken (I did not restore data, just system back to 150503 and then upgraded to 150514) :)
[Motorola Droid 4] joojoobee666:
Some changes in the device tree warrant a new SDSwap for tonight's upcoming Nightly (05-16). This is required if you want SDSwap and/or XPrivacy and support for the new CPU-Boost driver in the kernel. I also included an updated version without swap for those who want just Xposed support. If you don't want SD swapped nor XProvacy, then neither are for you. However, even if you don't plan on using XPrivacy, the SDSwap works just like normal. Support for it is simply there if you would like to use.

05-15 D4 SDSwap with XPrivacy support

05-15 D4 XPrivacy support (No swap)
[Motorola Droid 4] welder73:
What do you mean? If I update to latest nightly,I wouldn't be able to use Xposed?

Cpu-Boost?

Sent from my Razr XT910
[Motorola Droid 4] joojoobee666:
Description of CPU-Boost:

When certain bursty and important events take place, it might take a while for the current cpufreq governor to notice the new load and react to it. That would result in poor user experience. To alleviate this, the cpu-boost driver boosts the frequency of a CPU for a short duration to maintain good user experience while the governor catches up. Specifically, this commit deals with ensuring that when "important" tasks migrate from a fast CPU to a slow CPU, the frequency of the slow CPU is boosted to be at least as high as the fast CPU for a short duration.

Asfar as exposed, last I knew, it needed some special SElinux permissions. If that is no longer the case (haven't checked apparently) then let me know, I'll edit and correct.
[Motorola Droid 4] welder73:
Thank you for the explanation :)

About Xposed,if you think of the fact that we have to change selinux to permissive,that's no longer the case,Xposed is working fine.

Sent from my Razr XT910
[Motorola Droid 4] joojoobee666:
I went back and look at the changes there. They are actually for XPrivacy support, and NOT XPosed directly. :eek: So sorry for the confusion. I corrected the last post and filenames. Thanks. :good:
[Motorola Droid 4] Careless_:
So how is the latest build? is the CPUBoost working good?

Any issues that would prevent this one from being a daily rom to use?

My phone should be here any day now!
[Motorola Droid 4] Careless_:
I wasted no time in getting this absolutely mint Droid 4 working on Lolipop thanks to the help of this forum. If i could send thanks to everyone, I would!

I am just now installing the Gapps, after the phone finishes optimizing the first boot up. I thought it was just going to boot-animate forever, but she's runnin'!

Almost lost my Desire Z yesterday, which would have made this perfect timing. lol

will report on usage/experience soon!

Did find out that clock keeps crashing when i click on it. probably has to do with gapps?
[Motorola Droid 4] Careless_:
My experience thus far:

- Tried installing 4.1, then rooting, then installing safestrap 3.75, and finally CM12 nightly... it worked and everything was well, but I lost root somehow. tried flashing SU Binaries, tried different settings in dev options, etc... all to no avail... Started from 4.1 again and managed to retain root (faulty usb cable extension during end of rooting process is suspected).

- Clock does not work on the newest nightly. It force closes via the widget and via the app drawer icon

- Battery life on the Droid 4 is not as good as the Desire Z I was using, but it was a lot lower power in terms of specs and power demand. perhaps its just a performance profile thing at this point with the rom+kernel combo.

- phone is actually quite fast, and incoming calls are delayed maybe by 1 or 2 seconds. in fact, I'd say it's pretty normal delay for changing screens to an incoming call animation. Nothing to be overly critical about, IMHO. But maybe that's just CPUBoost working now.
[Motorola Droid 4] Puppymang:
are you using stock cm kernel or the overclocked? i find cm12.1 battery life to be better than cm11 unless you decide to overclock. at 1.4ghz the battery goes down pretty fast but the performance difference is pretty obvious

what clock are you talking about? lock screen? the widget? status bar?

i will try the latest nightly later but as of now im on 05/12 nightly and the clocks i mentioned dont crash
[Motorola Droid 4] Careless_:
Stock everything. Haven't played with kernels at all.

The Clock is simply the clock app, which is installed with the rom. The widget seems to display the time, but i can't click on the clock app to change settings, and I can't click on the widget to add alarms.

I don't know any other way to describe it. It's the "Clock" app in the app drawer. com.android.deskclock version 3.0.3

EDIT: I decide to force stop, clear data, clear cache, and reload the clock app, and it seems to work now. I'm not sure why it faulted on first startup- and every startup thereafter, but it seems ok now!

So far the ROM seems better than my Desire Z rom I used as a daily, so this is awesome!
[Motorola Droid 4] Careless_:
absolutely no FC's or slowdowns with the rom as far as I can tell. The clock issue hasn't come back up after wiping data.

battery life is pretty good. not super amazing. phone is snappy.

only issue I have had since the clock fix was clicking on the line to type something (messaging, password entry field, forms, etc) sometimes does nothing. I have to either close my keyboard and click it, or click it rapidly, or close and open the keyboard.

not sure if that's a normal issue with QWERTY devices. My desire Z was slow during these operations so I could not tell if it was a CPU issue or a generic QWERTY/ROM issue.

otherwise, this phone with this rom is rock solid thus far. amazing!
[Motorola Droid 4] will5:
Never used data with this rom, but now Im trying, and can´t get 3G DATA to work.

APN is fine, data is on. But data icon never appear.

Any ideas?

Tried mentor´s gsm patch, but no luck.

EDIT: Created a new apn with the same settings than the one that detects and come by default from the SIMCARD, and now both are working :silly:
[Motorola Droid 4] rblanca:
Seems that newest nightlies has pocket dectection :)... someone can confirm this?
[Motorola Droid 4] sd_shadow:
http://www.cmxlog.com/12.1/maserati/

http://review.cyanogenmod.org/#/c/99415/
[Motorola Droid 4] Careless_:
05/27 nightly seems to have a lot of bugs and force closes, and even random reboots. It also optimizes apps on every reboot. i didn't have any issues with the nightly from before 05/15 i think.

edit: second time i've had the phone not wake up. the bottom row of capacitive buttons lights up, but the phone is unresponsive.

should i go back to the first nightly i had or should i install the 05/28?
[Motorola Droid 4] Shobai:
This has not been an issue for me, coming from the 150525. Have you tried a clean install?