yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] daniel_m:
With the Xposed framework coming to Lollipop I was wondering if we could get XPrivacy to work on our Droid 4. According to Marcel (M66B), we should be able to use XPrivacy because, to my knowledge, Cyanogen has SELinux running in permissive mode. If not, we would have to modify the kernel image in order to register XPrivacy as a service. Since the bootloader of our device is locked, could this be done with Safestrap?

Here are detailed instructions and Marcel's post on XDA.

Trouble with Xposed on Lollipop is still holding me back from updating. And I would never want to use a phone that cannot be protected by XPrivacy. Are there any adventurers here that started to fool around with Xposed on CM12?

---------- Post added at 11:48 AM ---------- Previous post was at 11:38 AM ----------

Your logs are very extensive, do you know the time and date when you called your phone?
[Motorola Droid 4] mo0n_sniper:
I'm calling from 0761668XXX.

I compared the call logs on the phones and I have this:

Galaxy: 2 phone calls at 11:03, 2 phone calls at 11:04

Droid: 2 phone calls at 11:03, 1 phone call at 11:04

So one call at 11:04 rung only on my Galaxy and not on Droid.
[Motorola Droid 4] Puppymang:
if i use cm12 how can i "unroot it"? im assuming this comes pre-rooted
[Motorola Droid 4] Oggie7797:
.......why would you want to unroot it? That defeats the purpose of flashing an aftermarket rom...
[Motorola Droid 4] Puppymang:
there are multiple reasons for using an aftermarket rom (especially for a device thats been abandoned by their makers) and while i would prefer having it rooted there are apps i use that don't run on rooted devices and there is no rootcloak for 5.0 yet
[Motorola Droid 4] sd_shadow:
Cm 12 is Rooted, but default is limited

You can change root options in developer options
[Motorola Droid 4] Oggie7797:
Well cm12 has a joke of a root management system so just flash supersu, it runs in ghost mode.
[Motorola Droid 4] joojoobee666:
Definitely NOT permissive mode. Devices are not official in CM until SELinux is enforced. Nightlies won't even compile without it enabled.

That makes it easy. This is simply a new RAMDISK for us, no new kernel necessary. Since we use KExec, we can easily replace this (/system/etc/ramdisk.img). Here's a new SDSwap Zip which also adds Xposed SELinux policy and one without the swap that simply adds the Xposed support:

02-18 D4 SDSwap with Xposed support

02-18 D4 Xposed support
[Motorola Droid 4] Septfox:
Anything further on this?

I literally knew nothing about it, and information on Google for this particular application of loopback seems to be scarce, but from what I gather it has to do with mounting files as devices. Is this correct?

Assuming so, our slowdown comes from mounting slots (or rather the partition files in them) as loopback devices instead of "real" eMMC partitions?

So, er...wouldn't solving the problem be as simple as installing to the stock "slot", what with it being the real thing and not a virtual device?

Am I making any sense here, or just making myself look like an idiot? : \

also questionmarks
[Motorola Droid 4] joojoobee666:
Basically, that is all correct. The "slots" are actually just files on the internal SD that are mounted to a loopback device from SafeStrap (system, data and cache partitions). And yes, there are some performance losses doing it this way, though I cannot really say how much(they may be almost nil) since I've never benchmarked anything. It also prevents TRIM from running since it's on an SD and Android doesn't do TRIM for vfat.

The stock slot does not use the loopback so any losses caused by running through loopback would not be present. However, flashing anything to the stock slot is risky. The stock kernel (which is loaded by the stock bootloader first before safestrap runs) needs to have valid data in the system partition, particularly all the kexec files in /system/etc/kexec in order to boot. If anything goes wrong there, you SBF again.
[Motorola Droid 4] Septfox:
It does sort of beg the question "if it's such a serious problem with our eMMC, why hasn't it been brought up more?". As far as I've seen, most if not all users install to stock simply because of the space savings over making a slot, not to avoid a performance loss.

