yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] joefuf:
I brought the phone to work and tried my luck on the WiFi network there. It looks as though I experienced the same issues with wakelocks.

[IMG="d"]http://i.imgur.com/9qWDuZt.png[/IMG]

I might have turned my screen on twice all day and for whatever reason, the thing kept waking itself up.

The rest of my screenshots are in an Imgur album here.

I'll give it a try just on standby today, no WiFi.

I'm on CM11 as well. I've got a build from April 26, 2015 that has worked for me just fine and given me no reason to flash anything new. I typically get 4 hours out of pretty heavy usage before I need a charge, and that usually works for me. While it does take quite some time for apps to open occasionally (Untappd takes like ~18 seconds), the reviews from some people in this thread about how the more you install, the worse the ROM gets keep me away. I don't consistently get days where I would have the ~4 hours I need to flash a new ROM, restore all of my texts, and set up all of my apps (although the "Copy accounts" feature in CM13 might take several steps out of the process) so I don't know that I would be able to keep up with the maintenance the ROM on this phone sounds like it requires just yet. I'm sure I will eventually, maybe once I can prove to myself the battery life can last as long as I need it to/nail down this WiFi issue I'm having on my backup phone.
[Motorola Droid 4] stargo:
Hi,

Yes, heavy broadcast-traffic will keep the device awake. It's especially bad on networks with many devices (like work-networks and stuff like eduroam).

But your sudden big drops are an indication of a bad battery, you should think about replacing it. It's not hard, you just need a Torx T5(i think) driver to unscrew the battery terminals (before pulling on the old battery!).

Hmm, updating while staying on the same ROM "generation" (as in CM13 nightly -> CM13 nightly) only involves falshing the new ROM and waiting for it to be "optimized". All your data and settings will survive that (if you not manually wipe).

Cheers,

Michael
[Motorola Droid 4] joefuf:
I can't imagine a time I wouldn't be on WiFi that's gonna be full of traffic. If I'm at home, there's at least three or four devices (be it Rokus, computers, or other smartphones) on the connection. At work, it's anyone's guess how many things are connected. Is there really nothing I could do to aid my phone?

I guess that could be the case. The batteries probably stretch as far back as when the phone was last originally manufactured in 2012, so I guess four years on a Lithium-Ion battery will take its toll. I did look at some YouTube videos on how to replace the battery and it doesn't look too complicated. The linchpin seems to be on finding a good battery, as Amazon reviews point out the battery was either a great improvement, the same, or DOA. Not bad for a $10 investment if it works, I suppose.

I've always done clean installs whenever flashing ROMS. As a result, I've never had an issue after flashing your ROM. The only downside is the aforementioned ~4 hours it takes, mostly due to me meticulously backing up 75k texts over the last six years. Restoring those used to take me the longest. I saw CM13/Marshmallow now has the feature where you can use Bluetooth between an old and new device during setup which got all of my accounts, WiFi networks, and Android settings moved over effortlessly, so that would probably save me time.

I'll consider the battery replacement and see what that does for me on that ROM. There were a few other things I wanted to iron out. I found a way to remamp the physical keyboard to match what I was used to from my Droid 3, but that same file which worked in CM11 no longer works in CM13.
[Motorola Droid 4] martin9959:
Great, that solved all of my voip audio problems, thanks a million Michael!! Even the problem I had with the proximity sensor is gone with today's nightly, maybe by some other change? Anyway, you made my day! :o
[Motorola Droid 4] Careless_:
what do i do with this information? how do i add this fix?
[Motorola Droid 4] martin9959:
just use the latest nightly (i.e. cm-13.0-20160410-NIGHTLY-maserati), that's what I did. It includes the fix mentioned by Michael (see here: https://www.cmxlog.com/13/maserati/)
[Motorola Droid 4] Careless_:
HMMMMMM.

I've been having an issue with sdcard storage on the nightly I'm running (01/25)... I will see about running the new version. perhaps it fixes both.

It's not allowing me to use my 32gb SD card as storage, it doesn't put photos on it, and does not make use of it whatsoever.
[Motorola Droid 4] joefuf:
Do you have Xposed at all? I was having that issue back in KitKat so I got Pictures2SD and that's been all I need.
[Motorola Droid 4] M_w_B:
I have tried cm-13.0-20160317-SNAPSHOT-ZNH0EAO1RL eversince the day I got the phone. It crashed mid-day while uploading a video, and got stuck into a bootloop. I don't want any of that mess so I got back to the most stable version 10.2.1 at the download pages. It works fast, but the camera sucks and photos/videos are VERY important to me. I also have to do a lot of tweaking in Xposed to make the statusbar and drawer transparant. This ROM also crashed mid-day, this time while using camera.

