yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] Septfox:
I recently transferred my old 3G phone and number to Tracfone, and today finally after two weeks of back-and-forth with support (first they couldn't transfer the Network Access Code, then it turned out to be the SIM card was the problem instead, so they sent me an identical one and it worked...*holds head*) got my service transferred to my Droid 4.

Calls and texts were working, but data would come up at boot, Android System would transfer 66kb of data, then the data connection would go back down and refuse to even attempt to come back up. After some fiddling, it seems that the default Verizon APN is the culprit (which is reasonable I guess, since TF is only "technically" Verizon).

I entered the APN information found on this page, switched to it (this took several seconds to "stick"), and rebooted. LTE (or 3G if the signal is weak enough) now comes up and stays up at boot, can be enabled/disabled at will, and goes up/down properly depending on wifi connectivity. Success!
[Motorola Droid 4] Shobai:
Has anyone else seen a regression of the call fixes from a little while ago? I recall that changes were made to bring the second core online when an incoming call was noticed, and also to upclock the cores. It definitely helped, as I was able to take calls.

For at least the last few weeks I haven't been able to take calls - the phone just doesn't wake up while ringing, just showing a black screen until maybe 30s after the ringtone finishes, and if I wake it up via the button it takes a long time to draw the screen, and doesn't display the usual incoming call screen. I physically can't do anything with touch during this time; eventually, after the ringtone stops, I might see an incoming call notification with an answer button, but hitting 'answer' has no effect.

I'm not sure when it became an issue for me again. I did a clean reinstall of the ROM a little while back, but I can't remember which nightly I used, sorry. I remade the partitions at that time, so this was a fresh install from scratch. I had been on the 0727 most recently, and just updated to 0808 this morning after missing another call from my boss. I had been on the stock kernel, also, but I've got the Run n Gun OC from 0725 to try also.

Any ideas?
[Motorola Droid 4] Careless_:
i dont even remember what version I have, but I still get the missed call issue too. sometimes the screen doesn't wake up- or i can't swipe anything. it's quite annoying- but it happened on my desire z as well- so I'm sorta used to it.

raising the lowest speed setting on the cpu governer helps.
[Motorola Droid 4] aczlan:
I have been seeing that since early July (or perhaps June?), makes me miss 20-30% of my calls.

If I have the screen unlocked and am doing something, it will sit there ringing with no change to the screen until just before it goes to VM and then I will get the small "{CONTACT} is calling, answer or ignore" box that comes down from the top of the screen.

Aaron Z
[Motorola Droid 4] welder73:
Change your minfree values (LMK) like on the screenshot :)

And try to change your launcher,I have a much better response since I switched from Trebuchet to Nova or Apex ;)

Sent from my Razr XT910
[Motorola Droid 4] Careless_:
how do i get to that screen?
[Motorola Droid 4] aczlan:
Pretty sure you need to install a separate app. Possibly this one: https://play.google.com/store/apps/details?id=com.dustypixels.minfreemanager (does not load on my Droid4 though).

I switched to Apex and things became a lot more responsive.

Aaron Z
[Motorola Droid 4] welder73:
That screenshot is from Trickster Mod,you'll need a donation version ;)

Or you can do it also with Kernel Adiutor from the Play Store,it's free :)

Sent from my Razr XT910
[Motorola Droid 4] Shobai:
Thanks welder73, I'll give those values a go. I've been running Nova since my Droid 3 days, so if there's any benefit there I'm already seeing it.
[Motorola Droid 4] Septfox:
Content Provider being that high might mess with certain apps.

I tried increasing mine the other day to see what would happen, and got a lot of pausing/stuttering in Ingress because the game apparently needed to keep reloading something (at a guess, Play Services for its data). Reducing it back to stock value seemed to fix it.

It should probably be set lower than Hidden App (so the lowmem killer looks to end unneeded background tasks first)...maybe at 200 like Secondary Server?

-

And remember, guys: if you don't particularly need multitasking, you can go to Settings>Developer options>Background process limit, and mess with that. A setting of 1 will only allow 2 apps in memory (one foreground, one background), which will keep the LMK from even needing to do its thing most of the time.

Even if you are using tweaked minfree settings it can be worthwhile to mess with this setting; fewer apps in memory (generally) means more memory free, more memory free means the low-mem killer needs to do less work, less work freeing memory means more resources available for whatever you're trying to do. Loading an app into already-freed memory is always faster than having to free the needed memory on-the-fly.

