yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] Careless_:
for some reason, none of my apps would even request root access on nightly 9/26

i had to go to that option in developer menu, turn it to app+adb once, and then back to app. then my apps started to request root access.

this was on fresh install, so it could be why your apps aren't writing to files.
[Motorola Droid 4] Septfox:
Even if something successfully added to a script file under init.d, it wouldn't be executed at boot; init.d support is disabled by default in CM11 and CM12/.1.

All init.d is anyway, is...for lack of anything better to compare it to, the Startup folder as you'd find in Windows; it executes scripts within, said scripts try to set things, they are not where settings themselves are stored.

The actual settings are in /sys/module/lowmemorykiller/parameters/minfree and are set as pages rather than megabytes.

The problem is most likely as [MENTION=3179801]Careless_[/MENTION] said, the apps you're using aren't getting root access. On top of that, while the built-in Privacy Guard's SU functionality is adequate, you may want to make your life a bit easier and get SuperSU (also available here in the forums). It's less fidgety and in my experience the prompts for access tend to come up faster/more reliably (whereas Privacy Guard sometimes doesn't bother).

For actually setting stuff, give Kernel Adiutor a try; it's completely free, it can change most settings you'd want to, and will set them again on each reboot if you want it to.
[Motorola Droid 4] Careless_:
Kernel Aduitor and SuperSU are excellent apps.

I did also notice what you said regarding the speed of SuperSU in popping up permission/access toasts for root.

The 9/26 nightly seems to be pretty stable with the previously posted kernel adjustment settings.

I wonder when we'll start to get Marshmallow roms :D
[Motorola Droid 4] Jishkah:
Man, I hope that we get Marshmallow. Like, I can totally understand if the current maintainer(s?) tucker out and drop support, but I really don't want to see this phone die. :( I don't know if this makes any sense, but the phone is old - but at least it's not LG Ally-old. The LG Ally was released when Android was still VERY new, and when the hardware and software were still trying to establish themselves, catch up to one another. The Droid 4 was released when everything was beginning to settle.

It's, like... it'd be like owning a Pentium 4-era computer. Probably has a 1.7 Ghz CPU, integrated graphics, 512 Megabytes of RAM. It's old. Old as balls. Old old old. You probably don't want to run Windows 10 on that computer over a newer computer, but the Pentium 4 "era" is special in that you can. The computer hardware had finally caught up with Windows' system requirements, and Windows' system requirements began to plateau.

The Droid 4 is kind of like that. Relatively speaking, the Droid 4 was released in the "Pentium 4 era" of Android phones. Old enough to show, but new enough to still be able to run what's thrown at it. And that's what I love about this phone. Since it was released just as Android hardware began to plateau, it still has so much more potential.

To be honest, I've actually given some rather serious thought into figuring out what it takes to be a CyanogenMod maintainer for the Droid 4. Lord knows that it's tough, and I'm probably in over my head - I don't even know how to code - but this phone means enough to me, sentimentally speaking, to give me the drive to want to learn. Either way, I don't want to see this phone die. I want to see it thrive, because it still has so much more potential.
[Motorola Droid 4] Septfox:
Ehh, it's not that the Ally is really old - well, it is, but still - what killed the Ally, I think, were 1: no new drivers and 2: radical changes to Android starting with 2.3...that required new drivers. On top of that, it was the days when OEMs were loathe to release ANY sources, so everything had to be hacked together until it worked, then held in place with sticky-tack and a few prayers.

It's too bad, the two efforts I saw at 2.3 builds ran quite nicely considering the hardware, if they had been fully-functional I probably would have used the phone longer.

Fortunately for us, the Droid 4 shares its OMAP4 and various other chips with other, more popular devices. So even as it gets older and older, it'll still be easier to maintain support for it.

I'm hoping for an M build as well, but considering that Lollipop still isn't running anything resembling "consistently" due to the phone's specs, low memory in particular...not gonna hold my breath.

I wouldn't compare the Cortex A9 to a Pentium 4...it's more like a Pentium D. Dual-cored, somewhat refined over its single-core predecessor, but still a hot, noisy thing when you try and push it.
[Motorola Droid 4] Careless_:
dude... the desire z that I have had since its release has had support for almost a decade, and there are still some people pushing the boundaries of what can run on that little device. the Droid 4 has two times the power in every aspect, so I doubt this thing is dead yet.

yes, the newer roms require a bit more electronic balls, but the newer OS's are also somewhat optimized for speed and utility- so there is life left in this little guy yet!
[Motorola Droid 4] joefuf:
Does anybody have any experience with this phone and a broken screen? Just got a little hairline fracture across part of it, but not sure if I want to wait and see if it ever causes a problem.

Has anyone ever had a screen replaced or had an experience with Verizon either repairing or replacing?

Or is my best bet just finding a replacement?
[Motorola Droid 4] Careless_:
I got a mint condition (really!) replacement off ebay for 60 dollars US.

I first bought one that the seller claimed to be 9/10 but it was in maybe 3/10 condition, and wouldn't even turn on or charge. Then I got refunded for that one, and bought one from a better seller and it was truly a 9/10 phone, and cost less- and came with the factory charger, but no SD card (which is ok, because I have numerous cards to use).

It's not worth the headache and chance of breaking other items. They're plentiful on ebay.
[Motorola Droid 4] joefuf:
That's what I'm thinking. I see an eBay seller right now claiming "9.5 out of 10" for $50, but maybe I'll just try to ride this out a few weeks and see what comes up. Got this one in April and it came mint. Definitely the best route to go.
[Motorola Droid 4] Jishkah:
I actually bought a spare Droid 4 off of Amazon, several months ago, just in case my current one bites the dust. It was pretty cheap, and it doesn't look like it's been used at all. In fact, I'm pretty sure that I bought it "New" - in relative terms, at least; I don't remember choosing the "Used" option on Amazon, and I bought it directly from the Motorola Amazon vendor. Of course, it was probably sitting in a warehouse for several years, but it came with the charger, manuals, and the phone, itself, in a blue EcoMoto box. Looks pretty legit.

Seriously, go for it. Droid 4 phones and accessories are still rather plentiful, so I'd pick up what you can before you begin to see less of them, if I were you and had the extra cash.

EDIT: Nvm; it wasn't cheap. More like $127. Totally worth it, though.
[Motorola Droid 4] Careless_:
i'd rather pay $150 for a brand new droid 4 than any other phone right now. Can't take the qwerty away from me! :highfive:
[Motorola Droid 4] daniel_m:
Same here! Well, throw in some decent hardware and increase the price to 300-400 ;)