The camera sucking too much on 10.2.1 makes me want to switch to CM 11, since CM 13 appears too slow on the Droid 4 (so far).

Am I doing the right thing choosing cm 11 over cm 10.2.1 or will i loose a lot of performance? The camera on cm 13 was a lot better than 10.2.1, what can I expect from the camera on cm 11?

EDIT: ok, so the camera is the same on CM 11 latest snapshot, I have no idea at what frame rate I am filming and I am missing some options
[Motorola Droid 4] Jishkah:
Is there a changelog available for today's Snapshot? The one available in the CyanogenMod Updater seems to think that this is the first Snapshot for my phone, so it won't offer me any information about what's changed between versions.

So far, the only thing that I've found different is that the cLock widget is finally able to access my location for the weather feature, and there are a few new settings pertaining to validity and read/send reports in the Messaging app. Haven't really dove too far into the ROM, but so far it looks to be working just fine, after performing a dirty flash on top of the old Snapshot and wiping Cache/Dalvik.

EDIT: Bluetooth still doesn't work properly. :( I don't know if it's just my Bluetooth receiver or what, but my phone can't seem to remember it after I disconnect from it. Is there any way for me to generate a log file of some sort regarding this bug that might help, or to file a bug report?
[Motorola Droid 4] Careless_:
I'll give that a shot. Is there anything to installing xposed framework? Some steps so that I don't mess it up?
[Motorola Droid 4] joefuf:
It's pretty straightforward. Installed the XPosed apk, install the framework within that, reboot, find the modules that you want to install, make sure they're enabled within XPosed, reboot, and you're good to go.
[Motorola Droid 4] Careless_:
Would using the SD Swap joojoobee do the same thing?
[Motorola Droid 4] Careless_:
04/21 nightly breaks bluetooth connectivity.

I could not connect to a device I'm always able to, nor could I "forget" the device to reattempt connecting or establishing a new bluetooth pairing.

EDIT: no connectivity other then cellphone data seems to be operating correctly. Clicking on a Wifi Connection just says "Obtaining IP Address" and then reverts back to SAVED status, but it is connected. Though the icon does not update the signal status.

And Bluetooth does not connect at all. Wondering if this is a joojoobee kernel issue or the latest CM13
[Motorola Droid 4] stargo:
Hi,

It should only contain security-fixes, no other bug-fixes or new features.

Hmm, maybe there are actually a few bug-fixes in the base-tree then. Not sure if this was intentional or just pushed to the wrong stable tree...

Cheers,

Michael
[Motorola Droid 4] Careless_:
can someone confirm they also have bluetooth connection issues on the 4/21 nightly? I can't seem to get it to connect to my computer or my bluetooth speaker. was fine on the January 25 release I was running.
[Motorola Droid 4] Jishkah:
Yeah, I spoke too soon. The cLock widget is still acting buggy. Doesn't seem to want to update with the weather information, and when it does by some miracle, it doesn't seem to want to refresh itself afterwards. I remember having weather information on the widget from five days in the past from a different city, lol. Using different weather sources or resetting the app's data doesn't seem to fix anything, either, and it has all of its permissions, so idk what's going on. Might just be an issue on the CyanogenMod side, not device-specific, since I've looked into it a bit and I've seen similar complaints within the last few months.

Otherwise, the SMS/MMS app is the only thing that I've seen "different" so far, and that's only in the Settings menu with the added options to choose from.
[Motorola Droid 4] wsemi:
I took the LockClock.apk from a recent nightly, because it shows the humidity level and wind speed as well. It's working fine for me - I'm using the OpenWeatherMap provider.
[Motorola Droid 4] Careless_:
I got bluetooth to work on a different speaker today, so I tried to "forget" the bluetooth that wasn't connecting and will be trying that again.

I found a new bug in the 04/21 nightly.

when receiving a second call while on a current call, the END CURRENT CALL action will cause the phone to start. It's happened to me twice now.

- On Current Call

- Second call Incoming

- Press "END CURRENT CALL"

= phone reboots.
[Motorola Droid 4] Careless_:
Definite issue with Bluetooth.

