yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] Septfox:
First off: MotoDoze (edit: the gesture support specifically) is awesome. Whoever wrote it up and got it working properly is awesome. Since the commit that fixed up the random massive battery drain, it's been working seemingly as intended on my phone, for little to no additional battery drain (current indications on idle drain are 0.7%-1%/hr, which is about what I would expect as "normal" without battery-saving stuff installed/configured). No longer do I have to crack my keyboard open slightly to trigger a slowish screen-on, huzzah.

You should have tried it when it was first brought to our device. "Slow" didn't even begin to describe it. It's also not intended for use in the stock slot/is completely unsupported there, the last time I checked (though there shouldn't be a performance hit or benefit from doing so at this point, and I have it installed there myself). Also,

This.

Our hardware is pretty outdated. Heck, it was getting to be outdated when the phone was released to the public. It's not that the 4460 is a bad package or anything, but I'm not sure it had any business being in what should technically have been a flagship in 2012...

But that aside, as above, it (CM12 on this hardware) really isn't that slow these days. If it's exceptionally slow, then A: you haven't let it settle long enough after flashing the ROM (I would leave it sitting for an hour or so on the charger after flashing everything and booting), or B: there's something wrong.

There are a couple things you can do to speed the phone up a bit over plain CM12/.1, both thanks to [MENTION=1070688]joojoobee666[/MENTION], both easy to do:

Hop on over to joojoobee's kernel thread, and grab at least the "CM12 OC 1.3Ghz Kernel". This will allow the phone to ramp itself to 1.3ghz under load, improving overall performance for a negligible hit to power usage.

If you're feeling adventurous, try one of the 1.4ghz kernels; LV first, and if you have freezes/reboots with that, try HV. If neither work properly, just reflash the 1.3ghz kernel.

If you have a fast SD card, you can flash the latest sdswap zip from here to swap internal and external storage, so the phone will use the SD card as internal storage. The performance benefit will probably be more spotty here, since most apps are small enough they install to the system Data partition instead of int/ext storage. Again, only if you have a fast SD card, don't bother if you're using the little 4gb class4 card the phone shipped with.

Really though, even just enabling 1.3ghz operation helps quite a bit.
[Motorola Droid 4] RawSlugs:
I've had cm11 before this and it was much faster (for the most part) than stock (it was not in stick slot)

I would assume that cm12 would be better and faster than cm11

It is very slow I try opening apps or changing a setting and it takes a long time to go......I guess I'll put it in slot 1 (put it in stock cause I wanted more storage on device)
[Motorola Droid 4] Septfox:
Better, yes, in a lot of ways. Faster...selectively, but overall no, not yet.

Keep in mind CM11 is about as matured as it's going to get by this point, with a solid year of work put into making it run as well as possible. CM12 just rolled out near the end of last year, and while it's already running quite a bit better than it was when the maserati builds started, it's still very much a work in progress.

Give it time. If you really can't get CM12 to run satisfactorily, just revert back to CM11 and check back in a few months; it's still perfectly usable, after all.
[Motorola Droid 4] aczlan:
I have run into that the last few days, 40-50% of the time when I boot, wifi is off and it will not let me turn it on until I reboot.

The other issue I have seen is that when the phone starts up, it will frequently take 3-5 minutes before the cell connection works.

First it will say no sim, then it will either start working, or act like it has an un-provisioned sim for another 2-3 minutes, then finally it will work properly.

Anyone seen anything like this?

Thanks

Aaron Z
[Motorola Droid 4] aczlan:
I found the cause of my issue. There is a metal "cage" that holds the SIM down. Mine was bent up a little and that apparently allowed the SIM to lose contact.

I bent it back down a little and it had service within a minute of booting up.

Aaron Z
[Motorola Droid 4] mcmaxim:
SIM card not being recognised?

Hi guys, I've checked the thread but seems nobody has reported it over the last couple days.

I use Droid4 with Giffgaff network in the UK. Untill about last week (can't remember which CM12 nightly it was exactly I used last it was working) it was ok, recognising my sim card and network, but with one nightly built, can't remember which exactly it was I started to have problems. The Internet connection is working superb, phone calls are ok, I even receive txts but can't send any and I think it's due to my phone saying "no sim card". It also says the network is O2 (which is partly true, cos giffgaff is a MVNO running on O2 network). Have anyone else experienced similar problems recently? If there is a way to fix it - how?

Many thanks in advance for a solution! :)
[Motorola Droid 4] aczlan:
Try popping the back off and pushing down on the SIM to see of that fixes it. If so, bend the sim "cage" down a little bit so it pushes a little harder on the SIM.

Aaron Z
[Motorola Droid 4] moodroid:
I'm on GiffGaff too. Previously, CM12 had been working for me without having to install Mentor's GSM patch. When I updated it a couple of days ago, I lost connectivity and had to install the GSM patch to make it work. Unfortunately, with the GSM patch the signal strength indicator doesn't work properly, but at least you have a signal again.
[Motorola Droid 4] mcmaxim:
aczlan - but my sim card works very well, also with the stock rom, so it's not the hardware fault.

Hmm... well, if you say so - although the only issue is txt messages, cos the network itself works well. Could you please supply me with a link to download the patch you are talking about? Thanks alot!

EDIT: ok, found it, installed, works perfectly well, kudos! Just wondering why did it stop working simply within the CM...
[Motorola Droid 4] will5:
I have the same problem with SIM card. At boot, always says no sim card, after a minute, it goes fine. My simcard is listed as unknown source in stock rom (I have to delete some system files to avoid the message) in case this info will help.

Not a big deal really.

Still can´t fix random reboots. Will try a newer builds, the one Im using is a week old.

BTW, Im using mentor´s gsm patch. Not sure if simcard support is broken on plain cm12.1 newer builds.
[Motorola Droid 4] aczlan:
Running the 21 Jun nightly, I am still seeing "No SIM card" and "No Service" at bootup (have been seeing it for a while). After its been up for 10-15 minutes it will alternate between "Verizon Wireless" and "No Service" (but I can make calls, send/receive texts and use data just fine).

Also, what does the system use to determine if it has internet access?

I am seeing recurring issues where the wireless HAS internet access, it has a strong signal, other devices on the wireless network have internet access, the Razr M sitting next to it has internet access via WiFi but it says "no internet" and has a exclamation mark in the status bar across the top.

Right now (sitting 6' away from the access point), it says "Connected f=2462 ea:xx.xx.xx.xx.xx rssi=-54 score-60 tx=0.0,0.0,0.0 rx=0.0[(1){ea:xx.xx.xx.xx.xx*=2462,-54};] noInt=167 with an exclamation mark in the status bar across the top.

Thanks

Aaron Z
[Motorola Droid 4] will5:
I´d seen the exclamation mark on wifi many times at home, where I have no signal issues at all. Not sure what this means.

Sometimes I get the exclamation on the phone signal bars too.
[Motorola Droid 4] aczlan:
I think I found it, :o I have AFWall running and I think I was blocking whatever is used to check for internet connectivity, I re-enabled a half dozen "systemish" apps and it is happy with the WiFi now.

The catch is that if it cant get to the internet on the WiFi, it tries to use cell data which can burn through data in a hurry.

Aaron Z
[Motorola Droid 4] will5:
Good to know :D

I don´t use any third party app, so not sure why the exclamation mark appears from time to time. Probably inactivity, who knows.
[Motorola Droid 4] aczlan:
I haven't yet seen the exclamation mark show up since I unblocked the apps, but I haven't spent much time in a low signal area either.

Still seeing "No Service" instead of "Verizon Wireless" fairly frequently.

Aaron Z
[Motorola Droid 4] doener:
I have also WIFI problems, the phone dosen't remember the passwords anymore.

Also my phone feels not snappy with lollipop, it often takes a few seconds before it opens apps or generally reacts. Has someone the same issues?

I installed it in the stock slot a while ago.

Maybe it is time to make a clean installation, since im upgrading infrequently from nightly to nightly.

I see that the cyanogenmod continuously increases the rom size, while it gets slower and slower... however, its nice to have Lollipop!
[Motorola Droid 4] aczlan:
I had mine installed in slot 1 and it was doing that, but it was almost out of space.

I deleted slot 1, remade it with more space and re-installed and it is noticeably faster.

Aaron Z
[Motorola Droid 4] Shani Ace:
Wow, thanks so much for that! I wasn't looking for more performance, but for more storage, because the internal storage is too small and most of all, I always hated the internal storage! Back in the days when every smartphone had a (mini-, micro-)SD slot, there was no internal storage. I never got why I was forced to use that ****ty one when I have a fast microSDXC in my phone. :)

Now I can install games bigger than 1GB (like Batman Dark Knight and Injustice, never tried them before) on the phone. I probably won't play much, but still it's great to have the opportunity. Also the Camera App saves the files on the SD card, not the internal storage, which always annoyed me. And finally Comicreader.mobi finds my comic folder directly, whereas before I always had to open them with ES Explorer. Nice!

When I found out that I could swap internal and external storage, I only found some threads where it said I had to upload a system file and wait for it to be edited. But flashing this zip is so much simpler! Thanks again and hopefully other people will find your post, too, when they're looking for the same solution.
[Motorola Droid 4] joojoobee666:
I always felt the same way. Never understood why internal storage was given the keys to the kingdom while the massive 32GB, 64GB or 128GB SDcards sat there, basically ignored. That's why I made the zip install. I've been doing that hack since CM9.x. Essentially, the day I procured the D4. Glad I could help. :good:
[Motorola Droid 4] Shani Ace:
Ah, so it was you, I wasn't aware of that. Thanks. :) I wish had found this earlier, about a few years ago. ^^
[Motorola Droid 4] ary_evo:
Working very nice.. [emoji2]
[Motorola Droid 4] Septfox:
Woops, yea. Didn't mean to take credit for it or anything, I wouldn't even know where to start for making this sort of thing.

If you're not using one already, make sure you hop over to the kernel thread and grab one of his modded kernels, even going to 1.3ghz helps quite a bit.
[Motorola Droid 4] mcmaxim:
Guys... The exclamation mark appears when there is some sort of Internet connection available, but your phone can'connect to the Internet. For example: you turn on the WiFi module, but dot connect to any WiFi network OR you connect to a WiFi network, but the network itself is not connected to the Internet. The same with an exclamation mark on the mobile network: because your phone knows there is a gprs/hdspa/whatever connection available, but you do not let it use mobile data - it only then disappears when you connect to the WiFi network.
[Motorola Droid 4] aczlan:
In my case, it was showing up on WiFi, but the WiFi network HAD a good internet connection. It may have been due to the "Phone/Messaging Storage, Messaging service, SIM toolkit, Phone" service being silently blocked by AFWall+ (ie: it was blocking it but nothing showed up in the logs saying that it was trying to use the internet).

Aaron Z
[Motorola Droid 4] Careless_:
so any news on the latest nightly?

how's it running?
[Motorola Droid 4] aczlan:
The one from July 5th? Working fairly well on my phone. Might be a little slow, but not worse than the last one I had installed (25 Jun).

Wifi is prone to say it has a poor connection when it should be fine and the camera sometimes freezes, but everything else works (BT, 4G, 3G, calls, texts, MMS (with another app, not the built in one)) and those issues I am seeing might be due to something else I have installed.

Aaron Z
[Motorola Droid 4] hearkenoath:
I always mount /system an /data after make a slot and flash anything. It works wonders with the CM nightlies but not with the snapshots
[Motorola Droid 4] Careless_:
I'm not sure if this would help shed more light on your discovery as far as available memory, but have you tried limiting running apps using the developer options just to see what might happen?

I get the same slow-down issues- but it's still way faster than the Desire Z that I was "OK" with for a long time, so while it doesn't bother me as much- I know how you feel!
[Motorola Droid 4] rblanca:
finally! http://review.cyanogenmod.org/#/c/102499/ ...it's going to be on next daily!..lets hope it helps!. Thanks!
[Motorola Droid 4] Septfox:
I probably could have made my post a bit less...texty, I guess. It actually took me a moment to find what I wanted to quote...

But yea, low-end devices, right? My previous (and first actually) android device was an LG Ally. 600mhz single-core (overclocked to 787mhz), 112mb of RAM, 2.2.2 Froyo...I had to use it again for a month after I bricked my D4, and even when it was running its fastest, the difference in performance was rather stark. Not to mention practically all modern apps run on 2.3+, so there was a distinct lack of utility...

Saw that after posting. A little excited, wondering what the CPU impact will be like.
[Motorola Droid 4] joojoobee666:
Some changes in the device tree and kernel warrant a new SDSwap for tonight's upcoming Nightly (07-08). This is required if you want SDSwap and/or XPrivacy. If you don't want SD cards swapped or use XPrivacy, 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.

07-08 D4 SDSwap with XPrivacy support

07-08 D4 XPrivacy support (No swap)
[Motorola Droid 4] Septfox:
Another long post! This one clearer! Hopefully! Sentence fragments!

Installed the latest nightly. The zram addition...doesn't seem to have really helped the memory problem. If anything, it might be slightly slower now once it starts running low.

It does take a bit more effort to run it out, but once it's there, it's pretty persistent.

I was somehow under the impression that unlike in previous versions, Lollipop's minfree settings were baked in and couldn't be readily changed. I've since educated myself slightly more and tried screwing around a bit. Started out with large increases over stock, just to see what would happen.

Setting "Empty App" (completely exited apps) to 200 and "Hidden App" (background processes) to 160 seems to keep memory floating in the 200-250mb free range. It still hit just below 200 occasionally, but despite that, could probably be backed off a bit. The speed wasn't amazing when it started needing to kill things (I would guess because the lowmem killer itself is fairly intensive and/or apps being killed take a moment to save their state), but still faster than running low under normal settings...

I left all the other minfree settings at defaults. "Empty Apps" could probably be left alone too, since memory "used" by things in this category is technically reclaimable at any time (if I understand right)...but it seems to me that it would be faster to flush stuff beforehand rather than right when it's needed.

Setting the Background Process Limit low alone still results in more speed, since its killing is done way, way in advance rather than on the spot with the lowmem killer, but just messing with minfree potentially keeps the most multitasking capability. Maybe. *shrugs*

Anyway.

At the moment, I'm trying the "best" of both worlds:

Settings>Development>Background process limit: 4

minfree "Empty App" at 200

minfree "Hidden App" at 160.

My reasoning: the background process limit tries to keep too much unused crap from piling up in the background and hitting the minfree settings, and if some of said unused crap happens to be particularly heavy crap (*coughFirefoxcough*), the lowmem killer will kick in and clean up, hopefully preventing free memory from hitting the danger mark.

Seems to run pretty well, for a bandaid approach. Might drop the process limit to 3, just to keep the free memory as high as possible, but it seems to be doing a good enough job as-is.
[Motorola Droid 4] welder73:
Try this minfree values,you'll see the difference ;)

Sent from my Razr XT910
[Motorola Droid 4] Septfox:
That seems mighty aggressive for server and content provider. It seems to me like active stuff under both would end up being killed while still needed, using further resources to pull themselves back up...

Still, I like me some experimentation, and will give them a try.
[Motorola Droid 4] will5:
Guys, there is a patch to solve gsm or 3g signal bars not showing?

Id installed mentor gsm patch but I lose data with this patch.

thanks
[Motorola Droid 4] Careless_:
for some reason, I had no issue with screen wake for a while- now it's starting to happen again.

blank screen on incoming calls. have to wait like 7 or 8 seconds before I can even see who's calling.
[Motorola Droid 4] aczlan:
I see that occasionally, usually when Firefox, Google Now and a half dozen other apps are open in the background.

Aaron Z
[Motorola Droid 4] Jishkah:
Yep. Google Now is fine, but Firefox slaughters my phone's performance. Google Maps can be pretty killer, too.

For the most part, CyanogenMod 12.1 is fine. It's stable. For me, anyway, as long as I don't perform dirty flashes of Nightlies. At this point in time, it's the memory management that needs adjusting - specifically, the "re-shuffling" necessary resources on-the-fly that Septfox mentioned (btw, I totally found you on the Android Forums in the LG Ally section when I was looking for the old Stormdroid ROM, a few weeks ago - small world). I definitely notice a massive performance decrease if my phone hasn't been rebooted in more than a day, and I feel like it has something to do with the background processes/tasks not really being shuffled around in memory the right way to utilize resources when they need to be utilized - especially if I haven't cleared out my Recent Tasks list for a while.
[Motorola Droid 4] aczlan:
Anyone seeing bluetooth issues with builds after 14 Jul? On my phone, Bluetooth works normally on the 14 Jul build , but when I dirty flash the ones after that (I have tried the 16th, 17th, 18th and 19th), its like the Bluetooth radio is not there. I get frequent "Bluetooth Sharing has crashed" messages and if I try to turn on Bluetooth from settings, settings crashes.

If I dirty flash back to the build from the 14th, Bluetooth starts working right away.

I have not yet tried a clean flash or the build from the 15th, thought I would check on here first.

Thanks

Aaron Z
[Motorola Droid 4] Septfox:
I suspect Firefox of shenanigans, actually.

Even under aggressive minfree settings and low memory, the phone will still sometimes try and keep Firefox in memory for several extra seconds before finally dropping it (sudden huge raise in available memory). It's weird, and doesn't seem to happen with the other "heavy" apps I have.

As far as the general problems, it's as if the low-mem killer...I don't know, isn't considering most apps in memory to be "old" enough, and refuses to kill them until things become critical. In turn keeping everything, and completely choking the phone out.

Even worse, bigger apps aren't given any sort of priority, so you can sit there for a few minutes trying to launch the Dialer with ~170mb of free memory, watching it jump up and down wholly-inadequate 5-10mb chunks at a time as little things in the background get killed off while a couple elephant-sized apps sit in the corner having a spot of tea. It's a bit infuriating, really.

If you guys haven't, try flashing one of joojoobee's kernels, he's added a couple hundred kernel patches lately (mostly for the memory manager). The net effect, as of the one built on the 12th (haven't upgraded yet), is that the phone doesn't choke as badly when it hits and goes under 200mb (it's not any better at killing stuff off, it simply doesn't shudder to a complete halt).

I imagine that many of these patches will be merged into the CM12 kernel at some point., but for now, they're only in his.

Despite the above and especially with the stock kernel, messing with minfree is still very much worth it. "Empty App" at 210 and "Hidden App" at 170 keep the phone happier.

For even more consistently good performance at the cost of some multitasking, Settings>Development>Background process limit: 4

Last, you may want to turn zRAM off. For the moment, it doesn't seem to help the memory situation and slows the phone down. Many "kernel tweaker" apps can do this, Trickster being one of them and probably the most well-known.

-

Ah, the LG Ally, my first foray into anything Android. I'm still using it as a backup phone, infact my service is currently on it; Tracfone is having trouble transferring the service to my D4. A dinosaur as far as smartphones go, but solid and reliable and still works really great as a phone <3
[Motorola Droid 4] Goodevil95:
In stock OTG work good. But in CM 12.1 OTG not work. How to fix this problem?

Sorry for bad english
[Motorola Droid 4] dreikk91:
on cm12.1 phone do not records video with flash
[Motorola Droid 4] keaft:
Preferred Network

Running: cm-12.1-20150719-Nightly-maserati

Provider: Page Plus

I found that I could not get mms. Mms has always been off and on as I've updated CM. This time it was particularly interesting.

Generally I will go through the steps to get mms functional again by checking connectivity, checking the preferred network settings, checking apn settings, and physically moving to a different location.

I know there have been several updates to the mms system as noted in the change logs. When I go into my preferred network settings it does not stick with the option selected. It instead will show a different setting altogether on the settings page up one level. When I go back into the list to pick the correct option, the option is already selected from prior, but still doesn't indicate so after hitting ok.

I'll take pics if needed. Heck I don't even know if this is the best place to post bugs.
[Motorola Droid 4] joojoobee666:
We found and resolved some issues on VZW regarding MMS that will be on the upcoming nightly tonight. This may fix your as well seeing PagePlus is basically resold VZW.
[Motorola Droid 4] aczlan:
Will this help the "cant send/receive MMS messages when wifi is connected" issue (tries to send/receive MMS messages via wifi if its available and VZW does not allow that)?

Aaron Z
[Motorola Droid 4] joojoobee666:
I was able to send an MMS with Wifi enabled and connected just now. :good:
[Motorola Droid 4] aczlan:
Looking forward to testing it!

Of note, in the build from the 24th, 26th or the 27th, the erroneous "bad wifi connection" bug seems to have been fixed (I would get the exclamation mark saying that the wifi connection was bad when standing 6 feet away from the WAP if cell data was on, but if I turned cell data off, it usually reconsidered and decided that the wifi connection was ok after all).

Thanks

Aaron Z
[Motorola Droid 4] joojoobee666:
There is still an issue with the icon, presumably an overlay problem as mine showed "!" but was working fine (data shut itself off). Not sure how long it's been like that, however. I never use it :P.