A shame that not even Blackberry gets it right ... who wants to have a portrait slider?! :D
[Motorola Droid 4] Puppymang:
its really not worth it going through verizon for repairs. they use some 3rd party company that will send you something "equivalent" because i dont think they have any droid 4's left

back when i had a droid 3 with "insurance" i was dumb enough to ask them for a replacement because the slider function was messed up and pretty much crashed the phone every time i slided the keyboard. paid 100 dollars for a refurb droid 3 with a keyboard that was poorly glued on and came off after 20 minutes of use

when my first droid 4 died i just went to ebay but its pretty much a lottery. they sometimes sell you ones that are all scratched up or partially functional so it took me about 3-4 weeks to get a decent droid 4. if you buy from those major sellers chances are youll get a really used up one that wont last very long so try to be careful
[Motorola Droid 4] joefuf:
Yeah, that's my hesitation with Verizon as well. After I got my Droid 3, I sent my OG Droid in to Assurion or whatever that third-party you mentioned was. Similar results, so I couldn't even sell it.

It's functioning so far, so I figured I would just check every few hours until I see someone put one up that's mint or close. Unicorns are out there.

Not that ROMs aren't fun, but I would pay full price for a Droid 5 at this point... Conversation for another thread.
[Motorola Droid 4] Jishkah:
Hey, is anybody else having WiFi issues with the newer Nightlies? I've noticed that my saved WiFi networks don't persist across reboots. Which isn't really a big deal, since I have unlimited data, but I've noticed that this has been happening for a month or so, and I haven't really seen anybody else bring it up.

On that note, does anybody know of a fix? It seems to be somewhat hit-or-miss, too.
[Motorola Droid 4] aczlan:
No issues with saved WiFi networks here.

However, if I do a "soft reboot" its like the WiFi hardware is missing. WiFi is turned off and will not turn on unless I do a "hard reboot" of the phone.

