yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] aczlan:
Try a hard reset. My D4 does not do any of those things. My only complaints have been random ANR errors (apps randomly popup ANR errors, this happens both with ones that get used and could be running in the background (Clock, Trebuchet, Sheets, etc) and ones that shouldn't be running in the background (Youtube, AccuWeather, etc))

Aaron Z
[Motorola Droid 4] maisdoiscorregos:
You use the Facebook app?
[Motorola Droid 4] JLPDA:
Although I may get a random reboot, and ANR every once in a while, I'm fairly pleased with CM12 (10/12/15 Nightly) with OC Kernel (Full 1.3Ghz), Nova Launcher, NO Facebook app (use web interface) and keeping notifications and widgets to a minimum!!
[Motorola Droid 4] aczlan:
Nope.

I just did a wipe today and flashed this morning's nightly (last clean install was back in July). We shall see how it goes.

Aaron Z
[Motorola Droid 4] Careless_:
Does Nova launcher work better than the stock launcher that comes with cm12.1
[Motorola Droid 4] aczlan:
I found Nova to be slightly faster, but not much.

Aaron Z
[Motorola Droid 4] JLPDA:
Nova is more responsive for me and has more features (ie. infinite scroll) than Trebuchet.
[Motorola Droid 4] walter79:
Is there a way to fix singnalstrengh icon?
[Motorola Droid 4] Careless_:
Just realized I haven't had an issue with the phone restarting since you advised that I give this a go.

Thanks, Septfox! :D
[Motorola Droid 4] Careless_:
Spoke too soon.

lately the phone has just been going unresponsive on its own when I'm not interacting with it.

I'll come back to it and have to press random buttons, volume, power, etc. a million times, and it shows me the Cyanogen Mod boot animation again.

Starting to get annoying :(
[Motorola Droid 4] Septfox:
Hmm, no idea. My own phone is running more or less fine (I would even go so far as to say "consistently", for days and days), but I'm still using the September 30th nightly, sooo...*shrugs*

Maybe try running a backup, wiping /system and reflashing the ROM? I wouldn't think it likely that something got corrupted somewhere, but you know how this thing is. Use the 1.3ghz kernel for a bit as well, if you're not already; OC instability can manifest itself as slow freezes too.
[Motorola Droid 4] Careless_:
I was forced to format and reinstall.

I did so this time by putting it on Rom Slot 1 with 1000mb system so i can install Open Gapps Mini because it wouldn't install on the Stock Slot due to size.

Seems to be running a lot better now. Took like 3 hours to get it running right though. Not how I wanted to spend my day.
[Motorola Droid 4] Septfox:
You might want to pull a full backup while it's running decently. If it starts throwing fits again, simply restore the /system portion of the backup to hopefully make it behave.

Still dunno why it'd start throwing fits out of the blue if you've not changed anything, but then, I don't know why the phone does some of the other things it does either : \
[Motorola Droid 4] Careless_:
it's been randomly rebooting lately with the new install too. i believe it's the kernel.

how do I revert back to the stock kernel. I'm using the joojoobee66 one.
[Motorola Droid 4] Septfox:
Can't, unless you made a backup prior to flashing it, or get someone to pull the files and make a flashable zip for you.

Reflash the ROM, that'll overwrite it. Don't forget to reflash all the other stuff you generally do, and "aftermarket" apps should be unaffected as long as you don't touch /data.

You might want to condense your troubles and steps to try and fix them, and submit them to [MENTION=1070688]joojoobee666[/MENTION]'s thread, so he knows his kernel+current nightlies might be going pear-shaped and how.
[Motorola Droid 4] d.casper.b:
Why so quiet here? Lol.

So, do you guys have MoKee? I just wanted to say that us RAZR users have been enjoying it. We are using the release builds.

It runs very well with the 1.3Ghz OC kernel and also LMK values set to "very aggressive" in Kernel Adiutor". Just wanted to share.

Sorry for hijacking this thread.
[Motorola Droid 4] Careless_:
I don't run any special stuff except for the GSM patch.

But reinstalling the ROM again is something I'll wait for. I hate having to set aside like 3 to 4 hours just to get everything set up again whenever I flash a new rom. I'll just bear with the random reloads. Not sure why it happens but oh well!
[Motorola Droid 4] Septfox:
Again...if you don't touch /data (don't wipe anything actually, iirc nightlies wipe /system anyway), you shouldn't have to set anything back up. Just flash the nightly again, flash the GSM patch and Gapps, and you should be good to go. 20 minutes tops, and that's if it has to redo the ART precompiles as it's wont to do at the slightest provocation.

Don't suffer through random reboots if you don't have to : \

Didn't know it was being built for us. My CM12 install is currently running alright, but I wouldn't mind giving something new a try. Thanks for bringing it to the thread.
[Motorola Droid 4] Careless_:
EDIT: Nevermind, Successfully flashed 11/11 Nightly.

Hope it doesn't do funny stuff with Very Aggressive LMK settings and Stock Kernel.

thanks!

---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------

How do we try that? Is it available/stable for Droid 4?
[Motorola Droid 4] d.casper.b:
I saw it for maserati on their downloads page. From what Google told me maserati is droid 4. I'm using the 151030 release build and it's working very nicely for me. Just about two weeks on Lollipop.. Usually I tend to go back to KK by this stage, but so far, I don't know, things are just working.

Sent from my Motorola RAZR Maxx (XT910)
[Motorola Droid 4] Careless_:
saw it. i'll try it next week! wish i had more ROM slots :-/
[Motorola Droid 4] d.casper.b:
I usually only use one extra slot. But currently I have none. Using my stock slot.

@edit

If MoKee works nicely on your phones, maybe you should check out the thread by us for any news regarding the ROM. Like there are problems with the 11/06 release build for example. I'm not sure how similar the experience will be on your phones, but they're both OMAP4 devices.

http://xdaforums.com/showthread.php?t=2596176

Sent from my Motorola RAZR Maxx (XT910)
[Motorola Droid 4] Careless_:
I put my current rom into Slot 1 because i wanted to see if upping the cache/system folders made a difference in performance- and for some reason it feels like it does.

maybe ill delete my stock slot and try it there!
[Motorola Droid 4] Septfox:
Been pretty quiet for me lately, aside from my battery rapidly losing usable capacity...

One experience I did want to bring in, though. Up 'til yesterday, I had run my phone for about 3 weeks without needing to reboot, and wasn't having any trouble I'd attribute to the long run time. I was having issues with it running extremely slowly on occasion, though, despite memory and CPU usage being in order; this was happening even prior to the last reboot.

Yesterday I went to play Ingress; it needed updating, so I waited while it opened the Play Store, then prompted it to start. Immediately, I was rebuffed by both the Store's "Insufficient Space" warning, and another warning I haven't seen since my FroYo days: Android's own persistent "disk space low" warning.

I 'd already known I was low on space and had meant to pull a particularly heavy app to the SD card to have a look at it before uninstalling, but wasn't previously in any particular hurry. At the moment though, I had time to kill, so I went ahead and waded through further sluggishness and got all 200mb+ of the app+downloaded data copied over. That done, I uninstalled it.

Immediate, noticeable improvement in overall performance, probably due to the I/O queue being able to finally clear itself. I wouldn't have thought that the data partition being full would make that much difference in just messing around with already-established apps (which includes the launcher if not using the stock one, fyi), but in hindsight it makes sense (assuming I correctly understand how things work); apps read and write lots of user and (when exited/restarted) state data to...well, /data, and the latter is expensive when empty flash space has to be scavenged. We're not in really good shape as far as internal storage goes anyway because of lack of TRIM, but at least with space available the controller can be a little more picky about where/how it writes.

TL;DR if running on the original /data partition try and keep 100-200mb+ of space available for best performance (yes, that means you won't be able to keep all 13 flavors of Angry Birds, sorry), if running on a slot then definitely over-provision a bit when you can afford the space.

Now, I wouldn't think that this extends to /system...but in its case (if using stock) I would recommend what I always do, if only to shorten nightly flashes: use a Pico/Nano/Micro gapps package. Pico gapps and the ROM together leave a healthy ~130mb of space available in stock /system, down to about 50-70mb for Micro. Install what you need via the Store, so only the core services are wiped out every time you reflash.

On a final and unrelated note, it looks like we're getting some changes to improve OOM handling in this next nightly, so make ready :)
[Motorola Droid 4] joefuf:
I'm just surprised at this point in the game that there's no way to increase the partitioned space. 3GB for all of your apps and data is crazy. I wouldn't think we would still have to pick and choose one app over an update or something anymore.
[Motorola Droid 4] Septfox:
There've been attempts to repartition, since we have a few gigs of space bound up in /preinstall, /webtop and /cache. In fact, one attempt was made fairly recently, and met with failure; apparently the bootloader verifies that the partitions are all "correct" and won't allow the boot process to continue if they aren't. Essentially, the repartition soft-bricked the phone.

As far as what we can do to increase effective capacity...in theory, it's possible to use symlinks to transparently move apps off /data and into the internal SD (edit: or other partitions, as long as they're mounted when they're needed), and still have them behave normally...but I haven't really looked into it much. Lollipop's native app2SD also works "ok", but wastes an additional amount of space over what you'd expect, for some odd reason.
[Motorola Droid 4] JLPDA:
Running 10.10.2015 Nightly with OC Kernel (1.3ghz) with good results. Definately keeping 20%+ free memory on sys partition, emulated SD card, and RAM will keep things moving along nicely. Also using Greenify and MinMemory Manager (keeps RAM to 200MB+). Not sure add'l OOM patches to the ROM will help all that much. Let me know if you take the nightly and see any difference...good or bad!!
[Motorola Droid 4] Septfox:
Not so much a patch in this case, as it is porting in a useful mechanism in. See http://review.cyanogenmod.org/#/c/120936/. We also get a patch to the memory compactor, which ought to help keep a bit more ready-to-use.

I've been on a nightly from something like 3 months ago, so I decided to take the plunge. For anyone doing the same (and if applicable): make sure you grab the latest version of Xposed (v78, for LP/sdk22). I had v70 on my SDcard and was foolishly flashing that, and all it was getting me was infinite boots. The upgrade was otherwise uneventful.

OOM performance has definitely improved. Critical memory levels (approaching 100mb) are still quite slow, but the phone remains usable enough to save it by manually killing things. Letting it dip below 100mb is still a good way to get a long wait followed by a 'I GIVE UP' hot-restart, but eh, what can you do.

More relevant for the average user: the performance hit for going under 200mb seems lessened, and it feels like it has less trouble getting memory cleared. Might be able to go for slightly less agressive settings now; I'm going to aim for about 160-170mb and see how things go.

I can't say for 100% sure if the performance benefit is worth giving up overclocking and various other neat things in the custom kernels (particularly if you can do 1.4ghz), but mine seems to be working pretty well. Needs more testing.
[Motorola Droid 4] Bobcus Leper:
http://www.cyanogenmod.org/blog/a-marshmallowy-cm :good:
[Motorola Droid 4] MrPib:
Loving CM12.1 on my trusty Droid 4. One question: If I'm running the latest nightly. Is it a step backwards going to a JJB666 kernel that's 2-3 months old?

BTW, just found a nice list of nightly changes for CM12.1: http://www.cmxlog.com/12.1/maserati/
[Motorola Droid 4] Bobcus Leper:
Yes. Do not use that kernel until it is updated, because it does not contain four performance improving commits.
[Motorola Droid 4] Bobcus Leper:
Someone with a D4, give this a flash! :fingers-crossed::victory::o:svetius::highfive:

http://droid.cs.fau.de/cm-13.0/test/

---------- Post added at 11:36 PM ---------- Previous post was at 11:04 PM ----------

It's gone now.:crying:
[Motorola Droid 4] chuchipando:
its back :)

http://droid.cs.fau.de/cm-13.0/test/
[Motorola Droid 4] moodroid:
Thanks for the heads up, guys, and thanks of course to Michael and the CM team.

Looks pretty good to me.

Unfortunately, it seems to output sound to the speaker even when my headphones are plugged in, so had to stop testing.
[Motorola Droid 4] Bobcus Leper:
Hey, at least sound works now. It was broken when [MENTION=3457922]stargo[/MENTION] first got MM booting on the D4.:good:
[Motorola Droid 4] stargo:
Hi,

can anybody on Verizon please test if the CM-13 image has working phone/data for you? It's now working for me on GSM/UMTS (and no longer needs a special patch, I intend to push this to CM-12.1, too).

Thanks & Cheers,

Michael
[Motorola Droid 4] Bobcus Leper:
Any plans to release a build for the XT912? I could test everything except that which pertains to cellular data.
[Motorola Droid 4] chuchipando:
Ditto here. :)

