yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] TheXG6HD:
I can confirm that at least on my phone that LTE is working. Great work .
[Motorola Droid 4] nowseewhatudid:
flash these zips in recovery for root i got the from my nexus 7 root toolkit

HOPE IT WORKS FOR YOU :good::p:cowboy::cyclops:
[Motorola Droid 4] stargo:
Yay! Thanks for confirming :)

It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845

Cheers,

Michael
[Motorola Droid 4] thelolotov:
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<

It does come up a lot quicker, however.
[Motorola Droid 4] stargo:
That's VZW weirdness :(

But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...

Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?

Would be interesting to see, what is actually happening now. I can only guess from here...

Regards,

Michael
[Motorola Droid 4] sd_shadow:
LTE was working on first build, just took 10+ mins to connect then worked good.
[Motorola Droid 4] thelolotov:
The deal is, the data works at first, then at random intervals it breaks and needs to be manually reset. I'm travelling right now so I can't really risk using CM12 right now, but I'll get you some logs when possible. JJB is having the same issue, I'll ask him to try and get you some details.
[Motorola Droid 4] maisdoiscorregos:
joojoobee666

You could inform Stargo correcting the physical keyboard to incorporate it in the next building?
[Motorola Droid 4] Shobai:
Yes, I'm saying that the specs for the Droid 4 list USB Host, not USB OTG. Host works quite well in the context of a LapDock, but OTG is definitely more versatile. It's easy to see why more modern phones use OTG rather than Host.
[Motorola Droid 4] RawSlugs:
The gapps links didmt work for me
[Motorola Droid 4] sd_shadow:
sd_shadow's [Collection] of GApps
[Motorola Droid 4] RawSlugs:
How can I get root working?
[Motorola Droid 4] Septfox:
Ah, ok. I wasn't paying as much attention to the wording as I should have been.

Strange that they didn't at least pipe the original USB spec (5v/250ma as I recall) through to it to make it a proper fully-functional host, but I guess they didn't want users to just hook up a keyboard or somesuch rather than buy a Lapdock.
[Motorola Droid 4] maisdoiscorregos:
You could inform Stargo correcting the physical keyboard to incorporate it in the next building?

Thanks
[Motorola Droid 4] RawSlugs:
Root now works!!!

But swype gesture in the keyboard typing doesn't work when enabled in settings
[Motorola Droid 4] maisdoiscorregos:
Does not work here also
[Motorola Droid 4] Aceofzeroz:
Edit: Nevermind, I got what I needed.
[Motorola Droid 4] Septfox:
It hasn't since the first release.

Try Google Keyboard, as far as I've seen it's functionally and aesthetically identical.
[Motorola Droid 4] Cain77:
battery