This doesn't necessarily preclude multitasking, either: I use 3/4 in combination with my own minfree settings (170/200 for Hidden and Empty App respectively), and it works reasonably well while keeping quick-switching.

Keep in mind this has to be set after every boot.

Restarting the phone every couple of days is still beneficial, too. I've been noticing that under Settings>Apps>Running, the memory used by "System" (system apps/components) slowly bloats following boot, starting at ~350mb and increasing. After several days of uptime, mine is currently sitting at ~420mb. Roughly a week ago now, it'd gotten up to over 500mb somehow, causing issues (the phone started having trouble freeing enough memory to run big apps).

Your phone is a computer, and computers occasionally like starting fresh. It only takes a few minutes at most, so do your phone a favor and reboot it occasionally regardless of any tweaks you do :v
[Motorola Droid 4] Milp:
Has anyone got an idea how i would go about changing the lockscreen so not only the eta for charging is shown but also an eta for discharging as seen in the battery options?
[Motorola Droid 4] aczlan:
Might try a widget such as https://play.google.com/store/apps/details?id=com.preinvent.batteryleft that can display that.

(no connection, never used it. Just found it searching for "battery time left widget" in the Play store)

Aaron Z

---------- Post added at 02:42 PM ---------- Previous post was at 02:37 PM ----------

I tried that app (on "aggressive"), it actually made my battery life worse. It went from 70% to 40% in 3 hours.

Aaron Z
[Motorola Droid 4] JLPDA:
CM12 Nightly

I'm currently running the CM12 7/29/15 Nightly (my original flash). Has been stable, but recently, very laggy. I've uninstalled some apps. When I "tested" a newer nightly, I lost my google services (play store). I'm apprehensive about trying the current nightly again.

1) Is the newest nightly fairly stable?

2) Will I lose google services or any other apps/data? I have a nandroid backup.

3) How about using an OC Kernel?
[Motorola Droid 4] Milp:
I upgraded from an old cm11 nightly yesterday. In the process I also installed a gsm patch, the ulv oc kernel from http://xdaforums.com/droid-4/development/5-0-custom-oc-kernel-t3041512

and the appropriate google apps you can get here in the thread. So far it runs pretty stable and quick and all the lags and crashes i used to have seem gone.

I kept my data through the update and all the google services still seem to work.

That might do something similar, but i was only referring to adding that time left eta text for discharging in the lockscreen in the same way that cm12 does does it with the eta for time left until charged
[Motorola Droid 4] Septfox:
I can't say anything as far as the last few nightlies, but I recently flashed 2015-08-15, and have had no issues aside from a random wakelock caused by something to do with fingerprint unlocking (I think). Other than that, seems to be working properly.

Make sure your backup is on the external SD card. Sadness happens when Safestrap decides your phone needs to be rebooted in the middle of flashing and renders the internal SD inaccessible...ask me how I know : \

(note that under normal circumstances this is incredibly unlikely)

You shouldn't lose anything as far as installed apps/data, as long as you don't wipe /data/. It seems like I've never lost Gapps through a flash either, even though they really should be wiped (at least, ones that are flashed along with the ROM, as they're installed as system apps); but it could just be that my brain goes on automatic and I flash gapps each time. Dunno :v