Will not connect to some devices that it used to. My brother's samsung galaxy s6 edge connects to them fine.

I used to connect to this little bluetooth speaker every day, and now it will not connect. It says "Unable to communicate with <devicename>".

What has changed regarding bluetooth in the last month or so?

This is driving me crazy, I need tunes @ work.
[Motorola Droid 4] wsemi:
As I saw previously on cmxlog, 20160421 nightly contained some major changes - like update to 6.0.1_r30, and lot of commits with "do not merge..." titles. Many of those were BT related change.

If there are issues with BT currently, maybe it would worth to try a version before 0421.
[Motorola Droid 4] Careless_:
damnit. now i have to reflash this device all over again and install all the apps and all that jazz.

:(

thanks for pointing the cmxlog thing out, ill try the 4/18 snapshot.
[Motorola Droid 4] wsemi:
Before reinstall everything, you can try to dirty flash it first.

Usually it works, or if some process keeps stopping after upgrade/downgrade, it's enough to clear its data, not for every app.
[Motorola Droid 4] Careless_:
i tried. it keeps telling me android.process.acore keeps closing.

i'm just going to back-up and go to 4/18 snapshot.

i tried 4/27 and the bluetooth pairing still doesn't work.

it's actually quite odd, i've had one bluetooth device pair fine, this particular speaker however... it will flash the bluetooth LED until i click its name in my bluetooth pairings, and it will then stop flashing and stay solid (usually indicates its connected). they only difference is that the phone does not state that it's connected, and playing music does not play through the device.

lastly, this particular speaker says "BLUETOOTH PAIRED" when its connected, through the speaker in a male voice. Even when the LED goes solid and stops flashing, it does not say that- which means it is not paired completely.

I wonder if Bluetooth 2.0 connectivity was dropped in that cmxlog reference you quoted. The other device I connected to might be bluetooth 4.0 or something.

EDIT: 4/18 SNAPSHOT no bluetooth issues. paired with same speaker as before, so now I can go to work with some tunes again.

Thanks for the tip wsemi. Seems like anything after 4/21 might have issues. I didn't want to try 4/20 so I went with the latest snapshot.

Now... does snapshot mean its the latest "stable" milestone release, or the closest we have to most errors being minor or even fixed completely?
[Motorola Droid 4] stargo:
Hi,

Yes, happens on other devices, too. Cause currently unknown. It seems to work if you enable bt tethering before pairing, which is very strange.

No, 2.0 was not dropped (intentionally), but maybe something broke it.

But then you still have the audio-wrapper locking issue. What you could try is taking /system/lib/hw/audio.maserati.so from a current nightly and replacing the file in the snapshot-release. Then you should have a fixed audio-wrapper and working bluetooth (hopefully).

Cheers,

Michael
[Motorola Droid 4] wsemi:
As I understand, snapshots are made from a "stable" branch which contains only selected commits. So it's behind nightly and does not include so much new features. In addition snapshot is still on android-6.0.1_r17 while nightly is on r30.

I went back to snapshot as well, because had various issues with the nightlies. Snapshot is not perfect either but I have much less issues with it.
[Motorola Droid 4] Shani Ace:
I just went back and read the last 5 pages of this thread, despite the advice to stay on CM11, updating to Marshmallow is still tempting. I mean, my D4 is still doing fine on CM11, I can actually use my browser (Opera) without the phone freezing (on CM12, it always froze when I opened Opera). But Miitomo on the other hand takes an awful long time to load and when the app's running and the phone goes to sleep, the lock screen freezes when you try to unlock it. The only way to circumvent that is: while in the lock screen, going into the notification bar, then opening the system settings and pressing home.

The funny thing is that accessing the notification bar shouldn't be possible in lock screen (swipe method), but it is. I suspect this as the cause of a few strange incidents that I had. BTW: Does anybody know whether the lockscreen was improved in A6.0/CM13? Whenever there gets sweat on the phone's display while it's in my pant's pocket (e.g. when dancing in a club), it randomly unlocks and writes texts, notes etc. all by itself. Once it even deleted all my contacts from A to F (but not once did it pocket dial).

Anyone else here using Opera and/or Miitomo on the D4? I know freezes are often app-based, but the case of CM11 vs. CM12 and Opera shows me that it can actually be OS-based. So if A6.0/CM13 has any improvement that would make these two apps run (or run more smoothly), it would be an incentive for me to update to CM13.

Well there's the Blackberry Priv, of course, but you can't flash custom ROMs on it. Another option is the Galaxy S6 Edge Plus, because you can buy a neat official QWERTY case for it (the screen size adjusts when you put it on, I don't mind the smaller screen, still bigger than the D4 ^^). I'll probably switch to one of these devices soon. Probably the Priv, because it's a little smaller, has an microSD slot, the bigger battery. The S6 Edge+ on the other hand is lighter, has custom ROMs, OTG, slightly better hardware, but it would have to be the 64GB version for me (32GB is not enough), which is more expensive. On the downside, the S6 Edge Plus has a fingerprint sensor, Heart Rate Monitor and Barometer, all of which are completely useless for me but pose an invasion of privacy.

I took the comparison data from here, btw.
[Motorola Droid 4] Careless_:
Hi Michael,

I came to post that i was having the intermittent audio issue as I was at work using the speaker today- though it did connect to BT flawlessly. All was going well until the music stopped. Had to restart my device a number of times. Got really fed up- but it was near the end of my day so I just toughed it out. hahaha. I normally don't get so aggravated with free custom software to extend the life of my device- but I work alone now, so I need audio company!

I just transfered the 04/27 audio.primary.maserati.so to my current install like you suggested regarding the audio-wrapper issue, and I will report back. Hopefully it doesn't break again! I'm going to transfer the other audio.primary files just in case I need to inject those too, but I'll leave them on my SDCard for now.

---------- Post added at 12:39 AM ---------- Previous post was at 12:36 AM ----------

I was looking at the Priv, never saw the S6 Edge Plus addon. That is pretty... ummm.. interesting- but not my thing.

I think I'll stick with the D4 for now. If I can fix this audio issue it'll be all I need. I enjoy this device ALMOST as much as I enjoyed my Desire Z :)
[Motorola Droid 4] Shani Ace:
Yeah I just discovered the addon recently, and since the Priv's keyboard didn't convince me during a hands-on-test, I ordered the keyboard case for the S6 edge+ for only 6,85€ (Amazon Warehouse Deals) to try it out without the device itself. The Samsung is also cheaper (at least with 32GB, maybe I'll have to settle with that) than the Priv, I'm seriously considering it again. :D

Honestly, I feel a bit left behind with my D4. It's usable, but it's still dragging...

But the thing is, I think I like the D4's keyboard better, with five rows and really comfortable keys. Think I'll try out MM on my D4 first before I order anything. ^^

Uh I just discovered that the keyboard case effectively disables the fingerprint sensor of the S6 edge+. :D

I also like that it provides you with 3 hardware buttons (like back in the days), I never was too fond of softkeys. I also won't need longpressing the home button to alttab between apps. And hopefully it gives that huge phone a better balance when there is a bit more weight at the bottom.

But the keyboard is not backlit (the Priv's is), hm...
[Motorola Droid 4] Careless_:
The newer phones are simply too large for me to use comfortably. My bro has an S6 Edge... I don't know if I could deal with an addon ontop of that, it's slightly larger than I would want already. a D4 sized phone with less bezel, maybe 10mm wider, and a little thinner is all we needs. Snapdragon 820 would be appreciated too.

But we digress. Back to CM13 stuffs!
[Motorola Droid 4] Careless_:
Transferring the audio files didn't help. It made the audio not work at all, and neither does my dialer now. Going to attempt to transfer the other files as well and see what happens.

EDIT:

went back to the 4/18 audio files. I tried all the latest audio files in sys/lib/hw and it didnt fix anything, so I reverted back and its working again.

going to attempt to dirty flash an in-between nightly now

EDIT 2:

Are they purging nightlies older than 5 days? I can't find anything before the 25th.

I wanted to try something around the 10th to see if I can retain bluetooth function and remove the audio stutter issue...
[Motorola Droid 4] u.b.o.o.t:
I'm having a severe battery drain issue with snapshot cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NI-maserati (which is the first custom rom I try on my "new" Droid 4).

The phone never sleeps. According to BetterBatteryStats, a kernel wakelock is keeping it awake all the time: MAPAL_LITE_SOCKET_RECEIVE.

I traced this back to some radio-related library called libmoto_lte_ril.so. Seems to be a closed-source lib - correct me if I'm wrong.

My phone is running on GSM or WCDMA aka UMTS (provider: Eplus or O2). Different radio modes "GSM only" or "GSM/WCDMA auto", etc. do not make a difference.

This issue wasn't present from the beginning, but it started somewhen and never went back to normal since. Did several reboots and tried many things like freezing apps, playing with radio network settings, etc - without success.

And I'm absolutely stuck here. Any help is greatly appreciated.

EDIT: It's gone!

Installing Mentor.37's GSM patch did the trick for me: http://xdaforums.com/showthread.php?t=2394689

I thought this was not necessary because CM13 was reported to fully support GSM/UMTS on its own, but seemingly there is still missing something, e.g. build.prop settings.
[Motorola Droid 4] joefuf:
Hey [MENTION=3457922]stargo[/MENTION], do you have any idea where I might start for this? I've been messing around with the files from 4.4.4 that used to work:

\system\usr\keychars\omap4-keypad.kcm

and

\system\usr\keylayout\omap4-keypad.kl

But they don't seem to affect the Caps Lock and Shift key nor add any of the symbols to the other hard keys with the ALT function. Do you have any idea if ALT is no longer a functioning code in Marshmallow?

EDIT: Figured it out. It looks like Marshmallow references some of the other files related to the keyboard beyond those two.

I edited the Generic.kcm, qwerty.kl, and Generic.kl files which also required that I reassign the Caps Lock key (Key 222) and Shift Key (Key 42).

Then I had the same issue that I had when I tried this back in January where the emoji keyboard popped out when I hit the ALT key, now the Shift Key. All I had to do was disable that feature in Advanced and I was good to go.

The working file is attached.
[Motorola Droid 4] u.b.o.o.t:
[MENTION=2679469]joefuf[/MENTION]: I mapped Capslock to Ctrl and Sym to Alt -> works fine, see attachment. I did not have to modify the non-omap4-files.

Which snapshot/nightly are you using?
[Motorola Droid 4] Careless_:
Can anyone confirm the bluetooth issues are fixed in the latest CM Nightly + Audio stutter is not back?

I can't download a version between the audio-stutter and the 4/21 version that had the bluetooth connection problems so I'm stuck with one or the other right meow.
[Motorola Droid 4] joefuf:
I think it's a CM13 from March. I might have done the same as you and had it working back in January, but I think I forgot and flashed over that ROM. I only have CM13 on my backup phone.

I haven't had any audio issues, but I have only played a handful of things. I don't have any bluetooth devices to test bluetooth.
[Motorola Droid 4] dicer42:
I had the exact same issue. Triggered by AFWall+. See bug report here: https://github.com/ukanth/afwall/issues/525

I also installed the path and no more constant wake locks!

So there is definitely something wrong with enabling the GSM mode in cm13 and unfortunately it is not yet available without mentors patch.

I also have massive problems with 3G: Most of the time I can not transfer data or the connection drops completely (not just data, also no more calls). Sometimes it is so bad that the connection drops every 10 seconds or so. Weirdly enough switching to 2G only gets everything stable. But of course very sloooow.

This was working just fine on cm11 in the same locations. The phone was acting up though and my front camera failed. So maybe the 3G instability is just me and my failing mainboard. Or does anyone else see this as well?
[Motorola Droid 4] u.b.o.o.t:
[MENTION=1532859]dicer42[/MENTION]: I haven't seen any data transfer issues with 3G (@ O2, Eplus) with 16/04/18-Snapshot yet. But I don't use data connection permanently. I just activate it to e.g. check my emails and then disconnect.

The only issue I have with mobile data: it cannot be enabled / disabled with Tasker, nor with Secure Settings plugin, which is a pity because I'm doing much automation with Tasker...

And: wifi connection may drop after a while.
[Motorola Droid 4] stargo:
Arghs, AFWall! This breaks the whole modem subsystem completely. And the GSM patch just breaks it a little bit less.

I've just added this to the bug-report:

The LTE modem on the Droid4/Razr/Bionic is a network device with the IP 192.168.157.2. If the system can't communicate with it, this will cause the wakelock. Do not block access to 192.168.157.2!

Installing the GSM patch removes the network device from android and uses a different RIL to access the remaining GSM/CDMA modem. This will also cause some (other) failures, as the LTE modem is not only responsible for LTE but some SIM card management stuff.

Best regards,

Michael
[Motorola Droid 4] Careless_:
how do i download previous nightlies? i can't see anything passed like 5 days.