yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] bofis:
sigh...running your unofficial 1/21 nightly today and had while plugged in and charging (it's been plugged in for about an hour) it stopped responding around when it reached the "charged" state. I had woken up the phone a few times while it was charging, checked email, etc. Last time I did that was a few minutes ago when it was at like 93%. But without anything else happening, no notifications or anything, I tried to wake the phone and it did not respond at all. Nothing lit up, not even the soft keys. I had to hold the power button until it rebooted. :( Sadly I'm not sure what is causing this, but I flashed 1/21 last night as I was going to bed and it charged overnight without issue, and worked all day until just now.

Also having issues keeping a data connection...it'll drop out and seemingly forget what kind of network it wants to connect to. Under Mobile Networks in settings it won't list what it's presently on, and toggling it to LTE-only and back to CDMA+LTE/EVDO doesn't always effectively switch the mode back or restore service without rebooting. I'm fixing permissions now, but can it be set to CDMA+LTE/EVDO as the default when updating/installing the rom?
[Motorola Droid 4] Shobai:
suspend_backoff

I'm still having trouble with the suspend_backoff wakelock, which seems to sometimes crop up after I unplug from charging and other times somehow in relation to using WiFi. Without the wakelock I can get well over a day out of the phone, but with the wakelock it is flat, from fully charge, inside 10hrs with screen on time under an hour =/

Aside from rebooting my phone after charging or using WiFi, is there anything more proactive I can be doing?
[Motorola Droid 4] Krooked247:
Having the same connection issues here as well on 1/21/14 nightly.

Krooked All Day....
[Motorola Droid 4] stargo:
And I had really hoped I got that one :(

If this happens to you again and you have access to a pc at that time, can you please run "adb shell dmesg >logfile.txt" and send me the log?

I really want to get that fixed but need to see what's going wrong.

Hmm, has that changed recently? If so, it was introduced by an upstream CM-change which I need to identify then...

I don't think that fixing permissions will solve this.

If you are feeling adventurous, you could put the phone in fastboot-mode and flash the modem.bin from the cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip update, which will clear all settings in the modem. This at least helps if you select the wrong GSM-band, so it might help here, too...

Hmm, another one I had hoped to have fixed. But the suspend_wakelock could be caused by another issue and not only the HSUSBHOST-controller. If this happens the next time, can you please also run "adb shell dmesg >logfile.txt" and send me the logfile? Then I can see what's causing it.

Regards,

Michael
[Motorola Droid 4] maisdoiscorregos:
I noted when i switch the GPS to ON, my phone not entry in deep sleep mode, only after reboot and the GPS in OFF.

Wellington
[Motorola Droid 4] wolf45801:
im running 1/20 build and location for gps is on and im deep sleeping fine
[Motorola Droid 4] rruleford:
Same here on 1/22 build. Battery has been great. 10-12 hours with heavy use.
[Motorola Droid 4] wolf45801:
yeah the only problem ive seen is the phone will kick over to searching for service but still say it has signal inside the settings/ about phone
[Motorola Droid 4] Shobai:
Here you go; hopefully it's just that I'm doing something silly. This is on the 0119. Thanks for checking it out!
[Motorola Droid 4] stargo:
Hi,

You're not doing something silly, it's still the USB host controller :(

<6>[93236.468505,0] HSUSBHOST mode=DISABLED stbyst=STBY idlest=TRANSITION
...
<3>[93236.468841,0] Could not enter target state in pm_suspend

It should not say "idlest=TRANSITION" here, as this means the controller is stuck.

Time to look at USB-patches again...

Regards,

Michael
[Motorola Droid 4] stargo:
There is that strange wait_for_local_clock-function in drivers/usb/host/ehci-omap.c which motorola used to replace msleep in a workaround for an usb-bug where I am not entirely sure that the function is correct. As a quick test I'll multiply the timeouts by 4 and if this solves the problem, I'll throw out that strange function and try msleep() again.

And there are many upstream-patches fixing problems with the workaround which don't apply to our tree as motorola decided to do stuff a bit differently. I might need to revert all of these changes back to the omapzoom-tree...

This quick test will be in the 2014-01-25 nightly.

Regards,

Michael
[Motorola Droid 4] wolf45801:
another thing ive been noticing is that the rom has been rebooting on its on
[Motorola Droid 4] thelolotov:
Same here, on both accounts, sadly. I'll try and catch it on ADB next time it pops up, but it seems to love to pop up mostly when I'm charging on the road... Also, if it helps, IIRC, music keeps playing when this issue occurs, keeps playing, up to the end of the song. So it's not entirely frozen.
[Motorola Droid 4] bustr85:
How stable

I've been using CM10.2 (one of the recent nightly builds) for a while now and find it quite good / reliable in your experience is it worth flashing 11 over the original ROM? Is it good enough stable/usable/reliable etc?

Thanks all
[Motorola Droid 4] bofis:
I find CM11 to be faster and more-stable than CM10.2 was. It holds onto a data connection better, and 3G works as well as LTE. I think the issue with setting the mobile network mode had to do with permissions, as after fixing permissions I have not had that problem since. I'm currently on todays, 1/24, nightly and all is well. Looking forward to how the test goes with tomorrow's build as far as further increasing battery life, though it's still better than stock imo
[Motorola Droid 4] Ghost93:
I'm on the 1/24 nightly and I have lost the ability to connect to wifi. It is just stuck on "Turning on wifi." Is anyone else having this problem?

---------- Post added at 11:26 AM ---------- Previous post was at 11:01 AM ----------

Also, I used to be able to snap a pic using my volume control buttons, but now I can't. That was a nice feature I would like to have again, does anyone know how it's possible?
[Motorola Droid 4] rruleford:
Open terminal and type su and then wifical.sh should fix WiFi issue
[Motorola Droid 4] bofis:
I use Focal (https://play.google.com/store/apps/details?id=fr.xplod.focal) instead of the stock camera, since it seems to default to using the volume keys as shutter rather than stupid zoom that no one ever wants. Unfortunately, neither camera has any settings for saving images to the external (REAL) SD Card yet, but hopefully the setting to swap sd cards will get merged back into CM11 soon and fix that issue.

I'm on the 1/24 build now, but still having issues with my screen not waking up at times. I was just reading an SMS a second ago...let the screen time out, and when I pressed the power button to wake it back up immediately, only the soft keys light up for 30 seconds, but the screen itself now will not turn back on and I have to hold power until the phone reboots :(
[Motorola Droid 4] kwyrt:
For the phone not waking up issue, I have trained myself to give it a second or two before pressing the power button to wake it back up after a screen timeout. It's kind of a pain but I have not had any issues since I started doing that.

Droid 4 - CM11
[Motorola Droid 4] kwood129:
I decided to go to the 1/19 build because of the wake issue. Seems like it was better that way. Hopefully tonights build will be better
[Motorola Droid 4] bustr85:
So is there any major drawbacks from 10.2 or everything is okay?
[Motorola Droid 4] Ghost93:
Did not work. It says nvs_map.bin not found.
[Motorola Droid 4] rruleford:
Hmmm. Try reflashing after doing full wipes. If not try to redownload maybe it got corrupt.
[Motorola Droid 4] Ghost93:
Just flashed the latest (1/25) nightly. Got wifi back, thanks for the help.
[Motorola Droid 4] zman2107:
Try 25th nightly no WiFi tried calibration no luck downloading 26th nightly now

Edit wiped 3 times flashed again and all is good :) WiFi working on 25th build
[Motorola Droid 4] stargo:
Anybody experiencing deep-sleep problems caused by the suspend_backoff wake_lock with builds 2014-01-25 or newer?

If I don't hear anything in the next few days, I'll push the fix to CM upstream (let's hope that I finally found the real cause).

EDIT: fixed the wake_lock name

Regards,

Michael
[Motorola Droid 4] Shobai:
I'm now on the 0126. I thought I saw it yesterday morning, after taking my phone off the charger when fully charged, but neglected to take a screenshot or capture dmesg output. I'll try and reproduce it and let you know.

[edit]

OK, I've got one! From fully charged, I pulled the charger and had no suspend_backoff after a couple of hours of sitting idle. I turned on WiFi and GPS, and connected to a WiFi network, browsing the 'net for a short while to knock the battery down a little. I then turned off WiFi and GPS and let the phone idle; again, no suspend_wakelock.

I then plugged in the charger and let it get a partial charge, up to 93% or so, before pulling the cable. The phone then sat idle for a few hours, aside from receiving a phonecall that I missed due to it being on silent - whoops! :p I took the screenshots and dmesg log after this, and as you can see the suspend_backoff is there...

Hope that helps in some way! I've got the phone charging back up now, I want to see whether it gets resolved after receiving full charge - previously, only a reboot would fix it once it happened.

Thanks for looking into this!
[Motorola Droid 4] stargo:
Thanks for your detailed report, but I failed to reproduce the problem :(

I have now pushed some more cleanups to the usb-driver into the repository, so let's hope 2014-01-29 will solve it for you.

I would be very surprised if this problem clears itself without a reboot.

Regards,

Michael
[Motorola Droid 4] Shobai:
No worries =) it may still just be my phone. yes, it would have been a pleasant surprise, although i didn't hold much hope for it either
[Motorola Droid 4] bofis:
As there has not been an official build since 1/27, are you merging in all the changes that are listed as "to be included in the next nightly" into today's or tomorrow's build?
[Motorola Droid 4] stargo:
Yes, every build is running a repo sync as a first step. But as all official builds are currently failing due to an API change, I think that my build this night will fail with the same error...

Regards,

Michael
[Motorola Droid 4] YeeP:
Has anyone with Verizon service, in the U.S. been able to get MMS to work, without downloading something like Verizon Messaging app? I also have this problem with CM10.1. If I go to the "factory" setup, I can immediately use the standard text app to send MMS.

I have tried the manual setup of the APN settings to the following:

Name Verizon
APN internet or vzwinternet
Proxy blank
Port blank
Username blank
Password blank
Server leave it blank
MMSC http://mms.vtext.com/servlets/mms
MMS Proxy
MMS Port 80
MCC 310
MNC 012
Authentication type not set
APN Type internet + mms

Without any luck. Any help would be much appreciated.
[Motorola Droid 4] bofis:
I've been using Handcent SMS for SMS/MMS since CM7 and have never had any issues. I realize that isn't exactly what you were hoping for, but it's way better than Verizon Messaging bs and I happen to like many things about Handcent over the stock messaging app (or Hangouts at this point). It has a lot of customizations so you can fit it to your tastes or set conversation view that isn't ios-style bubbles. The notification pop-up that let's you reply over the lock screen is by far the feature I don't want to give up. And it manages to send MMS just fine under CM11.
[Motorola Droid 4] YeeP:
Great info, I will give that a try. Were you able to get the "factory" MMS to work before you went to Handcent?
[Motorola Droid 4] rblanca:
Once again thanks stargos 4 this roms...it's working great!
[Motorola Droid 4] rruleford:
It comes and goes for me. But never fails with handcent
[Motorola Droid 4] YeeP:
Interesting.... Handcent seems to fail "quickly" for me with a message that the MMS could not be sent. I HATE Verizon message but feel like I am being pushed toward it.

rruleford - can you actually get into the APN part of your phone? Mine is greyed out. After re-installing multiple ROMs in different orders with the GAPPS (installed at the same time versus installed GAPPS after first boot into rom then reboot) I have come to the belief that something changes after installing the GAPPS.

I literally installed 5 different ROMs yesterday, multiple times a piece, to try and solve this MMS issue. I love the cool stuff with the custom roms, but wth is the point if I cannot send MMS?

Frustrated.... :(
[Motorola Droid 4] COMpulse:
Try GoSMS. I've never had a problem with SMS or MMS when using GoSMS.
[Motorola Droid 4] bofis:
If you go under Mobile Networks, and "Preferred network type" do you happen to have it set to LTE? If so, then data will work fine, but that mode is LTE-ONLY, and what you need in order to properly send messages is CDMA+LTE/EVDO. As for going into the APN menu, it's listed for me under Mobile Network Settings three below "preferred network type" and the one presently selected is called LTE-Verizon Internet (vzwinternet).

I haven't had this issue on any CM10.1, CM10.2, or CM11 builds I've tried, though Stargo's unofficial ones are the best ;) I also have not reinstalled the gapps package since I first upgraded to CM11 from CM10.2. At that time, I used gapps-kk-20131208-no_set_metadata.zip
[Motorola Droid 4] Technix2002:
cm-11-20140113-UNOFFICIAL-maserati.zip

Reverted back to cm-11-20140113-UNOFFICIAL-maserati.zip after trying newer builds. I never had wake-locks or sleep of deaths until I tried newer builds. Just letting others know if you experience the same things. My only complaint about cm-11-20140113 is Wifi, have to toggle it on/off a few times to get it to reconnect with my network (generally doesn't auto-connect when in range either). Other than that this seems rock solid for me! Continue the awesome work Stargo, thanks!
[Motorola Droid 4] rruleford:
Messaging crashes when sending MMS using 2/1 build
[Motorola Droid 4] alteredlikeness:
Same in Atrix2, RAZR, etc.. Looks like dhacker pushed a fix yesterday: https://github.com/CyanogenMod/android_vendor_cm/commit/f8b0737a435d211b01baf5df3feb9f98039884e2
[Motorola Droid 4] PJroast:
Issues with Hangouts messaging

Anyone else having issues receiving Hangouts messages? I'm on the 1-29 Nightly and using the PAGapps, and the issue I'm having is that my Hangouts app doesn't always receive messages when theyre actually sent. Sometimes it'll come 3 minutes late, other times 30 minutes or more. The only way to force it to check for a message is to turn airplane mode on/off. These problems are happening on both WiFi and on data. I added Hangouts to the exception list of my app killer, but aside from that I have no idea why its not working well.
[Motorola Droid 4] rruleford:
Yea seems fine on today's build.
[Motorola Droid 4] beflythis:
anyone else having battery life issue? i'm having to charge throughout the day, when i typically can run a full day (16 hrs at least; more with the right tweaks) on a good ROM.

can also report sleep of deaths... and tricky automated wifi reconnection when in range (have not been able to fix this yet).
[Motorola Droid 4] viper2035:
Keyboard layout

Hi,

I'm using nightly of 29.01. and I've got a problem with hardwarekeyboard layout. If I push

"shift"

and the

".(:) button"

a

">"

appears and not the

":"

and similar to this if i push

"shift"

+

",(;) button"

the

"<"

appers. Does anybody know how to fix this? I'm using the English(USA) layout. Another problem is that the transparent statusbar doesn't work. I'm using the Xperia Launcher and the statusbar is black. Is it a launcher related problem or is it a general issue?

Edit: Fix found just unmarking all Keyboardlayout's does work
[Motorola Droid 4] bofis:
I have had no trouble with SMS/MMS on my phone, using Handcent SMS, including today's 2/03 build. As for the black status bar, that is entirely dependent on your launcher, and as far as I can tell, the Xperia Launcher shows a black status bar on Sony phones too, so no reason to believe it would do anything differently on our devices. In fact, even with the Google Experience Launcher the status bar is black except within an app that does it itself. I'm fine with it and have stuck with ADW EX Launcher, but I've heard you can get the transparent bar back if you use Nova Launcher.

Additionally, my physical qwerty keyboard works 100% fine, as do all function and extra characters using the shift key. I just tested it and : worked fine. You may have to clear data or at least try today's nightly to see if that fixes it.
[Motorola Droid 4] doener:
Any chance to see the Advanced Storage ( http://review.cyanogenmod.org/#/c/56516/ ) menu or at least the old swapping functionality in this rom? Its so annoying to have low memory while a 64gb micro sd card is in the phone with 16 gb free.
[Motorola Droid 4] bofis:
Stargo could merge it into a test build for us, and I would be more than willing to test that out and see how well it works with our device. However, the patch is on it's own track to be merged into the main CM11 tree eventually...so if anyone with clout can review the code maybe that'd help move things along?
[Motorola Droid 4] daniel_m:
Yes, that would be awesome! They seemed to have "fixed" the camera already, so that you can save pictures to the external memory in the official CM nightlies. But pictures are my least problem when it comes to storage space ...
[Motorola Droid 4] doener:
What does Enable camera-sensor calibration mean?
[Motorola Droid 4] wvdschel:
Thanks so much, it's great to have an actively developed, up-to-date ROM for our Droid 4's. I can't upgrade to anything newer, because there's no keyboard phone that works on the European GSM networks. Your work is a godsend!
[Motorola Droid 4] stargo:
The camera now reads the sensor- and device-specific calibration-files and should tune the camera with these values. The stock firmware does that, too. So the pictures should in theory get better and it seems to me that they are not as underexposed as before, but I'm not really sure.

If you can clearly see a difference (better or worse) please tell me so I can decide if I push this upstream or not.

Regards,

Michael
[Motorola Droid 4] rblanca:
Thanks once again Michael for everything you do!
[Motorola Droid 4] thelolotov:
I was coming here to whine some more about the SoD issues, because it was happening constantly, but, I updated from my late January build, and so far, so good. If SoD is truly gone for good, thank God, because I was about ready to switch to stock every day for work. Still might, because of the battery issues, but...

Okay, it's not just me and JJB, is it? Battery stats are completely screwed, It'll charge to 101-106%, then battery will nosedive at random, and suddenly a few hours later I'm at 10% battery. This is driving me insane, and I don't see anyone else talking about it here. Another guy I know using this ROM is having this issue, and it's happened with multiple phones and batteries for me, so I'm not crazy.

In other news, Stargo, keep up the great work, I really wish I wasn't being forced off my Droid 4 in a couple months, because if the SoD and battery issues went away, I'd love to keep my Droid 4 for the next year or two.
[Motorola Droid 4] stargo:
Hi,

I still don't know what causes the SOD as I simply can't reproduce it and I got no dmesg-logs from people who experience it... I'm pretty sure that I did not inadvertently fix it since 2014-01-16. If you manage to get a dmesg-log when the screen does not wake up I think I can see what's going wrong and fix it.

Which kernel-wakelocks are responsible for you problems? Still suspend_backoff?

That's another problem I can't reproduce any longer... It's been stable for me since the beginning of january.

Let's hope I can fix your remaining issues. But I need log-files!

To get the dmesg-log, run "adb shell dmesg >dmesg.txt" from a computer connected via usb. You need to first authorize this machine to be allowed to use adb, so try it when the display is working ;)

Regards,

Michael
[Motorola Droid 4] thelolotov:
Regarding dmesg, it never seems to happen when I'm near a computer, but I'll keep trying to get you a log.

Regarding battery, I don't think it's wakelocks, I think there's just something deeply wrong with battery reporting, my battery should not be charging to 106%. I think the battery reporting is just messed up. I'll try and get you some more details.
[Motorola Droid 4] bofis:
Well, I can confirm it is NOT fixed as of 2014-02-05's build, though it only happened once and hasn't on today's nightly....yet. I will authorize my machine to get logs when I get home and hopefully it'll happen while I'm home rather than when I'm out. It is very rare, and very random, as far as I can tell. Of course, it might not be random, but as I can't see the screen and always just hold power to reboot, it's not like I've been able to notice a pattern of what causes it.

As for the camera, I think it's working pretty well now, though regardless of what camera app I use, it does NOT rotate photos properly, and always saves them wide, even if taken in portrait. What is controlling that if not the camera app?
[Motorola Droid 4] crzayalex:
Problem with auto sync

Hi, thank you for making 4.4 possible on my Droid 4, but I noticed a problem. The rom works perfectly fine after fresh install, but after 3 - 4 hours of usage, the applications fail to auto sync. Apps such as gmail, hangout, groupme does not receive new messages until manual refresh or an one hour delay. Does anyone else have this problem?
[Motorola Droid 4] bofis:
I have confirmed with other people that do not have our phone and are not using CM11 that this has been a problem for them recently too. I think it is actually a sync issue on Google's end and that perhaps once disconnected for long enough, the phone won't retry until you go into accounts, and manually sync the affected accounts again. Once you force sync, it should be fine at least.
[Motorola Droid 4] lucize:
can someone with cdma confirm that by removing the line thelephony.lteOnCdmaDevice from build.prop, all services are working as they should ?

Regards
[Motorola Droid 4] IndiaBhai:
LTE service works fine after deleting the line, even upon reboot. Some oddities occur though:

- After Reboot, Verizon Wireless doesn't show up as my carrier, I simply have "No Service" listed

- 3G (EvDo) does not work

- Data turns off during call

I can confirm that SMS, Calling, Bluetooth, WiFi and an LTE data connection work fine.
[Motorola Droid 4] lucize:
So it can't be turned off by default

Thank you
[Motorola Droid 4] crzayalex:
Thanks for checking bofis, I understand the lag on google services but Group me is not provided by google?
[Motorola Droid 4] bofis:
sooo, I just had my phone not wake up, tried to plug it in via usb to get a dump for you, but my computer did not recognize the device :-\ Works usually...anyway, fantastic battery life on yesterday's nightly, but now this was just under today's
[Motorola Droid 4] stargo:
Ok, then something seems to have crashed completely :(

There is a fishy code-path in handling resume from sleep in the backlight-driver. I will put in a temporary patch for tomorrows build which correctly locks access to shared variables and tries to re-init the backlight if it failed.

The following parts are currently suspect for this problem (in the order of probability):

the backlight-driver

the omap i2c-driver

the dss-subsystem

EDIT: removed deep-sleep specific stuff, as the suspect code-path is also used when just turning off the display without entering deep-sleep.

Regards,

Michael
[Motorola Droid 4] LuH:
OTG working :)

OTG works fine, the phone just doesn't power it. I use a hand-made USB M - M cable that I plug into charger (be sure not to have current too much over 500 mAh. I use 700 mAh charger and it works fine) and USB hub (random slot), it powers the stuff well. I toyed with using mouse, keyboard, presenter and pendrive ;)