Aaron Z
[Motorola Droid 4] rpadula:
Having issues too!

i'm under the impression that i'm losing my wifi passwords also when the phone sleeps. it never comes back connected...
[Motorola Droid 4] stargo:
Hi,

I've posted this over in the Razr-thread:

I'm not using the D4 as my daily driver anymore (which doesn't mean that I want to drop support for it), but I'm using a Photon Q. It's also a great keyboard-phone which natively works on sprint and with a bit of hacking on everything except for Verizon.

Hmm, sounds like a permission-problem in /data/misc/wifi. Try renaming that folder and rebooting the phone, this should recreate it with the correct permissions and you should not lose your passwords after that anymore (hopefully).

Best regards,

Michael
[Motorola Droid 4] Jishkah:
Cool beans. I'll try your suggestion when I'm at home. Thanks, man.

Anyway, yeah. I don't know. About the 12.1 Snapshot, I mean. For me, anyway, I don't so much mind performance being factored into Snapshot status as I do the amount of bugs - so far, I haven't noticed any crippling bugs. The WiFi issue is the only bug that I've seen (or remember seeing, anyway) since installing 20151006's Nightly. The only other issue that I can think of is the timeout in installing certain apps (Facebook comes to mind), but adding the WatchDog string to build.prop seems to fix it - it's definitely a hack, though, 'cause it can cause the phone to soft reboot on especially strenuous app installations.

Like, CyanogenMod 12.1 works very well, out of the box, but most of the performance problems pop up when I begin to install some apps. Personally, I think that it's ready for Snapshot status, if only because most of the bugs have been ironed out. Performance isn't quite there, sure, but I don't really factor that in to whether it's ready for a Snapshot or not.
[Motorola Droid 4] aczlan:
IMO, its not too bad.

I run it as my DD, its not as fast as a new phone that's designed for Lollypop, but its better than my previous phone (TouchPro2 with WM6.5) and its faster than stock was (pre-bloat removal).

Aaron Z
[Motorola Droid 4] Jishkah:
So I renamed the "wifi" folder in /system/etc/ to "wifi.old", and then reset the phone. I don't think that it worked - the WiFi was turned off, completely, and I couldn't turn it back on. I'm going to do another reset, and hope for the best.

Did I need to rename it back to "wifi" before resetting the phone, or does the act of renaming the original folder prompt Android to automatically generate a new wifi folder with the proper permissions?

EDIT #1.): Oh **** I just realized that I renamed the wrong folder. ABORT MISSION ABORT ABORT ABORT

EDIT #2.) It didn't work. I renamed the correct folder, reset the phone, connected to the WiFi network, reset the phone... it didn't persist, unfortunately.

I took a few screenshots of the folder/file permissions, if you wanted to look at them. Should I change anything?
[Motorola Droid 4] Septfox:
I think the problem is that Snapshots are supposed to be fit for public consumption, whereas nightlies are automated, sometimes experimental-to-see-if-anything-breaks builds that you go into sort of expecting to be slightly wonky somehow.

Or to put it even more simply: nightlies are beta, snapshots are supposed to be more or less finished product.

Being apparently bugfree isn't quite enough in this case. You don't really want the common user to plop CM12.1 on their phone and expect it to run as well as JB, only to have it not do so as soon as they load some apps, primarily because of the memory situation. They then come to the forum to complain about it, get two or three people who tell them various ways that they can make it a bit better, get frustrated when the boost in performance isn't large/consistent enough and decide to flash KitKat or worse, JB. If that happens, then everyone's time has been wasted and little to no good comes of it.

I agree that the performance is adequate when things like joojoobee's kernel is installed and minfree limits messed with. It definitely feels like a phone that's running a version of Android several versions newer than intended...but it's adequate. Straight out of the box, on the other hand, I wouldn't recommend to anyone without knowing they're up to applying a bit of elbow grease.

And please, nobody take me the wrong way here: I cannot fault anyone who has worked on getting Lollipop to its current state, and in fact would like to extend a general Thank You to everyone who has helped make it what it is; stargo in particular.

We're just...starting to hit the limits of what the hardware itself can actually do, I guess, and there's nothing wrong with accepting that if it comes to it. The phone was originally intended to run ICS, after all, and that was ages ago in Android development.