Worries of prematurely wearing out the flash aside, wouldn't lack of TRIM itself introduce a sporadic loss to write speed?
[Motorola Droid 4] rblanca:
Wouldnt be better if someone implements fs2ps partition support? Maybe it helps a little...
[Motorola Droid 4] joojoobee666:
My original statement wasn't entirely accurate. The internal SD never had TRIM support to begin with as it is not supported on vfat (thanks for clarifying [MENTION=3457922]stargo[/MENTION]). So running from the internal SD just won't see the benefit. Premature death? Well they die when they wanna die anyhow...
[Motorola Droid 4] daniel_m:
Wow, thanks a lot! I don't think I will test this before Marcel is back from his trip, but it is awesome to know that our droid will live for a little while longer :D
[Motorola Droid 4] joojoobee666:
I haven't tested it myself. However, as long as this is the only change needed I don’t see how it won't work.
[Motorola Droid 4] MekaByte:
I've found build performance extremely erratic -- sometimes it runs great, but most of the time system_server and loop98 seem to lock everything up. I'm not sure if there's a particular app that does it, as I see it just running Google apps (Google Hangouts seems to be the worst). What I find works well though is to just totally disable background processes in advanced settings. This seems to prevent/reduce memory contention and the phone becomes usable again. Yes, each app has to reload when you switch between them, but I find this is actually faster than letting the system try to manage memory caching. Unfortunately, this setting doesn't seem to be preserved between reboots.
[Motorola Droid 4] sm4rty:
i flashed the rom yesterday and it rendered my device useless... like a huge piece of paperweight....

is it normal that it hangs and stutters? when im using the browser nearly nothing else is possible.

after taking a photo its a pain to get the gallery opened. gestures and keypresses are recognized seconds after pressing...

is there some fix for it?

i have nightly 19.02 installed, wiped all (cache, data, system, dalvik cache, android.secure) before installing the rom.
[Motorola Droid 4] joojoobee666:
New Kernel changes (dealing with low mem situations) was merged in. Here's a new speed-hack kernel with these changes and another link to the SDSwap fix, the same one I posted with the Xposed support, but this is just fine to use whether you use Xposed or not:

02-20 - Droid 4 Custom Kernel with Speed Mod

02-18 - Droid 4 SD-Swap
[Motorola Droid 4] welder73:
Can you make one for us with Razr XT910/912?

Sent from my Razr XT910
[Motorola Droid 4] joojoobee666:
The kernel is the same for the Razr and D4, however if you were looking for the Xposed or SDSwap, that's going to be different for each device. I can compile one if you'd like. Just let me know which device (umts or not) and if you wanted the sd swapped around.
[Motorola Droid 4] welder73:
No,I just want kernel with speed hack.

So,I can flash this one? :) (Umts here)

Btw,did you took something from this?

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

Sent from my Razr XT910
[Motorola Droid 4] sm4rty:
yeah thanks for this kernel :) now i can use my phone :)
[Motorola Droid 4] joojoobee666:
Yeah, you should be able to flash that zip. Alternatively, just put the kernel file in place over the one on the device in /syste/etc/kexec and reboot, just make sure the permissions are the same. (may not be necessary but just to be safe).

And no, nothing from there. It's just a simple mod of the frequency table, cutting out 600mhz and 800mhz, so it goes straight from 300mhz idle to 1ghz and 1.2ghz to help combat some of the sluggishness.
[Motorola Droid 4] welder73:
I replaced the kernel and changed permissions but I had lags all the time,strange...

No big deel,I tried it,thanks for your effort :)

Sent from my Razr XT910
[Motorola Droid 4] rblanca:
It's seems that beginning to use it on our omap4! or i'm wrong?
[Motorola Droid 4] Sensonic:
I dunno whether this has already been covered here but Folder Mount app doesn't seem to work with CM12 :(