I would recommend flashing the Pico or Micro package from here, and then reinstalling the Google-sourced apps that you use from the Play Store. This (shouldn't) lose your data in these apps, and it will install them as user apps, so they won't be removed again by a future flash (you'll still need to reflash Gapps each nightly for the core stuff like the Store and Play Services). This also leaves more room free in the system partition, which is never a bad thing to have.

Extras like Xposed, kernels and ramdisks will need to be reflashed, as well as apps that install themselves as stock system apps (e.g. BetterBatteryStats).

Use one of joojoobee's kernels. Even the non-OC one should offer an improvement, but most phones can use the 1.3ghz one no problem for a decent bump in performance. If you like, try one of the 1.4ghz kernels for even more of a boost; try each in turn until you can run for a while without freezing/rebooting (e.g. flash ULV, if that freezes try LV, so on). If none of them work, well, you're stuck at 1.3ghz like the rest of us plebeians.

If you check back a few pages, there's also been some banter about changing Android's minfree settings to better serve our phone's odd memory situation; without touching them, the phone will start bogging down after a day or two of use at most (the kernels linked above have some patches applied that help reduce the performance hit when this happens, but it's still there).
[Motorola Droid 4] aczlan:
Would joojoobee's kernels help with random ANR messages? For example, Youtube is set to not show notifications, I haven't opened it since July yet I get "Youtube is not responding" errors at least every other day.

When they happen, the display freezes for 30+ seconds until the ANR popup shows up. I have seen them for Calendar, cLock, Sheets, Youtube and a bunch of others.

Aaron Z
[Motorola Droid 4] Jishkah:
Random question, but has anybody else noticed any issues with data hand-off? I've noticed that if I travel (or even drive to work or elsewhere), my phone kind of maintains a "partial" data connection - the phone says 3G, LTE, whatever, but certain apps won't load or refresh. Facebook being one of them, as well as Yik Yak. Typically, I end up needing to switch my phone into Airplane Mode, kill off my recent app list, get out of Airplane Mode, and then re-open the apps; that's usually enough to fix it. Merely killing the app and then opening it without first putting it into Airplane Mode doesn't fix the issue.

I've actually noticed this since the CyanogenMod 11 days. It just has a really hard time maintaining a "complete" data connection when either switching between cellular towers, or data hand-off between 3G and LTE, in general. That's the best way that I can describe it. Certain data functions work, but not all, and it affects a lot of apps.

Has anybody else noticed this?

On an unrelated note, the official Facebook app won't install on any of the nightlies from the last month. :( I get Error -504, whatever that means; it's an unknown error, and so I'm having to use Facebook Lite, as a replacement. Everything else installs, but even installing it from APKMirror doesn't seem to work.
[Motorola Droid 4] welder73:
Regarding FB installation,add this line to your build.prop:

dalvik.vm.dex2oat-flags=--no-watch-dog

I haven't tried that,I just copied from someone's post,try and please report the results :)

Sent from my Razr XT910
[Motorola Droid 4] Jishkah:
Will do. I'm at work right now, but I'll try this when I get home.

Also, as an add-on to my post, the data connection issues are with Verizon Wireless, in case that information was necessary.

UPDATE: I downgraded to CyanogenMod 11. I'm a terrible beta tester. :(
[Motorola Droid 4] Careless_:
shun the non-believer. Heathen!
[Motorola Droid 4] Puppymang:
i experience this all the time and its been there since i started using CM12.1 back in april but never saw anyone mention it here.

best way i can describe it is that anything that uses background internet connections gets stuck trying to connect. this is true for any google apps including remote location search and lock, whatsapp, puush, facebook (i personally dont use this), hell even trying to search by just typing things on the address bar on flashfox gets stuck when trying to pass the search on to google search. the only thing i can do to fix the connection is set airplane mode then re-enable data.

cm11 seemed to have a similar issue but it wasnt from changing towers or changing network type. im not really sure how it happened but i noticed that sometimes apps that connected in the background would take a long time to connect and my only way of getting them to work properly again was rebooting so the issue cm12 has is actually easier to handle in my opinion but still unpleasant
[Motorola Droid 4] Septfox:
Anyone happen to be having issues with their compass/magnetic field sensor not seeming to do compass-like things properly?

I hadn't used mine in a long time, trying to use it today, it's acting kind of like an orientation/tilt sensor (and when level, just points NW regardless of direction).

Wondering if something broke in a past nightly, or if yet another component in my phone has decided to take the easy way out : \
[Motorola Droid 4] Milp:
Sorry if I'm blind, but could anyone point me towards the changelog for the nightlies? thank you.
[Motorola Droid 4] moodroid:
Hi Septfox. I've just tried my compass in CM12.1 (about 2 months out of date) and the compass didn't work. As I've never tried the compass before, and I still have stock in my stock slot, I thought I'd try it there, and it works fine. So, yeah, it looks like something is broken.
[Motorola Droid 4] Septfox:
Ah, good.

I actually do have a stock backup myself, but couldn't get it to to boot up once restored, or I'd have looked myself.

Thanks for checking, appreciate it.
[Motorola Droid 4] aczlan:
http://www.cmxlog.com/12.1/maserati/