[MENTION=3457922]stargo[/MENTION] a couple of questions, if I may:

Out of curiosity, what is our biggest bottleneck currently? Are we lacking in processing power, disk bandwidth, memory bandwidth, or is it just a general overall "everything is getting constantly maxed out and waiting on each other"?

Why is there such a crippling amount of performance loss when available memory starts approaching the 170-180mb range? That's quite a large chunk of memory we can't use because dipping into it brings the system to its knees...
[Motorola Droid 4] Jishkah:
So I don't know if double-posting is allowed, but I just wanted to bring to attention that I (think that I) fixed the WiFi. Um... I don't know what's different, this time around, but I basically repeated the "delete folder, reboot, reconnect" procedure a few times and, as far as I can tell, it worked. The WiFi credentials persisted across reboots. Now, I've only rebooted once, so I don't know if it'll stick, but it's still good news!
[Motorola Droid 4] stargo:
If I knew that, I would be really happy because I could fix it. I assume it's all of that mixed.

Running on an ext3 fs in a file on a fat-partition which doesn't allow trim to work doesn't help...

Because the (Java/ART) garbage collector tries really hard to free up every bit of memory and takes a very long time, instead of the system just killing the biggest memory hogs. But all changes made to the LMK mad this even worse :(

Best regards,

Michael
[Motorola Droid 4] Septfox:
Mm, and running it "properly" out of the stock partition isn't any better, what with lack of TRIM there...

Sorry, I should have been more specific.

Using Cooltool to monitor memory and setting the minfree settings very low (single-digit ranges) to allow memory to fill, there is a definite hit to the phone's performance when it drops below 200mb of memory free, getting exponentially worse towards 100mb free where the phone basically becomes unusable as kworker:0, 1 and 3 take turns sitting on the CPU, and after a while it all just gives up and hot-reboots.

As long as the reported free memory stays above 200mb or so, performance is decent to good, but this effectively locks us out of a quarter of our physical memory. Is the garbage collector running constantly regardless of whether it needs to or not, and steadily gets more aggressive as physical memory runs down irrespective of the minfree settings? Or is there some other mechanism at work here that I'm not getting?
[Motorola Droid 4] joefuf:
Addressing this part, I've noticed that I run up against a wall in regards to allotted app space. We seem to have only 3GB for apps, their data, and their cache. I have plenty of space on the internal SD on the phone, but no way to partition it, as far as I have found.
[Motorola Droid 4] Jishkah:
What I ended up doing was to transfer apps over to the SD card after they were installed. I'd swap from the Play Store to the Applications menu, back and forth, transferring apps to the SD card and then installing new ones, and so on and so forth. Watch out, though - the installation process WILL eat through your Cache. You'll probably need to clear it a few times (via the Storage option in Android's settings, not SafeStrap) to be able to get everything installed properly. When I was downloading and installing all of my apps (a good 77 of them, I think), the system Cache ballooned out of control - I had to go in and manually clear it every once in a while to have enough space for additional apps.

I don't know why the maximum partition size is ~3GB, however. I'd assume that it's either an inherent limitation with how the virtual partition system works, or just a quirk with Safestrap, in general. Either way, it doesn't help that a good chunk of the internal storage is reserved by the stock Android operating system.
[Motorola Droid 4] joefuf:
I've done this as well. It doesn't appear that every app is able to be run off of the external SD card. I have heard of App2SD which will let you move those that don't give you the option, but they caution instability and other issues can occur. But correct me if I'm wrong. Or if anyone else has a solution, that'd be great.
[Motorola Droid 4] Careless_:
been having random restarts with 09/25 or even random lockups.

I thought it was my battery acting up again. sometimes it will seem like the phone just turns itself off, and my usual fix is to loosen and retighten the battery terminal torx screws... but that's not the case this time.

it seems like the phone goes into a super dead state, but it's not off. it just doesn't wake for like 10-20 minutes. and when it finally does, one of two things happens:

1) it will just resume like nothing was wrong.

2) it will soft-reboot.

it's not a hard reboot, as i don't see the motorola logo come up, it just goes right into scenario #2 with the cyano boot animation.

weird. I'm going to attempt to go to a different kernel for a week or so.