Sent from my XT912
[Motorola Droid 4] MrPib:
Hi Stargo. Installed to SS slot#2. No data on Verizon. I can make calls, however.

SIM status:

Network = unknown

Cellular Network Type = unknown

Service State = Voice in service / Data out of service

Cellular Network State = disconnected

My phone number is correct
[Motorola Droid 4] stargo:
Hi,

As building for a "new" device (when I haven't built for it after cleaning up the last time) always takes about an hour, I only built for maserati. I'll start the build for the spyders in a moment and will upload them (if I don't forget that) when they are. If I forget I will upload them this evening when I get home again.

Thanks. Did the signal-icon show signal-bars or just a missing sim card?

Do you by any chance have adb installed on your machine and could run "adb logcat -v time -b radio >radio.txt", then rebooting the phone and connecting it while it is on the initial logo display and let it run until the system is up for a few minutes? This could help me find the cause for the problems on CDMA.

Do you have LTE service or "just" CDMA?

Btw, I have uploaded a new build with a fix for AOSP keyboard crashing after installing gapps (gapps include a library which is not compatible with omap4).

Thanks & Cheers,

Michael
[Motorola Droid 4] MrPib:
Hi Michael. I'll check that out and give ADB a whirl tonight or tomorrow night.

Never got a missing SIM card message. I have Verizon LTE. Hmmm, I'll turn off LTE and see if I get data.

Thanks for working on this!
[Motorola Droid 4] joojoobee666:
Not sure why. What happens when u drag down from the clock area?
[Motorola Droid 4] sharptv:
i get the notifications pulldown, but the quick settings doesnt show when i slide down again. I have tried the two fingers method and it also didnt work.
[Motorola Droid 4] rush242:
Wipe Stock Slot?

Welp, I skrewed up the Stock slot somehow. Nothing would boot, CM11, JJB's CM12, nothing. So I sideloaded CM11 onto Slot 1, and all is well.

I'm at work, so I can't fiddle with it now. Quick question: I seem to remember that I can go into recovery and delete/completely wipe slots. Does that hold true for the Stock Slot as well? The plan is to put JJB's CM12 back onto Stock and go from there, but that wasn't working at all last night. Needed the phone for today, so I stopped meddling. Heh

Any tips, things to look out for?

Thanks again.
[Motorola Droid 4] joojoobee666:
Ok, finally had a chance to look it over, confirmed. I only tested to make sure it booted due to time constraints but I'll get that fixed and upload a new one today.
[Motorola Droid 4] thelolotov:
I've had it forget my wifi password a few times, I don't care too much, as I don't use WiFi often.

Okay, so JJB and I have reproduced this issue extensively, can you guys try making Hangouts calls? Doesn't seem to matter if they're voice, video, or Google Voice, if they go over data, they drop, and data drops, cycles from EVDO to 3G and never goes back to 4G until you reset it.

This issue is driving me nuts.
[Motorola Droid 4] rush242:
Stock slot wipe

Yep, just tried the stock slot again, anything installed in there goes into a boot loop.

If I want to truly wipe it, do I go into "Advanced" and click all of the check boxes? I've been hesitant to do that as I don't want to wipe the internal sd-card. That is where the ROM/GApps I want to install are stored.

Any thoughts?
[Motorola Droid 4] sharptv:
whats's your safestrap version? you can do a complete wipe, go to advanced and check all the boxes, except for sdcard and internal storage, that way your installation files will not be deleted. make sure you install a rom after full wipe, or you will have to rsd 'cause you will lose safestrap once you reboot.
[Motorola Droid 4] rush242:
3.75

Safestrap 3.75, great, thanks.
[Motorola Droid 4] joojoobee666:
I had to do a bunch of cleanup and a bunch of testing, but it's fixed. Here's another with no GApps but Quick Settings is working now:

12/12 ROM No GApps - MD5

Not really sure what went wrong but somehow it only worked with GApps installed. I had to clean out for another reason anyhow so I didn't bother to dig any further since that dig the trick.
[Motorola Droid 4] joojoobee666:
Turns out WiFi has not been working for the last few builds, including the one above. Here's an updated version with working WiFi:

12/12/14 - ROM No GApps - MD5

Links in the other post are updated as well.
[Motorola Droid 4] sharptv:
The capacitive keys do not turn off when the screen is off, perhaps you could look into it.
[Motorola Droid 4] joojoobee666:
I noteiced it as well, actually noticed it a few builds back. Not sure exactly what is causing that, I'm guessing some change in CM as none of omap4 stuff has seen any updates. If you wait, they do eventually turn off after about 10 seconds (at least in my case), they just don’t turn off immediately. I'll look at it when I have some time but the issue is most likely over my head anyhow.

Despite a few oddities like the above, this build is quite stable and I'm using as a daily driver. The smoothest yet.:D
[Motorola Droid 4] welder73:
Just turn off the "Ambient Display" option in the Settings/Display. :)

Sent from my Razr XT910
[Motorola Droid 4] joojoobee666:
Well, that was easy :D
[Motorola Droid 4] sharptv:
Once [MENTION=3457922]stargo[/MENTION] pushed everything into the cm repo, we will be able to receive parallel cm updates.
[Motorola Droid 4] joojoobee666:
stargo, going to need a new prop setting:

ro.telephony.get_imsi_from_sim=true

When you make your return. ;)
[Motorola Droid 4] joojoobee666:
I've put up some new builds if anyone wants em:

12/14 ROM With Gapps - MD5

12/14 ROM No GApps - MD5

Changelog:

Advanced reboot option "Recovery" works again(it's a cludge, but what the hell. Not sure why TARGET_RECOVERY_PRE_COMMAND is being ignored)

Stock browser works in landscape mode again (CM team fixed)

Changes to the data connectivity from the CM side

APN's are visible again

Whatever else the CM team changed
[Motorola Droid 4] sharptv:
Thank you for the new build.. So far how do you find the standby battery life on lollipop? I am still using cm11 as my daily driver and battey life is really bad for me.
[Motorola Droid 4] joojoobee666:
Battery life is about the same, maybe slightly better than it was on cm11 for me.
[Motorola Droid 4] sharptv:
on cm11 the usage time is all right, but the standby time is really bad, so bad i have temporarily switched to an iphone. I have tried a flash install and also brand new battery but it didn't help, so hopefully things will get better with lollipop.
[Motorola Droid 4] Shobai:
Thanks [MENTION=3457922]stargo[/MENTION], you're a wonder!

If I wanted to give CM13 a go, which GAPPS would you recommend? I see that OpenGAPPS has 6.0 GAPPS available, I'm thinking I might try their Micro package and see how I get on.
[Motorola Droid 4] Bobcus Leper:
I used Open GApps, and they work perfectly. I would recommend the smallest size, because it will fit into a 700MB /system partition with 4MB to spare.
[Motorola Droid 4] Shobai:
Cheers [MENTION=5711114]Bobcus Leper[/MENTION], much obliged
[Motorola Droid 4] OGdroidster:
I tested everything last night om your cm-13 image and everything is working except data and on voice calls you can barely hear the voice with volume all the way up. Boot was nice and quick. I temporarily got data working after messing around with it but then when I rebooted I had no data again.
[Motorola Droid 4] Shobai:
Hey all,

Have flashed the 151207 CM13 from above, it looks pretty good on the whole. Phone is quite responsive until you open a few apps. Stock browser consistently crashes with only a few [3-4] tabs open. WiFi works, GSM works [on the Telstra network in Australia]. Haven't tried much else.

I'm trying to get Trickster Mod working, as it feels like CM13 could benefit from similar modifications as CM12 did, but I've run into an issue: Trickster Mod tells me that it can't find a whole bunch of symlinks to busybox applets. After installing their recommended busybox app, it still can't find zcat and gunzip. Any ideas?

Also, it looks like 'reboot to recovery' isn't making it into SafeStrap, but rather the old Android on its back with an access panel open and a red triangle with a black exclamation mark. Would that be a relatively simple fix? A number of apps appear to want to be able to reboot to recovery, and this seems to stump them...
[Motorola Droid 4] d.casper.b:
I tried CM13 last night on my RAZR but without the hardware keys working, I couldn't continue.

Have you tried Kernel Adiutor? It's free so you can say goodbye to Trickster Mod.

I always set the Low Memory Killer values to the "very aggressive" profile in Kernel Adiutor on LP (MoKee). I can't actually use the phone on LP without setting these values. Major help that. Might be good on Marshmallow too. But Marshmallow is still too new and we need time to fiddle.

Sent from my Motorola RAZR Maxx (XT910)
[Motorola Droid 4] Shobai:
Thanks for the tip, I've installed that app and it appears to start with no issues. I've set the Low Memory Killer settings similarly to what I had in Trickster under CM12, although I might just try "Very Aggressive" and see how that behaves.

Thanks again!
[Motorola Droid 4] Shobai:
I've had a bit of trouble with the SD card under CM13: apps couldn't write to it, so I pulled everything off and tried to let Android "adopt" it, or whatever, but no joy - it was listed as "corrupted" after Android told me it was set up and ready to go. I tried rebooting, performing the setup another 2 times with reboot in between, but no luck. I formatted it the other way and put my files back on.

Now some programs can write to it, but Titanium Pro tells me it can't write to it after updating the path... Any ideas?

Also Music is playing audio via the speaker when I have a 3.5mm cable in - how might I fix that?

thanks for bearing with me!

(Edit)

Response has been great since setting the Low Memory Killer values - no crashes, and quite responsive. Battery life has been great so far, also