Aaron Z
[Motorola Droid 4] joefuf:
Considering upgrading from CM 11 to this as a daily driver. Any feedback on what's still not working and battery life? Should I make the jump?
[Motorola Droid 4] aczlan:
Seeing random soft reboots with the 25 and 26 Aug nightlies (https://jira.cyanogenmod.org/browse/NIGHTLIES-1715). None yet for the 27th nightly (and I am currently installing the nightly from the 28th).

Aaron Z
[Motorola Droid 4] Careless_:
looks like soft reboots are still an issue with aug28 nightly.
[Motorola Droid 4] Jishkah:
It's pretty stable - about as stable as CyanogenMod 11, at this point (in some ways, probably even moreso) - but it can be pretty slow. I've seen some performance increases, enough so that it can be a "daily driver", but you'll need to be careful. It's an older phone, with older hardware, and so you probably won't be able to use it as you would a newer phone - but it's stable enough so that you won't experience any significant bugs. It's quite a bit more fleshed out and robust than CM11, too. I keep finding myself switching back and forth between CM11 and CyanogenMod 12.1, personally, and so I don't think you'll find any significant issues with the ROM.

I'd say go for it. As long as you don't throw too much at it, your phone should be fine.
[Motorola Droid 4] Septfox:
Make a backup first, so there's little to no risk.

Battery life while the screen is off is pretty good. In CM11 (at least, last time I used it) you'd have to go out of your way and dumb down Play Services to fix all the battery-killing wakelocking going on; this isn't the case with Lollipop. You can probably expect around 1%-1.2%/hr on wifi out of the box, down as low as 0.7% if you use things like Amplify and Greenify to help keep the CPU sleeping more. Can't comment on LTE's idle battery drain since I only use it selectively, and screen-on drain is still horrendous (unfortunately there's no software in the world that's going to fix our undersized battery and inefficient screen).

What I've noticed is not working/working improperly:

Compass (magnetic sensor still picks up fields, just doesn't work for directions)

Data handoff/reconnects are fidgety (going from 3g to LTE and vice-versa might require toggling data on/off to get connectivity back; according to another user, this issue was in CM11 too)

Apps/services that write quickly to system "files" might cause hot reboots (Velis Auto-Brightness was killing my phone a few times a day until I figured it out)

External notifications/ringtones (may have been fixed by now, manually dropping audio files into the system folders works as long as permissions are right)

To use CM12 as a daily driver, you'll probably want to increase the minfree limits; Lollipop slows down drastically once the phone reaches 200mb of RAM or so free, and the stock minfree settings let it happen pretty quickly.
[Motorola Droid 4] mo0n_sniper:
I have the same issue, but for me even the phone signal is lost.

For this I have swiched to a Galaxy S4, which is a pitty because I really love the Droid Keyboard :((
[Motorola Droid 4] Jishkah:
Hey. Just to let you know, I'll be installing the 20150906 Nightly, today. I'll go ahead and add that to the build.prop file, and let you know if it fixes anything. I've seen a few other people complain about the same issue, and so I'd like to try to solve it once and for all.

I don't have anything to compare the "patch" to - I don't know if people are having success installing Facebook on the newer Nightlies or not - but we'll see if the build.prop edit fixes anything. Either way, it doesn't seem too dangerous - from what I can tell, doesn't it just get rid of the installation timeout for apps? Facebook is a bulky, complex app, and it's being installed on older hardware... so maybe that's why it throws up the -504 Error message.

Anyway, I'll update this post with the results when I see them.

UPDATE: It worked! See my post a little further down for details.
[Motorola Droid 4] welder73:
I tried that on my Razr and I managed to install FB.

But be prepared,installation last 5-10 minutes and the phone can reboot itself...

Sent from my Razr XT910
[Motorola Droid 4] Jishkah:
That's a scary thought. :x Anyway, I'm glad to see that it worked for you. The Droid RAZR is practically identical to the Droid 4, in terms of hardware, so it'll probably work on my phone, too.

Anyway, after mucking around with a few GApps packages (the "Stock" package hosted on the Open GApps website needs a larger /system/ partition than can be created via SafeStrap; finally ended up using the one linked to on the CyanogenMod GApps Wiki page), I'm finally getting the ROM installed. I'll let you know how it goes. I don't have the device overclocked, either, so here's hoping for the best.
[Motorola Droid 4] will5:
Not sure if it was reported earlier, but if you make a clean install with any of the latest nightlies, there you got no ringtones or notifications sound files to choose. List is empty and default sounds are none.
[Motorola Droid 4] Jishkah:
I don't know what you're talking about; it works for me. :/ Clean install of the 20150906 Nightly gave me the complete list of ringtones, playback and everything. So if it was a problem in prior Nightlies, it seems as if it was fixed, recently.

UPDATE: The build.prop edit worked! Facebook is installed. Thanks a ton for the advice, welder73; what I ended up doing was to add the string to the build.prop file before installing the ROM. Opened the 20150907 Nightly .zip file with 7-Zip, went to the System folder, copied the build.prop file to my desktop, deleted the build.prop file from within the archive, added the new string to the build.prop file on my desktop, and then copied it back over to the archive's system folder. Everything worked without a hitch.

EDIT: Okay, bugs galore. I don't know if it's related to the string that I added to the build.prop file, or if it's just this specific Nightly, but the Cache "section" of my internal storage just ballooned out of control whilst I was installing apps. It usually stays under ~100MB, for the most part, but as the apps were downloading and installing, it reached upwards of ~600MB. Needless to say, I ran out of storage space almost immediately... beyond that, my phone's WiFi crashed. Anyway, I'm rebooting the phone, now - hopefully that'll fix things. I've found Android, in general, to be kind of janky on the first boot after a clean install.
[Motorola Droid 4] will5:
Yes, tried latest build and ringtones are there :)
[Motorola Droid 4] Careless_:
Has anyone experienced issues in any of the nightly builds with the files on an "external" or expansion SD card not being readable?

Sometimes I'll be playing music through bluetooth and it will cut out and starting saying "<song name> is unreadable" or something like that. The album art will disappear and the songs will stop playing.

Not sure if it's my SDcard ****ting the bed, or what.
[Motorola Droid 4] Septfox:
The closest I've had to this is music occasionally cutting out for a moment, as if subject to a CD skip. I always assumed that it was my SD card momentarily losing connection somehow, since the problem doesn't seem to happen with internal storage.

It happened mostly in KK, though. I'd sometimes get as bad as several "skips" in a single song; here in LP, it's a skip every few hours of music. This is all with the same old 16gb card I bought ages ago.

Have you tried taking your SD card out and making sure the metal strip that goes over the contact area is nice and flat? If it's bowed out at all, the card might be intermittently losing contact. Wouldn't hurt to make sure the pads on the card are clean, too.

Beyond that...try with a different card, if the problem persists, it might be time for a new SD card assembly or even motherboard : \
[Motorola Droid 4] Careless_:
Well this is odd.

I installed another SD Card, formatted it within CM12, started putting music on the card.

Went to do something while listening to music, paired to bluetooth device... less than a minute into a song it stops playing- as if it lost bluetooth. but it was still paired. Paired it with another bluetooth speaker, plays for less than a minute, stops playing. Still paired. other device is off- so i know it's not hopping between two bluetooth pairings.

SO i went into recovery. decided to wipe dalvik and wipe cache. Now my phone is stuck in a boot loop. On top of that, I can't get back into recovery because when I get to the dead android image, I do VOL UP+DOWN and it shows up with the blue recovery menu... no SafeBoot.

Not sure what to do now. The phone is just stuck at the Cyanogen Mod boot animation with the blue face.

This blows. :(

UPDATE: I can get into recovery via BP TOOLS on the first VOL UP/DOWN boot menu. Not sure if I should attempt to flash a new nightly over what i gots on there just so I can get in and backup my photos and texts and then reinstall. What a bummerrrrrrrrr.
[Motorola Droid 4] JLPDA:
Running CM12.1 Nightly 09/24 and all is OK. Have tried many times to change minfree values (with Memory Manager, Trickster Mod and others) and it doesn't seem to write these values to the system/etc/init.d/90userinit file. The file is +rw but shows as 00 bytes and empty. Any Droid 4 users running CM12.1 having success tweaking LMK values? FWIW, same whether I run an OC Kernel or not.
[Motorola Droid 4] Shobai:
I've been user TricksterMod, but I'm setting them after every reboot - they don't persist. I haven't looked for a way to make the changes persistent, though, sorry.