it doesn't happen often- but two of the 5 or 6 times it did, it was when I really needed to use the phone. And it can't be turned off when it's in that mode, for some reason.
[Motorola Droid 4] Septfox:
[MENTION=3179801]Careless_[/MENTION]

Do you have hotplugging turned on? If so, try turning it off with Trickster or Kernel Adiutor and see that helps.

I don't know why it would suddenly be an issue, but I was getting random reboots while the phone was sleeping; it seems a panic would result on the occasion that something woke the CPU at just the wrong time. I'd imagine the issue would be more prevalent for someone who uses their phone more actively (due to more wakes).

When it was happening to me, though, the symptoms were slightly different. I never had super-slow wakes, I would usually just woke up in the morning to find the phone had rebooted itself at least once overnight. So it might not actually be whatever problem you have.

[MENTION=3457922]stargo[/MENTION]

I've been reading a little bit, and among the things that official ART brought was a new garbage collector, right? Said garbage collector has a compacting routine to shift things around to make contiguous free memory.

I would assume it was designed with much newer, more powerful devices in mind, where any overhead created would probably go unnoticed...is it possible that all the shuffling going on in memory is having a significant impact on performance?
[Motorola Droid 4] Careless_:
Do I turn off IntelliPlug?
[Motorola Droid 4] Septfox:
Yup.

In the JBX kernel I think it would make it fallback to mpdecision, but in joojoobee's, it disables hotplugging completely.

Keep in mind, if using Kernel Adiutor, disabling it will also make most (all?) the other options on the hotplugging page do nothing, so if you count on any of them, you'll have to find alternatives...
[Motorola Droid 4] stargo:
[IMG="D4 CM13-1"]http://xdaforums.com/attachment.php?attachmentid=3505369&stc=1&d=1444750548[/IMG]

[IMG="D4 CM13-2"]http://xdaforums.com/attachment.php?attachmentid=3505370&stc=1&d=1444750548[/IMG]
[Motorola Droid 4] daniel_m:
Holy sh*t! :D

With all the Xposed trouble on 5.x, I might actually wait for Android 6 and live with CM11 for the time being :o
[Motorola Droid 4] stargo:
Hi,

let's see how well this works out...

Currently working: display, touchscreen, wifi, external sd, camera a bit

Not working at least: phone, audio, power button, internal sd

Best regards,

Michael
[Motorola Droid 4] dreikk91:
why we did not use the filesystem ext4. I format the data in ext4 and slightly changed FSTAB and safestrap ss.config (not sure what it need), and it worked well

By google translate
[Motorola Droid 4] Bobcus Leper:
I think that I just cried, and laughed with joy!

Wow! You are awesome stargo!
[Motorola Droid 4] Shani Ace:
That's it, I'm done with CM12 on the D4! I'm gonna downgrade now.

In the last months I haven't used my phone for anything else than calls, sms and emails (and occasionally music and comics) because it's just too unresponsive for anything else. So my D4 basically isn't even a smartphone anymore, it's just a regular phone. Even if I don't use my browser or any other app, it still freezes regularly. Then it either comes back after some minutes or it reboots and apparently loads a backup (it says "updating Android app x of 120). Besides, the phone always forgets my Wifi password and sometimes the Wifi doesn't work at all. Photos also never got saved on the microSD, so I had to change the save location to storage (exactly what I didn't want, I wanted the camera to store on the SD) It's just so annoying, I'd like to throw the phone at the wall or just smash it for not responding for several minutes. Every time I really need my phone to work, it just doesn't. Or when I try to download an email attachement (or download something from the browser), it says download finished but then the download folder says it's empty! And since a few days, I can't even access the SD card via USB on my PC. Today the phone even didn't work at all for about an hour before it responded with loading a backup again. It's so frustrating! I really came to hate my phone because of all of this.

I don't even remember what the differences between CM11 and CM12 were (aside from the Do-Not-Disturb-mode, which was the main reason to get CM12 in the first place - and if I remember correctly, Privacy Guard already existed on CM11, right?), so now I'll just go back until the Android Blackberry phone is out, or Project Ara with a keyboard-module or maybe I get a magnetic keyboard case for the Galaxy S5 and buy that phone someday.

It's just such a pity since the keyboard of the D4 is so awesome. But what good is it if I can't use the phone.

I just hope I don't run into any trouble while downgrading (stock slot).