yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] stargo:
Hi,

Any particular time when they happen? Right after suspend/resume?

Is it a real reboot (Motorola logo visible) or "just" surfaceflinger crashing (just CM logo visible)?

I have added kernel-changes which should solve the suspend_backoff wakelock, as the internal USB Host is getting stuck in a sleep-mode transition, but they worked fine for me.

Then I had to do a qucikfix because surfaceflinger was broken and did no longer compile.

So I'm not sure which of these 2 is responsible...

Reagrds,

Michael
[Motorola Droid 4] stargo:
Ok, I could just reproduce it. Seems to be related to my USB changes, as it only happened after I reactivated wrigley (I'm in GSM land with LTE in the wrong frequency range).

I've just removed the image from the webserver and will put up a newer version if I can fix the problem.
[Motorola Droid 4] doener:
With the official CM11 nightlies I get the same result. So I expect that there is some general problem with Bluetooth in cm11 maybe only with older Bluetooth Profile version. Log: http://pastebin.com/dC7SNjT9 with my MC00 Headset.
[Motorola Droid 4] lucize:
it's working fine, until build.prop is modded for gsm, then it will start rebooting, too bad I finally had deep sleep..
[Motorola Droid 4] stargo:
I also had it reboot with the stock build.prop...

I'm not using the multimode-ril at all on my phone, so the wrigley chip never gets initialized (only the cdma/gsm mdm6600) and so I didn't see the crash...

But it seems it is not the commit fixing the USB related sleep problems but another one (also touching USB suspend/resume), which I have now reverted. I am currently doing a clean build (it worked fine for me on a dirty build).
[Motorola Droid 4] PJroast:
I tried to apply the 12/21 nightly and my phone bricked - HARD. It gets past the red Moto logo and is stuck (the bootloader is locked too, but I dont know if it was ever unlocked?). I was running the PA-GApps full modular (pa_gapps-modular-full-4.4.2-20131215-signed.zip), and I went to apply the update as usual through the settings menus and it bricked :(

On a side issue, with GApps installed, I couldnt adjust the number of rows and columns on my screens. Before those settings were accessible through the Personalization section of settings, and in CM11 (without GApps) i could get to it by long pressing the screen. However, when I long press and click settings it takes me to the damn Google Now settings.
[Motorola Droid 4] lucize:
using safestrap and everything is ok..
[Motorola Droid 4] lucize:
tried second build from today and no luck with deep sleep

I've made a screenshot
[Motorola Droid 4] stargo:
Can you please also make a screenshot of the kernel wakelocks? They might contain additional clues.

And try tomorrows build, I've added more suspend-related changes.
[Motorola Droid 4] lucize:
this is the page with kernel, i'll let it settle some more and I'll make screenshots with all the ages from WLD

I cloned your git, I'll make a local build, as I'm interested if bluetooth BLE can be made to work

Regards
[Motorola Droid 4] stargo:
You are right, sorry. I'm probably too tired...

I don't like the "deleted_wake_locks". There shouldn't be that many of them. If you still get them, can you please run "dmesg" on the phone and look for something like this:

<6>[ 1176.083374,0] Read Powerdomain states as ...
<6>[ 1176.083374,0] 0 : OFF, 1 : RETENTION, 2 : ON-INACTIVE, 3 : ON-ACTIVE
<6>[ 1176.083404,0] Powerdomain (core_pwrdm) entered state 1
<6>[ 1176.083404,0] Powerdomain (gfx_pwrdm) is in state 0
<6>[ 1176.083435,0] Powerdomain (abe_pwrdm) entered state 0
<6>[ 1176.083435,0] Powerdomain (dss_pwrdm) is in state 0
<6>[ 1176.083435,0] Powerdomain (tesla_pwrdm) entered state 0
<6>[ 1176.083465,0] Powerdomain (wkup_pwrdm) is in state 0
<6>[ 1176.083465,0] Powerdomain (cpu0_pwrdm) entered state 0
<6>[ 1176.083496,0] Powerdomain (cpu1_pwrdm) entered state 0
<6>[ 1176.083496,0] Powerdomain (mpu_pwrdm) entered state 0
<6>[ 1176.083526,0] Powerdomain (ivahd_pwrdm) entered state 0
<6>[ 1176.083526,0] Powerdomain (cam_pwrdm) is in state 0
<6>[ 1176.083526,0] Powerdomain (l3init_pwrdm) entered state 1
<6>[ 1176.083557,0] Powerdomain (l4per_pwrdm) entered state 1
<6>[ 1176.083587,0] Powerdomain (always_on_core_pwrdm) is in state 0
<6>[ 1176.083587,0] Powerdomain (cefuse_pwrdm) is in state 0
<6>[ 1176.083587,0] Successfully put all powerdomains to target state

If you get a "Could not enter target state in pm_suspend" then I would be very interested in the block before "Read Powerdomain states as ...", which should look something like this:

<6>[177113.084442,0] PD_CORE curr=ON prev=ON logic=ON
<6>[177113.084503,0] PD_L3_INIT curr=ON prev=ON logic=ON
<6>[177113.084533,0] CD_L3_INIT mode=SW_SLEEP activity=0x2006100
<6>[177113.084564,0] HSUSBHOST mode=DISABLED stbyst=STBY idlest=TRANSITION
<6>[177113.084625,0] DPLL_USB status=locked
<6>[177113.084625,0] PD_L4_PER curr=ON prev=ON logic=ON
<6>[177113.084686,0] PD_MPU curr=ON prev=ON logic=ON

In this example case, the USB host controller is stuck in a power-state-transition which can only be fixed by a reboot.

Good luck! :)

Regards,

Michael
[Motorola Droid 4] lucize:
no I have different output in WLD

I attached a dmesg and a logcat too

Regards
[Motorola Droid 4] stargo:
There is your problem:

<6>[ 553.027374,0] active wake lock st_wake_lock

This is fixed in tomorrows build (or if you build an image from my repositories now).

Try toggling bluetooth on and off for now, this should also release the st_wakelock.

The kernel-code for this thing is definitely wrong, but I'm still missing some internal relationships of the shared-transport-driver to correct the code. That's why there is only a workaround in the code in tomorrows image.

Regards,

Michael
[Motorola Droid 4] xantanion:
I would say the battery life is pretty good on the 12/21 build, will compare to the 12/23 when its up later, here are some screenshots of how my phone is doing on the battery. And stargo, it was a full on reboot to the moto emblem
[Motorola Droid 4] rruleford:
Looks like you should safeboot back to stock. It happens
[Motorola Droid 4] scottay:
I am also seeing MAC address unavailable. I never paid much attention to how custom ROMs handle this, but now I'm seeing that this seems to be a common issue but generally doesn't cause connection problems with unfiltered networks.

Now, however, I am trying to use an Eye-Fi card which requires a consistent MAC address for my Droid 4, and I would like to use my original true MAC address, and not a random one which it seems many ROMs across many device types generate. I can find some solutions to set the MAC address, but not anything specific to Droid 4 and I am not sure which solutions are specific to different devices or ROMs. Is anyone familiar with how the MAC address is handled in CyanogenMod ROMs, and the reasoning behind it?

Don't know for sure if these posts are relevant, since they relate to different devices:

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

http://xdaforums.com/showthread.php?t=2135128
[Motorola Droid 4] thelolotov:
12/23 build won't install for me, another guy has the same issue. I think he was able to fix by swapping the updater from an older build or something.

E:Error executing updater binary in zip

Error flashing zip

Also, how different are these builds from official CM11? Anyone tried?
[Motorola Droid 4] stargo:
You are in fact using your static mac-address, it just is not displayed in the settings. This is because the generic wpa_supplicant is currently running on the device and not the ti-specific one (which is not yet fully compatible with 4.4). It's just a visual problem.

You can find out your mac-address by executing the following on the phone (in a terminal emulator or via adb):

ip addr list dev wlan0

This will result in something like this:

13: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:11:22:33:44:55 brd ff:ff:ff:ff:ff:ff
...

In this example, 00:11:22:33:44:55 is the mac-address.

Regards,

Michael
[Motorola Droid 4] stargo:
You are using SafeStrap 3.65?

This ROM should install without any hacks there.

Regards,

Michael
[Motorola Droid 4] joojoobee666:
That other guy was me. I noticed that the update-binary was almost identical byte for byte (maybe there were a total of 5 bytes that were different) so I don't believe the updater itself is broken. I did note that there were some changes to the updater-script. Namely, all the set_perms were changed to set_metadata. Looks like we actually need a newer updater that understands these new commands. I found this thread which seems to be directly related to the issue: http://xdaforums.com/showthread.php?t=2532300 and it offers a patched updater as well. I haven't tried it.
[Motorola Droid 4] kwyrt:
Just installed 12/23 over 12/17 with no issues. I didn't look at the updater script so I can't say what might be different or not but I encountered no errors during install and everything seems to be running fine.
[Motorola Droid 4] joojoobee666:
I checked the script, it is using the new set_metadata. After some further reading, I found that this was something was handled by the recovery itself (TWRP). I was on Safe strap 3.53. Updated to 3.65 and tried to install, but failed again, this time with a "set_metadata_recursive: some changes failed" error leaving the system completely trashed. So back to my modded 12/23 zip I go. :D
[Motorola Droid 4] xantanion:
12/23 build won't let me install anything, tried fixing permissions and such, says it can't write to usb or sd card
[Motorola Droid 4] lucize:
for me is working very well, deep sleep too !

Regards
[Motorola Droid 4] Technix2002:
modded zip of 12/23 KK

Hey Joojoobee,

Any way you could share that modded zip of 12/23 KK? Ihave the same deal going on, but I'l still on SS 3.53 and I'm not going to update since you said it doesn't appear to make a difference.

-I followed the steps in your post, but it failed for me again. Looks like I still would like a copy of your zip file please.

Thanks,

Brad
[Motorola Droid 4] PJroast:
Yeah, I got the D4 utility so that should do it.

On a side note, is there a way to change the number of rows or columns or other homescreen options for 4.4?
[Motorola Droid 4] joojoobee666:
I build from source which I modify for personal needs. But, if you just want to get the latest build, grab the 12/18 build pull out the files in "META-INF/com/google/android" and overwrite the ones in the zip from the 23rd, rezip and flash. The only difference in the script is the changes between set_perm and set_metadata but the outcome is the same.
[Motorola Droid 4] rruleford:
12/23 build and finally deep sleep and great battery life so far. Thank you stargo!
[Motorola Droid 4] stargo:
It definitely works with SafeStrap 3.65, that's what I am using. It should really work without replacing anything in the zip.

But as a christmas present, I'll reeneable SKIP_SET_METADATA, so it works with older recoveries again (but this will prevent selinux from ever working correctly on the device).

Yes, I've seen that. Came from a fix I pulled in yesterday. I have pulled in the fix for the fix and am currently building a test-build. Should be fixed in tomorrows' build.

Regards,

Michael
[Motorola Droid 4] kwood129:
Is there a chance that video recording on KitKat will be higher than 480p? I realize this has been an issue for some time but was just hopeful that we will be able to get a higher resolution sometime. The real stocking stuffer would be using the HDMI but I think I have a better chance of getting a lump of coal instead :)
[Motorola Droid 4] lucize:
I can connect the device to my laptop and I can listen the music from the phone to my laptop. It works also while it's playing on the phone and when I activate the bluetooth it automaticaly plays on the laptop.