I starts to check whether the phone is rooted and stays there. So what gives and what to do next???
[Motorola Droid 4] Cyber-Logic:
Man, so happy to see that the Maserati is still getting official CM support. :)

Can someone tell me how the latest CM12 nightly is? Any issues/bugs?
[Motorola Droid 4] Sensonic:
Anybody else experiencing the same thing:

My phone won't flash the updates automatically :(

When I had CM11, I just had to click "update" and the phone booted and updated itself. Now with CM12 I have to do it manually. Anything I've missed during the installation procedure?

Edit: another issue: KBR.zip which enabled "scandinavian letters" in CM11 (i.e. ä & ö etc.) doesn't work with CM12 :( Any cure for that?
[Motorola Droid 4] sm4rty:
yep. i had the same problem too. but where is the problem to chose the downloaded file from cmupdate folder?
[Motorola Droid 4] Septfox:
Try updating to at least yesterday's (20150224) nightly, it should eliminate the excessively long hangs. Seriously, it's worth the few minutes to flash it.

---

Some WIP CPU governor tweaks, if anyone is interested. They'll cause the frequency to ramp up more aggressively, and hang there slightly longer, with the intention of improving responsiveness and smoothness somewhat at the cost of (probably) higher battery usage when not idle.

I personally use Device Control to apply the settings, but any utility that can change governor settings should work.