it seems that in latest builds (stargos 2015-01-15 and cm-12-20150116 from me ) developers managed to remove wakelocks and battery again lasts 6+ days ( http://krilip.cf/download/img/Screenshot_2015-01-17-10-30-01.png ), can anyone confirm that?
[Motorola Droid 4] Elanzer:
6 days? It looks like you lost 15% battery in about 3 hours without much screen time in that picture.
[Motorola Droid 4] Cain77:
graph begins at 16.1. 11am and ends at 10am 17.1. so its 15% for nearly 24 hours
[Motorola Droid 4] rblanca:
I believe that its a false reading of battery...sure soon you are going to see a huge drop on battery %...15% on 24 hs it's something that doesn't exist since nokia 1100 :P
[Motorola Droid 4] Cain77:
builds from 9.1. lasted without charging whole week (since i keep wifi/mobila data turned off)
[Motorola Droid 4] Septfox:
That's what, 0.625%/hr?

It's very possible when the phone is mostly idling, in fact I've seen 0.5% in (earlier versions of, the build from the 9th wasn't as good about it) CM12 as long as wifi is off the majority of the time. Wifi deciding to be on more takes it up to 0.7%-0.8%/hr. Kitkat was capable of roughly the same, but it took a lot more work to get there.

And of course, the CPU being on more than a few minutes in a several-hour stretch hurts. I would imagine that most people don't see these low of idle figures because they have things running that wake the phone more in a given amount of time; though Lollipop's new APIs should help that quite a bit, once everything is updated. Just look at what they've done for Play Services, which in KitKat had to be basically gutted to make it stop killing the battery.

Haven't had a chance to really sit down and mess with the phone in the last few days, but I'll flash the latest tonight and see what I get. The build from the 9th has begun having difficulties (mostly in the form of random Play Services crashes, but the random wakelocks continue), so I look forward to getting back away from those.
[Motorola Droid 4] Cain77:
my words exactly, battery life depends on if you use phone as phone or as gaming console. sms and phone calls dont take so much power, but if you leave brightness at 100%, use wifi alot, navigation in the car, then you cant expect more than one or two days of battery life

i will try how long can todays build last normal usage on battery
[Motorola Droid 4] naifaharsy:
Just flash right?
[Motorola Droid 4] stargo:
Hi,

I have just uploaded new CM 12.0 builds for the OMAP4 devices which contain SELinux changes.

You have to do a manual fix for your current system to continue working without going through a wipe:

Edit: This is only necessary when updating from 2014-01-14 or 2014-01-15 as they include a commit which broke SELinux handling and causes unlabeled files on /data to appear. Upgrading from earlier builds is fine.

Due to SELinux changes, you have to relabel your data-partition on the first boot of a ROM built after 2014-01-17 when upgrading from a ROM from before that date. This only needs to be done once. To do this, enable adb/usb debugging and grant root to adb (both in developer settings) (do this before installing the new rom and try to access your device with "adb shell" from your PC to make sure you can get a shell).

After the system has booted up and is at the lockscreen, execute the following in an "adb shell" session:

su -c 'for i in /data/*; do echo "${i}"; restorecon -DFrv "${i}"; done; sync; reboot'

I'm sorry that this can't be integrated into the ROM directly and has to be done manually.

This has been tested on maserati and umts_spyder and should also work on spyder and targa.

Cheers,

Michael
[Motorola Droid 4] rblanca:
Sorry to ask this stargo but this could possibility install it on stock slot?...Again thanks for everything you do....put a donation link!
[Motorola Droid 4] stargo:
Hi,

I currently don't test on stock and I would assume that some SELinux-labels broke installing into stock. What is exactly happening for you? Does the Safestrap splashscreen still come up during boot (then there is a chance to fix it)?

Cheers,

Michael
[Motorola Droid 4] wolfah:
How do I get root to work?
[Motorola Droid 4] joojoobee666:
You have to enable it under the developer settings menu.
[Motorola Droid 4] wolfah:
I'm getting an error 'Unfortunately, the process com.android.phone has stopped'
[Motorola Droid 4] joojoobee666:
Yeah, known issue for Verizon users. Currently being investigated. Reboot again, if it still comes up, you will need to work around it and manually set the APN to "Verizon Wireless". If it's already selected, choose any other one and then reselect.
[Motorola Droid 4] anderskaseorg:
/pds/wifi/nvs_map.bin not found

I installed cm-12-20150118 in a freshly created rom-slot1, and noticed that WiFi came up with the default MAC address 00:da:36:16:de:eb instead of the unique MAC address associated with my device. Recognizing this as probably a wifical problem, I tried rerunning it:

root@cdma_maserati:/ # wifical.sh
****************************************
* Turning Wi-Fi OFF before calibration *
****************************************

********************************************************
* /pds/wifi/nvs_map.bin not found !! Not setting MAC *
********************************************************
******************************
* Finished Wi-Fi calibration *
******************************
*************************
* Turning Wi-Fi back on *
*************************

Indeed, /pds/wifi is an empty directory.

(Perhaps it’s relevant that I have CM11 in my stock slot?)
[Motorola Droid 4] sm4rty:
is installing lollipop into stock slot safe?

I dont want a Rom-Slot. I want it sitting in my stock rom.

Thanks in advice
[Motorola Droid 4] joefuf:
How is this as a daily driver? Any major components not working? How's battery life compared to the CM11 ROM?
[Motorola Droid 4] rblanca:
Nop...safestrap animation doesnt come up :(.... Thanks anyway stago!
[Motorola Droid 4] milda001:
I have a feel, device is a bit slower and the battery life is too shorter compared CM11.
[Motorola Droid 4] Oggie7797:
A "fix" on targa is to change the line in build.prop "ro.telephony.default_network=10" to an =6 this changes the default from global to not and helps with connecting to Verizon. It defaults to 3g though, so you have to select 4g in settings but no more fc. Again, this is on targa not maserati so it may or may not work but they're basically identical and use Verizon so..
[Motorola Droid 4] Septfox:
It's very stable and a good 95%+ functional.

Current issues that come to mind and aren't listed in the first post:

GSM setup is a bit finicky (see previous posts)

Installing to Stock slot doesn't currently work and leads to Bad Things happening

Virtual keyboard will pop and stay up regardless of physical keyboard status

The CPU governor doesn't ramp the CPU speed up completely sometimes, causing some random slowness

Ambient Display works, but doesn't trigger for pickups (missing sensor) or screen taps

So...no, nothing major. The GSM problem can be worked around, and the others are minor irritants.

I never liked CM11 itself, preferring Slimkat, so I can't make a direct comparison for battery life. I can however say it's about as good as a tweaked Slimkat 7.6 (which yes, I realize is pretty old); 0.5%-0.6%/hr idle with wifi off/half-on, ~0.8%/hr with wifi on, using CDMA in a rural location. No idea what data being on might do to that, though, and having non-L-optimized stuff running that causes wakelocking will naturally hurt it.

I noticed yesterday around 3%/hr playing music with the screen off, not sure if it's better or worse than 4.4-based ROMs manage. Think I'll check that tonight since I never really paid attention before, but it's probably similar.

And of course, having the screen on kills the battery pretty fast regardless of what you're doing.

CM12 itself is still missing some CM features - notably theming - but they've been working their asses off getting features added, and are making some impressive headway. Our resident D4 devs - primarily stargo and joojoobee666 - have been doing an awesome job both making sure commits don't cause anything to be horribly broken for us, fixing the few things that weren't working from the outset, and tailoring the builds to our phone a bit better. So if something above really bothers you, it's probably already in the process of being changed or fixed.

TL;DR I would say "yes", it's at daily-driver status, and in fact others in the thread have been using it as such with little or no issue. You should definitely spin up another ROM slot and give it a go if you want to try something new.
[Motorola Droid 4] joojoobee666:
No, it is currently broken. If you install in Stock slot, you WILL be SBFing.
[Motorola Droid 4] maisdoiscorregos:
I am using CM12 in slot stock smoothly.
[Motorola Droid 4] joojoobee666:
Stargo did mention some changes that were made recently (partition names, iirc)that could resolve this problem but they were not tested. This may be confirmation that they fixed the problem :good:
[Motorola Droid 4] tcrews:
I've been using CM12 in the stock slot since Stargo first released it. However I only use it on WiFi as it's not my primary device.
[Motorola Droid 4] sm4rty:
I installed it for testing in stock slot yesterday. Its working really good. No problemes so far.

Thanks for your help.
[Motorola Droid 4] stargo:
Hi,

with the help of [MENTION=1070688]joojoobee666[/MENTION] we seem to have found the fix for VZW data issues and com.android.phone crashes on VZW.

I've uploaded test-builds with the fix to: http://droid.cs.fau.de/cm-12.0/.test/

If you suffer from problems on VZW, please give these builds a try.

Thanks & regards,

Michael
[Motorola Droid 4] jbeazell:
I had to SBF my phone the two times I tried it in the stock slot. Granted, I haven't tired with any builds in the last week and half or so. The device wouldn't even boot into safestrap.

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

I didn't do any long term battery tests, mostly because I didn't like the lag, so I reflashed back to slimkat. The device is fast...when it actually got to doing something. Getting there, however, was a different story. I'd unlock it, and there'd be a full-second delay between the completion of the unlock swipe and the launcher being displayed. When tapping on an app, there as a likewise one-second delay before it would start to open. I often found myself trying to do the same thing twice because it would lag. I hope it was just a governor setting, but I really haven't had the chance to get too far into it before I needed the phone back to work.
[Motorola Droid 4] Septfox:
The problem with installing into Stock is that (as far as I know) there's no way to increase the size of the partitions...running out of space for app data might end up being an actual issue because of the precompiling for ART. On the other hand, using a slot you can plan ahead and make an extra-large Data partition (or alternatively make a normal-sized one and later expand it using nandroiding shenanigans).

I can understand wanting to use the space, but it's less flexible and future-proof than just installing into a slot and getting a bigger SD card to make up for the unusable Stock space.

[MENTION=1070688]joojoobee666[/MENTION] Is there any significance to the minimum CPU frequency being reported as Unavailable in both the CM menu and utility I use? I can manually change it in the latter, the setting will take (for a while), and following that it comes up fine.

How long did you try for?

The build from the 18th was horrendously slow for me at first, worse than previous ones have been when freshly installed. The stock launcher especially was extremely slow to come up, and seemed to redraw itself a few times before finally stabilizing enough so I could use it. It was ridiculous. Once I got into the store and installed my preferred launcher, things were a bit better, but general slowness still went on for a while.

Since then, it's calmed down and is as quick as it should be. I would say flash it, boot it up, get your Google stuff set up if you use them, then just...let it sit on the charger for an hour and do its thing. Once it gets settled, it should be fine.
[Motorola Droid 4] joojoobee666:
Not real sure, as I see no reason to make that any higher. I'm fairly certain it wont help wake the phone quicker. As soon as it needs to do work, if you use the modded it jumps right to 1000 and get's busy.

I've noticed the same thing as well. I found that this is usually caused by some services that are indexing music, video and image files on the SDCard in the background, presumably it's rebuilding the indexes....it hits all of my few thousand MP3's. No small task. I've watched it do that for 10-15 minutes. Usually I just don't pay attention, I know the first boot is slow for a while due to that. Things will eventually calm down just as you have observed.

Unrelated, things look really good for the VZW data fixes for our poor old OMAP4 devices. I'm running a few more tests, but if all goes well I'll post a clean build with no enhancements for testing.
[Motorola Droid 4] Septfox:
Not what I was going for; the phone wakes in about a second anyway (at least, if the keyboard switch is used, no idea how those of you with a power button fare). More than good enough in my opinion.

I was thinking more that the apparently undefined minimum frequency might be screwing with the governor's ability or willingness to jump through the rest of the frequencies in the table properly...but probably not.

While the straight jump to 1ghz is probably best for overall smoothness, have you considered adding in a couple of "classic" governors, to see how they behave? Smartass and its variants come to mind, since they're similar to Interactive.

I've always found it to be the case when freshly booting the ROM, but the build from the 18th was especially bad for it, at least in my experience. The phone was nearly unusable there for a while, it was so slow, whereas previous builds have just mostly had UI chop for a while. Very strange.

-

Flashed yesterday's build this afternoon, a straight upgrade instead of complete wipe for once. No new problems encountered so far. Flashlight's working great, thanks stargo!

Not build-specific, I've noticed a sudden drop in battery charge level when hitting about 30%, going directly to 18%-20%. It doesn't seem to happen (or at least not badly enough to notice) at other levels, always around 30%, on four separate occasions now. It's easy to think "maybe the phone is using more power than expected, and the battery gauge is catching up", but I do wonder if something else is going on. Anyone else notice the same thing?
[Motorola Droid 4] joojoobee666:
I think [MENTION=3457922]stargo[/MENTION] and I finally hit pay-dirt for VZW users. I've thrown together a test build. It's all stock, except I left in my reboot to recovery and on-screen keyboard "fixes". if anyone has a chance to test, let us know if the com.android.phone crashes come back or not. I haven't been able to reproduce, but I'm not 100% convinced just yet, only because I'm somewhat in disbelief it may finally be resolved. ;)

Builds can be located here: http://d-h.st/users/JooJooBee666/Test

Speed-hack kernel mod can be downloaded from here. The last SD-Swap fix I posted should work fine (have not tested to confirm).

---------- Post added at 09:31 PM ---------- Previous post was at 09:27 PM ----------

Adding governors is currently beyond my knowledge level. :(
[Motorola Droid 4] Septfox:
I can verify that the SD-Swap last posted is still working properly as of the build for the 20th. http://d-h.st/vrYu if anyone needs it.
[Motorola Droid 4] joojoobee666:
Updated speed-hacked kernel mod for the new 01/22 builds for those interested - http://d-h.st/OZ7m.
[Motorola Droid 4] Astrobrewer:
Device Encryption

Is there any chance of getting this working? I was really hoping that it would be working in CM12 as I need my device encrypted for access to my work email. I'm sure there are other priorities, but this would be a big help to me. No complaints about this ROM as so far everything seems to be working very well on my Razr Maxx. Thanks.
[Motorola Droid 4] maisdoiscorregos:
[MENTION=1070688]joojoobee666[/MENTION], you could pass the fix informed in your post above for Stargo?
[Motorola Droid 4] joojoobee666:
Stargo is aware of my "fixes", he is also aware that they are simply hacks in the framework, short-term workarounds that cannot be merged with CM. However, I'm sure they will be properly addressed now that the VZW data issues seem to be resolved.
[Motorola Droid 4] maisdoiscorregos:
Thanks.
[Motorola Droid 4] joojoobee666:
I did some digging today and believe there should be a fix coming soon for the keyboard issues. In the meantime, you can fix this yourselves (if you are not using one of my ROMS) by going in to Settings -> Language & Input -> Current Keyboard. Toggle the "Hardware" switch to on, then back off. This will should persist unless installing on a clean slot, or a wipe is done.

Update: [MENTION=3457922]stargo[/MENTION] and I were able to locate the offending code and have issued a fix for review. Hopefully this will be merged to CM soon. In the meantime, use the fix above. :good:
[Motorola Droid 4] jbeazell:
I just installed the 1/22 test build into the stock slot, so far, so good :)
[Motorola Droid 4] rblanca:
Awesome dude!!! Thanks for the info!
[Motorola Droid 4] Septfox:
Looks like it was indeed merged. Has anyone told you guys lately how awesome you are?

Although...

I don't know if there're actually currently three QWERTY models ported to, or you were just being facetious, but either way, I'm saddened by the utter lack of phones with hardware keyboards these days :<

Sure wish a new one - with modern hardware, even, not something tacked together using old stock from the back of a warehouse somewhere - would come out for us power-users. *coughDROID5cough*

-

Beginning with the build from the 18th, I've been starting to have problems with ringtones unsetting themselves or refusing to work when set. At this point, I've moved them from the eMMC to the "internal"/swapped SD card to see if that helps, and it's completely ignoring them---except the Hangouts tones. I wonder if Lollipop needs flags set on OGGs aside from Loop for them to work properly...will pull a few stock ones and see.

Any ideas why it takes so long to open the Recent Apps list? I thought it might be the CPU capping out and taking a moment to chew through it, but monitoring the speed while waiting for it to pop (several seconds sometimes), that doesn't seem to be the case.
[Motorola Droid 4] joojoobee666:
Indeed it was me being facetious by claiming there were only 3 qwerty users total. In reality, I believe there are actually 2 supported devices with qwerty on cm12, xt897 and xt894. However, it turns out that anyone with BT keyboard connected was also affected by the bug so it was much more pervasive than we realized (see the gerrit commit comments now).

Droid 5? At this point I believe it is nothing more than a pipe dream :(.

Haven't noticed this myself, though I haven't changed ringtones in quite some time. Lame? yes. I'll check it out for myself tomorrow.

None yet, but I agree. It it is painfully slow at times.

On a more positive note, [MENTION=3457922]stargo[/MENTION] isolated the failure with reboot to recovery , hopefully this fix will be merged soon as well. :D
[Motorola Droid 4] jbeazell:
I also have issues with my ringtone and notifactions not saving or working. I gave up on that after trying to move them around, and even trying to put them into /system/media.....

My phone seems to also have an issue where it forgets my WiFi network. Its pretty odd. It'll be working, then I'll pick it up 30 minutes later and the WiFi is off with a little exclamation mark. I check it out, and it has forgotten the network. I have to enter the password again. The great news is that the mobile network seems very solid.

My device is also getting stuck with 100% CPU spikes that go on for minurtes. It also seems that the CPU gets stuck @ 800 MHz or something around there. Does anybody have a good monitoring app to recommend to see what's eating the phone? The ones I've tried don't show me the process that is so busy.

I let the phone mostly hanfg out since oi loaded it yesterday, but it hasn't gotten any better. I'm considering taking all my mp3s off it to see if it is the media scanner giving me issues.

Thanks all! You rock,BTW it is truly amazing that you've found a way to keep these old beasts going.
[Motorola Droid 4] MekaByte:
I've had this problem for a while, even in earlier 4.4.4 builds on this phone and stock. I haven't tracked down what's doing it yet, but I suspect it's certain app(s) since the phone tends to work great before I load much onto it. I've tried to use things like Cool Tool, but it only reports weird built-in stuff like loop98, system_server, and zygote using up the CPU. In 4.4.4, it tended to report high I/O, though in these 5.0 builds, I/O reporting doesn't seem to work. I don't have MP3s, but I do have a lot of files in general on the SD card (it's 64GB), so indexing does sound suspicious.