The calls are not working.. neither on the laptop nor in the headset.

but my test is made on a local build of 23 with BLE enable and the last (working) firmware from TI, tomorrow I will test with BLE devices (the software doesn't complain anymore about the lack of BLE), hopefully it will work and maybe with the original firmware too.

I can't recall if headset was working from start or not..

Regards
[Motorola Droid 4] thelolotov:
Upgrading to 3.65 fixed it for me, JJB is the only one who is using 3.65 and is having problems. Maybe hold off on changing SKIP_SET_METADATA for now.
[Motorola Droid 4] rruleford:
Am also experiencing this issue
[Motorola Droid 4] rush242:
Agreed. Some of the best battery life I've ever seen on this phone.

Question, do any of you have any issues with ending calls? Screen won't come on, et cetera?
[Motorola Droid 4] rruleford:
Intermittently. Haven't seen it past few builds though.
[Motorola Droid 4] xantanion:
12/24 build, everything is working smoothly, no issues with camera or installing anything (when I flash nightlys I have to reinstall xda every time) I will report on battery findings in the morning
[Motorola Droid 4] stargo:
:)

But I wouldn't say there are no issues with the camera, it's way to underexposed currently.

CM added code which relies on some parameters available only on QCOM hardware (max-saturation, max-contrast and max-sharpness). If the camera does not provide these parameters (which aren't even defined when building for non-qcom-hardware), the Camera-app just crashes.

My quick workaround was to provide these parameters in the OMXCameraAdapter, but it seems if they are available, other things go wrong. Trying to find a better fix now...

Edit: Ok, exposure fixed, but it's still broken in many other ways (e.g. touch-focus). We simply don't have qcom-hardware and the Camera-app now relies on it...

Regards,

Michael
[Motorola Droid 4] kwyrt:
Thanks [MENTION=3457922]stargo[/MENTION]. Is there another camera app that we could sideload that might work better? Or is it a CM11 problem and not an issue with the app itself?

Droid 4 - CM11
[Motorola Droid 4] stargo:
It's just the Camera app. Haven't found a good replacement yet and focal leads to a PVR buffer problem killing the camera for the session, so that's not a replacement either. Sadly the output I get in the kernel log when that happens is not too helpful to fix that problem.

I hope that CM upstream will fix the reliance on qcom hardware once the N1 madness has slowed down. Yesterday they also broke Bluetooth for many devices while fixing stuff for the N1...
[Motorola Droid 4] lucize:
I tested moto x cam (the leak) and is working ok

Regards
[Motorola Droid 4] COMpulse:
Themes Provider and SystemUI took a dump on me in the last few builds. Had to full wipe and reinstall.
[Motorola Droid 4] joojoobee666:
Well, further info regarding the issue over here. I did a compare of the updater script in your build and in mine, they are identical. I re-jiggered my internal space and created a 3rd slot, tried to install there but same error. Download your 12-23 nightly, confirmed it was still using the set_metadata_recursive.and attempted to install to new slot and it worked, I'm not sure why mine are failing, but that does confirm that SS 3.65 fixes the issue. I just need to compare and see why mine failed. Maybe I'm missing a folder/file that that set_metadata_recursive gets all pissed about, where set_perm didn't give a rat' ass. I'll compare and step through the script to see what I can find.

Update:

I added a ui_print in front of every set_metadata_recursive and discovered it's failing on the first one encountered:

set_metadata_recursive("/system", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");

I looked at the file_contexts being generated, both are identical. Also, as far as I can tell, the only differences between the nightly and my builds are additional files, minus a few APKs (which don't appear to be target with this anyhow). Any ideas on where to go next?
[Motorola Droid 4] DiMacho:
updating the rom

I am now running the cm-11-20131201-UNOFFICIAL-maserati . Is het save to update through cm updates in the settings? I just got the notice for update cm-11-20131223-Nightly. And if I do so, is there a need to wipe cache?

Or shoud I do a backup and install it fresh in SS?
[Motorola Droid 4] rush242:
Hroom, hm, hrroom. Don't be hasty.

Please.

---------- Post added at 02:14 AM ---------- Previous post was at 02:07 AM ----------

Wait. What are you asking? Michael (OP) has got UNOFFICIAL updating through Settings > About Phone > CyanogenMod updates, where you can set how often it checks for updates, and what kind of updates it checks for. You can update it that way--it works automatically.

If you install it yourself, best practice is to wipe cache, Dalvik cache, and system first (SS will give you the option to Factory Reset, but unless that has changed, I don't like/want to completely wipe the phone each time), then, after the ROM is installed, wipe cache and Dalvik cache again before you reboot.

Does that help?
[Motorola Droid 4] kwyrt:
I follow the same procedure except for the wiping system part. If you do wipe system you will have reflash gapps unless I'm mistaken.

Droid 4 - CM11
[Motorola Droid 4] myk3916:
is no headset capability... Not talking abou tbluetooth... Wired headphones w/ mic

No icon... Cant voice type thru external mic
[Motorola Droid 4] kwood129:
I just plugged my headset in and google search is taking voice commands just fine.
[Motorola Droid 4] myk3916:
try hiding the phone under a pillow or putting it further away because it's probably picking up the sound of the phone Mic... I tried several times... at first I thought my voice recognition Google typewas just acting crazy and then I figured it out.

but then again it could be the brand of headset, which I will not rule out... Do you get the headset icon on the statusbar?
[Motorola Droid 4] kwood129:
I did the easiest test I could. I tapped on the headset mic. In google search it gave the circular wave around the microphone icon. It is definitely getting input from the headset and not the phone. I am not getting the icon on the phone but I figured thats just eye candy they havent made it to yet.
[Motorola Droid 4] lucize:
wrong post.. sorry
[Motorola Droid 4] DiMacho:
In my rom, one of the first 11.2 is no UNOFFICIAL Updating. Only STABLE or NIGHTLY.

One time I update through that menu to another NIGHTLY and my whole system was broke. So that is why I ask this. I guess i have to do a backup in SS first and then try to update through the menu/settings.

I also have a lot of apps and sysytemapps freezed. Is that going to be a problem while updating?
[Motorola Droid 4] stargo:
Ah, you are still on one of my "old" ROMs. This will still have the URL of the CM update-server, so you would install the official nightly this way. If you want to stay on my nightlies, download and install the current one manually. After that, you can update through the updater.

Frozen apps shouldn't be a problem.

Regards,

Michael
[Motorola Droid 4] DiMacho:
Thanks Michael! It is still working perfect, only did some own tweaking. Only problem is getting a good gpsfix.

Guess I can try the new ones out after Christmass when I have time.:cool:
[Motorola Droid 4] myk3916:
Mines not working at all... But if i safestrap over to stock its fine. Definitely could be a minor issue. Its a pain because im a truck driver, allway forget to charge bluetooth cause i got more important issues, so i use wired headsets.

Great rom.. Cm 11.2 is almost perfectly flawless...love it.. My dsily driver for about 48hrs now... I tried gummy, its cool but freezes on me...
[Motorola Droid 4] wolf45801:
any one try 12/25 build and if so hows it running I haven't gotten a chance to flash it yet been busy getting Christmas ready
[Motorola Droid 4] rush242:
Got it. You're on the previous versions. D/L the latest nightly and install it manually. That will update such that it will update with Michael's soiree, and not the CM version.

You won't have to fiddle with SS or gapps, either.

---------- Post added at 09:16 PM ---------- Previous post was at 09:15 PM ----------

I haven't noticed any issues beyond the known.
[Motorola Droid 4] rblanca:
What a great rom! Thanks Stargos!...the only missing thing it's HDMI but is a common bug.....Thanks anyway!

By the way...searching on google a found this:

http://e2e.ti.com/support/omap/f/849/t/249397.aspx ... using this kernel https://github.com/CyanogenMod/lge-kernel-omap4/tree/android-omap-3.0/drivers/video... it seems a LG phone with omap4430 and HDMI drivers (i dont know if it will work or not)

In any case..Thans 4 this awesome rom!
[Motorola Droid 4] stargo:
Thanks :)

Motorola decided to implement everything their own way, so the normal omap-drivers won't work. It seems the code was in the CM kernel once, but Hashcode reverted it (it probably conflicted with some updates to the display driver). I'll try to get it working if I have some spare time.

I'm signing off now until next year, maybe I'll meet one or the other at the 30C3 (yes I know, very low chance). If you're there, call 2746.

I'll probably not fix build-problems during that time, so if the nightlies break, they will probably be available starting on 2014-01-02 again.

Cheers,

Michael
[Motorola Droid 4] DiMacho:
\Do I still have to turn on ART after the ROMflash? And the install de gapps? Is anyone using ART?
[Motorola Droid 4] COMpulse:
ART is working fine here.
[Motorola Droid 4] rblanca:
Thanks Micheal 4 everything you do! Like a said HDMI is the only missing but even without that is the best rom for our Droid 4!...Again Thanks y have a nice Holydays!
[Motorola Droid 4] kwyrt:
FYI: Bluetooth is not working for me on 12/26 nightly. Will not connect to car. Tried deleting the paired device and reconnecting. It seems to see my car but after entering pin will not finish the connection. Rolled back to 12/24 and working fine.
[Motorola Droid 4] lucize:
maybe BLE activation is not ok, but I have mine working ok with the laptop and my earpiece.

Regards
[Motorola Droid 4] stargo:
I've reverted the BLE changes for now, so tomorrows build should work again. I'll look at when I'm home again next year.

Greetings from Hamburg

Michael
[Motorola Droid 4] firefox1996:
I have the same issue. But after install Camera Awesome v1.0.4 it works well :) But video only 480p.
[Motorola Droid 4] doener:
For me its working with the stock camera2.apk since the build from 24/12.

---------- Post added at 12:58 AM ---------- Previous post was at 12:51 AM ----------

For me even with BLE activated nothing changed with my MC00 headset. Its still disconnecting with: "btif_media_aa_prep_2_send congestion buf count 24" error message. I think we have some more Bluetooth Issues at least with older Protocols.
[Motorola Droid 4] firefox1996:
I try 20/12 build's camera2.apk, its working well :)
[Motorola Droid 4] lucize:
I left only #define BLE_INCLUDED TRUE in the build of bdroid, can you try with this attachment ?

it's based on 27 buld, the bluetooth is built into the kernel so you need to overwrite the whole kernel.

the revert kernel is 27 based, it should work with other builds too (both the patch and the restore)

I have broadcom based bluetooth in the laptop, some noname bluetooth usb and an sony ericsson headset so I can't test in the car. In theory it should work because the TI chip relies on standard bluetooth protocols.

Regards

Lucian
[Motorola Droid 4] kwyrt:
Thanks [MENTION=4772154]lucize[/MENTION]. I am at work now but will try to give this a test on my lunch break.
[Motorola Droid 4] lucize:
I have those errors too, but only when I have the sensor tag connected while playing music over BT, and the sound shutters but is not disconnecting

Regards
[Motorola Droid 4] kwyrt:
Bluetooth confirmed working after applying 4.4.2_BLE-maserati based on 27 patch. Updated to 12/27 nightly this morning and connected just fine. I then applied your patch and bluetooth connected with again with no issues. Thanks [MENTION=4772154]lucize[/MENTION].
[Motorola Droid 4] rruleford:
Am I the only one seeing phone app freezing when hanging up?