I've been messing with it on the normal kernel, but there should be no issues using these settings with joojoobee's tweaked kernel since it uses the same governor (the 600/800mhz settings will be ignored, or simply don't enter them).

Again: WIP. I won't guarantee that they'll make your phone run any better. Some operations, like cold-starting apps, are still also limited by storage speeds.

target_loads
98 300000:40 600000:50 800000:55 1000000:60 1200000:70

above_highspeed_delay
20000 800:10000 1000000:25000

highspeed_freq
300000

go_highspeed_load
99

min_sample_time
150000

timer_rate
20000

timer_slack
80000

boost
0

boostpulse_duration
80000

Hope it helps.
[Motorola Droid 4] joojoobee666:
Yeah, hangs were gone with latest nightly. As far as the mods, I've been playing with those myself as well. I'm currently using go_hispeed_load of 65 and just a flat out 35 for target_loads.

Also, here's a new kernel. Gonna need this with the new nightly, otherwise I expect surfaceflinger to be seg faulting ;)

02-26 CM12 Custom Kernel with Speed-Mod

Nothing has changed to warrant a new D4 SDSwap patch.
[Motorola Droid 4] joojoobee666:
And in case anyone is brave enough...

Thanks to some assistance from [MENTION=3457922]stargo[/MENTION] and [MENTION=4243514]Hashcode[/MENTION], I was able to get an overclocked kernel created. It's currently OC'd to 1.3Ghz. All other frequencies are still present, including 1.2 currently. Anyone brave enough to try it and let me know how it goes for them, head over to this thread: http://xdaforums.com/droid-4/development/5-0-custom-oc-kernel-t3041512. I don't want to clutter up this thread for something like this.

I've only been running it for about 2 hrs or so, which means I haven't seen how much of an impact it has on battery, though I'm sure it does since 1.3 requires slightly more voltage. I'm showing an increase of about 30% on CPU Prime Benchmark. Scores went from ~1600 to ~2050. So far, no other issues I've seen....yet.
[Motorola Droid 4] moodroid:
Apologies for being a little off-topic, but does anyone know anything about allowing non PIE binary files to work?

I've got an app that won't work on CM12, and apparently it might be possible to flash something that will allow non PIE binaries to work, but I'm not really sure what I'm looking for.

Thanks
[Motorola Droid 4] mifritscher:
Hi,

just installed the latest nightly from http://www.cmxlog.com/12/maserati/ - using the extended Safestrap 3.75. Now it hangs at the boot animation. I upgraded from Cyanogenmod 11. I additionally installed the google apps from http://wiki.cyanogenmod.org/w/Google_Apps and the gsm-patch.

I get a connection via adb. logcat says:

...
E/Whisper ( 160): No Vectors installed (errno = No such file or directory)
E/Whisper ( 160): Failed to open file (errno = No such file or directory)
E/Whisper ( 160): accyAuthInit() failed
...
I/Cryptfs ( 157): Check if PFE is activated on Boot
E/Cryptfs ( 157): Bad magic for real block device /dev/block/userdata
E/Cryptfs ( 157): Error getting crypt footer and key
...
D/BootAnimation( 196): Use save memory method, maybe small fps in actual.
I/BATTD ( 159): Event from SBCM Driver=Coulomb Counter Calibration Interrupt
W/sh ( 201): type=1400 audit(0.0:8): avc: denied { getattr } for path="/system/bin/logd" dev=loop99 ino=32839 scontext=u:r:shell:s0 tcontext=u:object_r:logd_exec:s0 tclass=file
W/sh ( 201): type=1400 audit(0.0:9): avc: denied { getattr } for path="/system/bin/logd" dev=loop99 ino=32839 scontext=u:r:shell:s0 tcontext=u:object_r:logd_exec:s0 tclass=file
W/sh ( 201): type=1400 audit(0.0:10): avc: denied { getattr } for path="/system/bin/logd" dev=loop99 ino=32839 scontext=u:r:shell:s0 tcontext=u:object_r:logd_exec:s0 tclass=file
<hangs>

ps shows:

...
logd 153 1 13220 1412 ffffffff 00000000 S /system/bin/logd
root 154 1 3692 324 ffffffff 00000000 S /sbin/healthd
root 155 1 4396 1148 ffffffff 00000000 S /system/bin/lmkd
system 156 1 3300 652 ffffffff 00000000 S /system/bin/servicemanager
root 157 1 9720 1932 ffffffff 00000000 S /system/bin/vold
system 158 1 62708 22912 ffffffff 00000000 S /system/bin/surfaceflinger
mot_accy 159 1 3284 700 ffffffff 00000000 S /system/bin/battd
root 161 1 3124 532 ffffffff 00000000 S /system/bin/uim-sysfs
root 165 2 0 0 ffffffff 00000000 S pvr_workqueue
root 170 2 0 0 ffffffff 00000000 S kauditd
root 182 1 2564 256 ffffffff 00000000 S /system/xbin/su
shell 183 1 8788 404 ffffffff 00000000 S /sbin/adbd
root 188 2 0 0 ffffffff 00000000 S omaplfb
graphics 196 1 45076 27084 ffffffff 00000000 S /system/bin/bootanimation
shell 201 183 3188 756 c00a88c8 4018f8ac S /system/bin/sh
shell 210 201 4476 940 00000000 4015e5dc R ps

df:

Filesystem Size Used Free Blksize
/dev 418.0M 56.0K 417.9M 4096
/sys/fs/cgroup 418.0M 0.0K 418.0M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt/asec 418.0M 0.0K 418.0M 4096
/mnt/obb 418.0M 0.0K 418.0M 4096
/ss 8.0G 7.3G 682.9M 8192
/system 881.9M 687.0M 194.9M 4096
/data 3.0G 1.7G 1.2G 4096

I don't see any obvious error...
[Motorola Droid 4] joojoobee666:
Try this here. I haven't tried it myself. http://xdaforums.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731
[Motorola Droid 4] Marky__Mark:
Installed this kernel on 2/24 nightly and it doesn't even boot.
[Motorola Droid 4] Septfox:
Why would you expect a kernel meant for 02/26+ to work on the 02/24 nightly?
[Motorola Droid 4] Marky__Mark:
Because you didn't include the "+". Your post was responding to the 2/24. It took you 2 days to make the kernel for 2/24. Valid reasons...

---------- Post added at 10:16 PM ---------- Previous post was at 10:08 PM ----------

My bad. I was giving you credit for building the kernel. Thanks for your input!
[Motorola Droid 4] Oggie7797:
Read what he said:

"Gonna need this with the new nightly, otherwise I expect surfaceflinger to be seg faulting"

Kernel was for 2-26.

Your rom was 2-24.

Just throwing that out there, take it or leave it.
[Motorola Droid 4] joojoobee666:
You are correct. This kernel is ONLY for 2-25 and later due to changes in DSS (Display Sub System). I would suspect it would not boot on older nightlies, just as I would suspect the older kernels would not boot on the newer nightlies.
[Motorola Droid 4] Marky__Mark:
Yep. Running great on 3/1!
[Motorola Droid 4] mifritscher:
Same problem with nightly from yesterday. I had enabled root for adb, but again didn't see anything important in the logs. It seems that surfaceflinger hangs somewhere. How can I debug this?
[Motorola Droid 4] Puppymang:
i finally decided to give this a go (03/01 nightly with OC kernel) and there were a few problems that made me go back to cm11

1. no data connectivity. calling worked but data just gave me a ! sign and a disconnected state this happened on both 3g and LTE on verizon wireless

2. rootcloak didnt work but thats not really related to the rom itself. the module hasnt been updated in ages so i had low hopes in the first place.

2. setting root access as disabled didnt "hide" the root and i was unable to use the apps that require rootcloak

the extra colorful and bright menus really aren't my thing so it looks like im not quite ready for lollipop
[Motorola Droid 4] L3ibnitZ:
Any news about miracast support?

Sent from my XT910
[Motorola Droid 4] rblanca:
Nothing since this commit http://review.cyanogenmod.org/89776 , but i don't know if it's currently on development...
[Motorola Droid 4] joojoobee666:
Some changes in the device tree warrant a new SDSwap. Not REQUIRED, it enables KSM and makes some changes to the way the kernel handles flash storage. Basically performance enhancements. I also included an updated version without swap for those who want Xposed support. If you don't want SD swapped nor Xposed, then neither are for you. However, even if you don't plan on using Xposed, the SDSwap works just like normal. Support for it is simply there if you would like to use.

03-04 D4 SDSwap with Xposed support

03-04 D4 Xposed support (No swap)
[Motorola Droid 4] Puppymang:
well i tried again with the nightly from 03/04 and i still have no data connectivity. when i booted up the phone for the first time after flashing it said "unrecognized sim" for about 10 seconds then it went away and it got service but no data
[Motorola Droid 4] Oggie7797:
Make sure you have the correct network settings. I tend to prefer cdma+LTE and then I use RUIM instead of NV.
[Motorola Droid 4] stargo:
I'm pretty sure it's caused by http://review.cyanogenmod.org/#/c/85595/ which is fixed by http://review.cyanogenmod.org/#/c/90558/ in the next nightly.

Cheers,

Michael
[Motorola Droid 4] Puppymang:
the description on that says that it hangs on 1x or 3g or that airplane mode might help but i was unable to get 1x or 3g.. no data at all just a !

in any case im strongly considering going to the verizon store to try and get my sim replaced because on cm11 it takes about 30 seconds after its fully booted for my phone to read the information off the sim (prl, iccid, phone number, etc) they just appear as unknown for a while.

i just tried again with the same nightly using the suggestion of changing to cdma+lte/evdo and ruim/sim but still no data connection just a !
[Motorola Droid 4] joefuf:
Sort of random/off topic, but has anyone ever been able to figure out call recording on the Droid 4? I've tried a bunch of apps and the CM Call Recording feature, but I haven't had any success.
[Motorola Droid 4] joojoobee666:
It's definitely the cause of data issues for VZW users. If you would like to use, edit the Verizon Internet APN, and set the APN type to "default,dun,supl" then save. Your data should come right up. As stargo mentioned, this will be resolved in the next nightly anyhow if you just want to wait.
[Motorola Droid 4] Puppymang:
okay i changed the apn type to what you said and data works now.

guess ill mess around with this a little more

thanks

edit: unfortunately my data drops are still present in 5.0 but i guess the rom isn't at fault here

also the keyboard seems to not wake up the device like it does on cm11 and i tried the custom layout mod but it doesnt do anything. hopefully this gets fixed/changed in the future although i guess its not a major problem

oh and one last note: when i linked my google account to the phone it did a soft reboot but im not sure if this is a bug or if its related to the test kernels ive been using from joojoobee666. i wasnt really looking after i put in my information i just let it load and when i looked back it was doing a soft reboot
[Motorola Droid 4] Septfox:
Are you referring to the slide sensor not waking, or individual keys not waking it?

The former should definitely be working, if it's not there's something wrong. The latter requires WAKE being added to the line of every key you want able to wake the phone in omap4-keylayout.kl, but I'm not sure it's working properly (every time I tried in earlier nightlies, it'd cause a bootloop).
[Motorola Droid 4] Puppymang:
oh sorry i meant individual keys. i usually have the keyboard out so i didn't pay attention to the sliding but im pretty sure that works just fine
[Motorola Droid 4] NicoDJ:
Slow

Today I installed CM12 on my droid 4. Everything seems to work, but at such a slow speed that it is not realistic to use the phone for normal use.

Did I do something wrong, will the speed be improved over time, or is it just not realistic to expect 'normal' performance of Lollipop on such an old device?

Btw CM11 has always performed fine but I was hoping to improve on battery live

Thanks,

Nico
[Motorola Droid 4] Septfox:
[MENTION=1599791]NicoDJ[/MENTION]

The phone will be slow for a while after the ROM is first installed; it should speed up once it settles in. Probably not a bad idea to just leave it on the charger for a bit and let it sit, doing its thing.

That said, it's not quite as fast (or, not consistently fast) as CM11 or other KK-based ROMs yet. Joojoobee's kernels help, even the non-OC one, and a few pages back you can find some sysctl tweaks that may help if you're running from a ROM slot.

Battery life is decent to good, seeing around 0.7%/hr standby consumption with wifi on and only Google stuff syncing, naturally it'll go up as you add other things that wake to sync and/or use mobile data instead.
[Motorola Droid 4] NicoDJ:
Thanks Septfox.

The phone seems to get faster indeed and battery-life looks promising.

I'll just install some stuff and try it out for a while.

I'll have a look at the tweaks you mentoined.

Thanks!
[Motorola Droid 4] Septfox:
Hmm.

I had my copy of the 04 nightly working fine in Stock, until I tried to reboot the phone this morning. Same result; it got stuck at the bright screen after the Kexec buzz. After trying a variety of things to get it to boot again, including flashing a stock nandroid (which booted perfectly), finally ended up leaving my current data in place, wiping /system/ and reflashing the ROM, which screwed up Play Services, necessitating a Gapps reflash, which...doesn't seem to have completely fixed the problem, since I'm no longer getting GCM pushes. Sigh.

Safestrap's also been acting very weird today; unable to change slots off of Stock (it resets on reboot...at least, prior to getting CM12 fixed, haven't tried it again), unable to flash Gapps from the first post (seemed to "crash" SS, screen goes black for a moment then returns to main menu, finally went and got PA Gapps), ROM flashing taking longer than usual...

The only thing that's changed is Daylight Savings coming around, so maybe that's screwed with something. Or perhaps it's completely coincidental. Who knows. It was an incredibly annoying morning, in any case.
[Motorola Droid 4] Oggie7797:
[MENTION=5347028]Jishkah[/MENTION] the new ss says 10mb cache but to me 300 is better and when you make the rom slot it is easy to bump it up. Also as far gapps go I strongly recommend using pa gapps. Gapps are gapps regardless of the rom label but the "pa" ones (paranoid android) give you size options for full, modular, micro, nano, etc...