yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] JLPDA:
Here are my observations on installing CM13 1/26 Nightly on a "test" DROID4:

Clean Install

1) Created ROM SLOT 2.. 1GB Sys, 4GB Data, 500MB Cache.

2) Installed CM13 and GAPPS MICRO http://opengapps.org/?api=6.0&variant=nano at the same time.

3) SD Card accessable with odd naming convention as previously indicated.

4) Installed Waze and several other applications from Playstore without a problem.

5) Installed Titanium Backup (Pro) and performed a batch restore of several apps+data from SD Card without a problem.

6) Attempted to flash several different CM13 OC Kernel versions and just get a bootloop on CM13 logo. Tried 1.4 RunNGun, Full, Lite, HV, LV, etc. Not working for me.

Dirty Install/Upgrade

1) Created ROM SLOT 2.. 1GB Sys, 4GB Data, 500MB Cache.

2) Performed a TWRP/Safestrap Restore from SDCard of a nandroid backup from my "Live" DROID4 (CM12.1 112615 Nightly).

3) Many programs on SD Card not recognized. Greyed out icons on NOVA launcher and not appearing in Apps.

4) Installed CM13 and GAPPS MICRO http://opengapps.org/?api=6.0&variant=nano at the same time.

5) Appears apps and data on internal memory woking OK with CM13.

6) MS Exchange data (contacts) and account not updated/created. Will have to create and sync.

7) SD Card accessable with odd naming convention as previously indicated.

8) Performed a TI batch restore of several apps+data from SD Card without a problem.

Overall performance in a side-by-side comparison between my "test" DROID4, with CM13, and "live" DROID4, with CM12.1, appears as though apps will load and run slightly faster except have seen lag on graphics display and refresh.

** I'll keep testing, but, can't update my "Live" DROID4 untill I know apps on SD Card will update (I don't really want to reinstall or restore everything).

**Also would like to get OC 1.4 to work.

If anyone would like me to test a particular application and/or configuration, I'd be happy to do so on my "test" DROID4...don't really care if It gets screwed up, just don't want to brick it.
[Motorola Droid 4] Bobcus Leper:
FYI, with ART, the cache partition only needs to be 10MB. Also, for pico GApps, the system partition only needs to be 700 MB. For micro and nano GApps, the system partition only needs to be 800 MB.
[Motorola Droid 4] Septfox:
In the past, our int/ext SD have always had volume labels. They don't at the moment, and lacking those are simply marked with (abbreviated?) UUIDs.

So they're there and perfectly fine, the only difference is they're not using user-friendly identifying strings. You can probably mark them yourself, but I don't know how off the top of my head.

---

Sizes:

800mb (+)

4000mb

10mb

/data limit is just shy of 4gb. It seems to be our hard limit, probably due to the filesystem limitation (FAT32); setting any bigger just makes it go "nope" and revert to 4gb. I don't recall if we're about to change the internal SD filesystem and get around that without breaking everything.

Cache is used, but I believe it's only for logging purposes (most I've ever seen in it was ~20mb, last night it had 4mb in it, couldn't be arsed to check what that 4mb was). ART precompiles and download caches are stored in /data, so no worries about them. So I somewhat tentatively agree: over 10mb is a waste. But then...it's only another 100mb to be "safe".

The thing about /system is, we can expand it up to 1gb (or more? Haven't checked.). /data can only go to 4gb. By using a larger /system and a bigger gapps that includes stuff you'd usually install as user apps into /data, you can make more effective use of the limited storage available in a slot.

Sure, you're looking at a ~5gb slot here, but upgrading the external SD card for "everything else" is reasonably inexpensive these days.

---

The stock partitions will usually remount properly for me if I reboot the phone. It seems like I often "lose" /system when switching between it and virtual slots, but it's perfectly fine and will be booted from after a restart.

If it's permanently unmountable, you could do the wipeless SBF flash, that'd definitely bring it back incase something got corrupted.

If it doesn't work from the outset, there's probably not much to be done under joojoobee's kernels. You're gonna have to live with 1.3ghz until he gets something JBX-esque going with voltage management.
[Motorola Droid 4] JLPDA:
UPDATE. Looks like the SD Card has to be reformatted "as internal memory" in order to move apps to it. This sucks. Means I have to backup all my data from the SD Card and then copy it back after reformatting. So, performing a "dirty" update flash to CM13 with many apps and data on the SD Card is not seemless, nor quick.
[Motorola Droid 4] stephbiker:
Hello , i have a problem with bluetooth

My bluetooth is ok with my little speaker

But with my radiocar , a clarion cz302e

It try the association and nothing else

Thanks (and sorry for my english)
[Motorola Droid 4] daniel_m:
How is the 3D-performance in the latest build? I'd like to switch to CM13 this weekend and try to get XPrivacy running. So far, the build from 25.01.16 seems to be the safest option...
[Motorola Droid 4] kzin42:
Observation

Hi, I just installed "cm-13.0-20160127-NIGHTLY-maserati", this being my first time installing a ROM I expected some problems but It seems to run well! :good:

I have noticed that after you close the keyboard the current App wont go back to portrate mode, I have had to "Home button" back to the home screen, then it changes. & I can go back to the App.
[Motorola Droid 4] Careless_:
Well I can report a couple of things with the Jan 25 Nightly

1) Battery life is pretty bad at this stage. Even after turning off Wifi and Bluetooth and rebooting the phone, it just drains batt compared to Lollipop. I hate when my battery runs out. The phone doesn't turn back on until it charges to 100%... (any way around this?)

2) Bluetooth seems spotty. Some of my devices drop from connection randomly, or stutter when playing music. Going to charge them all up and try a different device when I get back to the shop where I left them. Will report back from more testing when complete (Monday or Tuesday night).

3) Reaction time using the rom is definitely slow/choppy. It's not as good as Lollipop was to me. Maybe I need to tweak the kernel settings.

Perhaps at the end of the first post, the ideal Kernel settings should be posted, with a link to Kernal Aduitor or similar program so we can alter the kernel cpu profiles upon install. This would help people find a better starting point and it would allow all of us to benchmark closer to what everyone is running to make performance more "controlled" when comparing from one rom to the next... just a thought.
[Motorola Droid 4] Septfox:
Got this, at least.

Bring up the recovery menu when you turn it on (hold Vol+/-), select BP Tools. This should take you straight to Safestrap, where you can then reboot normally. "Should", because I haven't actually tried it to circumvent the forced charging BS, only to skip the recovery song and dance I need to normally do when powering on.

Otherwise, and what I had to do before I figured out I could use the above: http://xdaforums.com/showpost.php?p=63700941&postcount=2

Edit: that was even in reply to you, how have you already forgotten? :v
[Motorola Droid 4] kzin42:
Is the GPS on? once I turned this off mine seems to last about the same as the stock Rom.
[Motorola Droid 4] daniel_m:
CM13 20160130 is running fine so far. XPrivacy is working in AOSP mode (forced) with SELinux on Enforcing. I will restore my backed up apps and test XPrivacy more thoroughly.

One question though: How to enable init.d support? I see init.d in system\etc\, but a test script does not get executed (permissions are set to rwxrxrx).
[Motorola Droid 4] Septfox:
If I'm not mistaken, it has to be enabled when the kernel is built. I haven't seen it enabled by default since running Slimkat.

If you only need to run scripts, and the changes you're applying can wait until post-boot (during app startups), you could get Universal Init.d.

Or, if you're running joojoobee's OC kernel, you could ask him to enable it.
[Motorola Droid 4] Shobai:
This seems to work for me, give it a try and see how you go:

From dead flat, plug the charger in - you'll get the Moto logo, then a screen showing a battery being refilled.

Let the battery get to 10 to 15%, then unplug the charger.

Reboot the phone, by turning on with the power button [or sometimes by holding power and volume down, for a hard reset].

Wait for the Moto logo to flash up and then off, then once the SafeStrap display appears, plug your charger back in. The phone will continue to boot.

For my phone, 10% appears to be enough to get to the SafeStrap screen. If you don't unplug the charger during the reboot, you'll always get kicked back into the charging display rather than pogressing to the SafeStrap display.
[Motorola Droid 4] daniel_m:
Unfortunately, I don't think post-boot would do. Init.d is important for Link2SD and AFWall+. And I'd like to get Live Boot to run as well.

Stargo, do you have the possibility to enable init.d in your ROM? It is a very powerful and essential tool :)
[Motorola Droid 4] daniel_m:
Is there something wrong with App Permissions? I tried to allow additional permissions for some apps, but the setting does not stick. Additional permissions show up as disabled after moving away (back button) from the additional permissions screen. I'd like to give XPrivacy the permission to kill apps and manage restrictions and settings...
[Motorola Droid 4] Careless_:
I knew I had asked it at some point, but I wasn't sure if it was in a dream or if it actually happened. lol.

in any case, I tried many things and just waited for it to charge to 100%.

---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------

Happy to report MUCH MUCH better battery life with Ultra Low Voltage joojoobe kernel with FullScale 1.4ghz clock.

The phone feels WAY snappier with this kernel and finally Chrome browser doesn't feel like I'm trying to run it on a comodore 64 emulator.

Everything is snappy and responsive with that kernel, and so far I'm liking it.

Will report my Bluetooth findings tomorrow if my devices at the shop are fully charged.
[Motorola Droid 4] Денис (Denis):
...and I have some problems with the bluetooth headset connection. When first connected everything is fine, but the next times when connecting music plays intermittently until the phone is restarted.

But that's not all. If the headset is active, the connection should take place automatically when activated bluetooth on your phone, but it does not.

Bluetooth headset: prolife bs-720

cm-13.0-20160201-NIGHTLY-maserati

sorry for my bad english, thank Google for translation.
[Motorola Droid 4] Careless_:
Seems like both music apps, song browsing, and bluetooth itself is ALL much faster and stable than CM12.

Everything is running amazing. Very impressed.
[Motorola Droid 4] Milp:
Is there any way to keep the microSD working the way it was in cm 12.1 while still being able to move apps to it aswell as accessing the ones i moved to the sd in cm12.1?
[Motorola Droid 4] daniel_m:
After some research, it looks like it might be possible to get init.d to work by editing init.rc in root and adding logwrapper and run-parts. Am I correct in assuming that editing init.rc will not survive a reboot because it resides on a ramdisk that gets populated from a Safestrap boot image? ... Or did I misunderstand completely?
[Motorola Droid 4] synpse:
Unplug the phone, press the power button, then plug it back in to charge the rest of the way. My Droid 4, just like my Droid 3, will NOT power on while charging. So.. just unplug it, hit the button, plug it back in. ta-da! :good:
[Motorola Droid 4] Jishkah:
If you hold the power button down while it's charging like that, you should be able to boot into your normal system, regardless of charge level. That's how it works for me, anyway.

On an unrelated note, I've started to use CyanogenMod 11, again. Er, not because it's any better than CyanogenMod 13 - it's not (it's only a teensy bit snappier) - but because I'm fairly certain that I'm beginning to experience some hardware deterioration unrelated to the ROM that seems to not pop up as often on the default Stock ROM and CyanogenMod 11. The screen artifacts and jumps around and looks "glitchy" sometimes when I switch screen orientations (think partially unplugging old VGA cables, or in "creepy" YouTube videos where the video "supposedly" becomes corrupted - best way to describe it, really), phone randomly loses service entirely, soft reboots, the works. The whole thing just kind of locks up, at times - like it's having a really hard time processing even the most mundane tasks - and then soft reboots on me. Switching between data sources seems to kill performance, too, to the point that it just ****s itself and calls it a day. Kind of popped up all at once, too.

In the meantime, the only issue that I remember being a persistent annoyance in CyanogenMod 13 (and, by all means, it could be related to the hardware issues stated above) was that it forgot my WiFi settings at random whenever I'd need to reboot the phone, much like how it did in CyanogenMod 12.1. Manually deleting the wifi folder in the ROMs internal filesystem never did solve the issue, either, unfortunately - so if it's a permissions issue, re-creating the folder never did fix those permissions.

Otherwise, that's about it. I'll probably be purchasing a new phone in the next few months, so I'm going to stick with CyanogenMod 11 for stability's sake until then.
[Motorola Droid 4] synpse:
Yeah, I upgraded from a Droid 3. It's nice to have people chime in with "This works for me..." responses. Those are what people REALLY search the forums for! Answers! Solutions! Help!

I bought my Droid 4 about a year ago, online, and "Used, but Like New" for about $50. That's what Verizon's pre-paid 1 GB Data plan costs a month! $45 plus tax. So far, this is the best Physical Keyboard phone I know of. And.. with it being that cheap, you could just buy another one. Alas.. we're of the h4x0r world, and don't want to see the old one go to waste. I just wish it had the removable battery like the Droid 3.
[Motorola Droid 4] Shobai:
As long as you carry a Torx driver with your spare battery, it's a fairly simple process to remove and replace :)

[MENTION=3457922]stargo[/MENTION]: a long press of the volume buttons isn't working to skip songs in the Music app - is that an issue with my settings, with the app, or with CM13? I have "Playback control" under Buttons set on, if that helps diagnose.
[Motorola Droid 4] JLPDA:
Ditto...with the dirty flash I did on my "test" DROID4, CM13 wouldn't recognize my SD apps.
[Motorola Droid 4] Careless_:
I am getting some of the same issues.

today i went to play some music and it would play 1 second and pause for about 3 or 4, and then play another second, etc.

I had to reboot the phone, and it was all good.

my phone seems to automatically connect to the speaker whenever bluetooth and the speaker are turned on.

i'm on 01/25 nightly.
[Motorola Droid 4] Milp:
It's not only that, i also can't find any "move to sd card" button in the apps settings.
[Motorola Droid 4] daniel_m:
Is it possible to disable "battery optimisation"? It is very cumbersome to disable it for each app individually.
[Motorola Droid 4] JLPDA:
No "move to sd card" available in apps settings or "Apps2SD" app. Quite possibly the SD Card needs to be reformatted for CM13...which I read somewhere. Haven't had an opportunity to do more testing, but, can't do a dirty flash and go live unless the SD Card apps and data get upgraded with the flash.
[Motorola Droid 4] Bobcus Leper:
In Marshmallow, you have the option, when you first set up your device, to use your SD card as internal storage, or to use it as portable storage. In order to move apps to SD, you must set it up as internal storage. Just a disclaimer, doing this will erase all of your SD card's contents, and your default internal storage will be seen as an SD card. There is no switching apps between the two. Once you have formatted the SD card as internal storage, it will remain as such until you manually change it, or factory reset.

Deleting storage.xml, located in data/system/ will allow you to change your SD card to internal storage. Just reboot after you delete the file.
[Motorola Droid 4] Milp:
Yes, you have the option to either use the sd card as internal storage by reformatting it, or to keep using it as an sdcard, but without apps on it.
[Motorola Droid 4] Bobcus Leper:
Read the post above yours.:rolleyes:
[Motorola Droid 4] Septfox:
Looks like an issue with the app...Poweramp is working as well as it ever has, as long as bluetooth controls are enabled. Soundcloud, after it's done being painfully slow to start up for some reason, is also working fine.

Not really a solution to the problem itself, but: if you have a few dollars to spare, Poweramp is a worthy purchase. It works fairly well on our hardware and is quite feature-rich, especially compared to something that has all of five or six options like the stock app does.

There're other options around too, but I don't really have experience with them. Already had the Poweramp license from my old phone, where it was the only player at the time that didn't randomly skip like mad at 122mhz :\

Edit: Poweramp has a 30-day trial for the free version iirc, it's the full-version unlocker you pay for.
[Motorola Droid 4] Milp:
Thank you, but even with a modified storage xml, i won't be able to use the sdcard that is designated as "internal storage" to store camera photos or for general other mass storage usage?

I don't get how one is expected to decide whether to use the only sd card as a fully internal or a fully external storage. If there were 2 or more sd card slots, i would understand, but it's just so impractical this way.
[Motorola Droid 4] Bobcus Leper:
It looks like you understand perfectly. Yeah, I personally agree that the new SD card system is a step backwards.
[Motorola Droid 4] Shobai:
Cheers Septfox,

I picked up Player Pro on sale a year or more ago, and it seems to work well also. I'd uninstalled it because it used to crash on me often but after reinstalling, and updating, it handled the trip to work fine. I'll keep an eye on it. Thanks for the reminder!

[MENTION=3457922]stargo[/MENTION], [MENTION=272927]bobc[/MENTION]us et al.

I've heard that the internal storage on the Droid 4 is pretty slow. Is it still faster than SD card? For instance, I have a 32GB card with a nominal 90MB/s read speed. Would there be any performance benefit to me adopting the card as internal storage? Or would I be getting more storage space but less performance?
[Motorola Droid 4] JLPDA:
Exactly +++1
[Motorola Droid 4] Bobcus Leper:
I ran a benchmark once, and my 8GB class 10 SD card was 2-3MB slower than my I internal storage. I received around 15MBs with the SD card. I'd give it a shot to see how your SD card performs compared to the internal storage.
[Motorola Droid 4] Shobai:
Which benchmark would you recommend?
[Motorola Droid 4] Bobcus Leper:
I used this one.

https://play.google.com/store/apps/details?id=com.a1dev.sdbench
[Motorola Droid 4] Shobai:
I gave that one a run, after failing miserably with Androbench and AnTuTu. My SD card got 12.85MB/s read and 10.28MB/s write, while the "internal memory" partition got 17.82MB/s and 7.65MB/s respectively. I haven't tried any subsequent runs, normally I'd do at least 3 each and average.

Hmm.

I'm not sure if adopting the SD card would give it any improvement in performance, but I might give it a go in the next few days [when I have some free time].

[edit - some more runs}

I did another 5 runs each for the on board and external devices, then sorted each data set in descending order. There's a median filter [MF] below each set also. I'm seeing a large amount of variation in some sets, very little in others - weird... it'll be interesting to see if adopting the SD card makes any difference whatsoever. Again, this is for a nominal 90MB/s read card. The card obviously gets much better results when plugged into a PC, rather than the Droid 4.

Device	R	W
SD card	14.05	10.45
12.95	10.28
11.51	8.67
11.15	5.80
10.97	3.26
9.07	3.15

MF	11.65	7.00

Int.	26.41	8.13
23.07	7.87
20.99	7.65
17.82	7.51
16.00	7.42
14.72	7.30

MF	19.47	7.61
[Motorola Droid 4] Careless_:
Can anyone confirm if the latest nightly fixes the Bluetooth issues?

Today I was using a bluetooth speaker and after one album was done playing, I tried to start playing another and it would only play a split second and cut out for another 5 seconds, and then repeat.

no reboot or on/off would fix the issue. I tried on two speakers, same deal...
[Motorola Droid 4] Septfox:
From what I've read:

Adopting turns your SD card into internal SD storage, and "encrypts" it. The "real" internal SD is rendered inaccessible to the user (or at the very least, it's no longer mounted automatically). You're essentially replacing your internal storage with larger, expandable storage...though I'm not sure what the upgrade process would be like if you wanted to put a bigger card in later.

If you use the built-in App2SD a lot, and/or regularly load big things off your SD card like Osmand maps, external game data, etc, then you would probably see a benefit in doing this if you have a very fast SD card and if you can get the phone to play nice with it (as you've noted, the interface seems arbitrarily slow).

The internal eMMC is a single chip split between the user 8gb and the system partitions, so being able to have the external SD shoulder some of the I/O when loading apps should leave the eMMC more free to do things like...running the operating system.

As far as speed, using the above app I was pulling ~26mb/s read and ~15mb/s write from internal storage, whereas my old 16gb Sandisk card - a class 10/UHS-1 - was only averaging ~15mb/s and ~8mb/s respectively. Back in KK I saw upwards of 80mb/s and 60mb/s read for int/SD respectively, but that was in another app and I think was due to cache and scheduling shenanigans.

Another thing to worry about is the encryption. As I understand it, adoptable storage uses ext4 w/encryption, which is newer and much less resource-intensive than previous offerings...but still causes a performance hit, especially when the filesystem is really being beaten on. Any performance benefit gained from splitting operations between SD and eMMC is probably going to be eaten up by this.

Also due to the encryption, Safestrap won't(? it shouldn't be able to access the key(s)) be able to access the adopted SD card. If CM13 ever becomes unbootable, you're probably completely screwed as far as accessing the stuff on the card. This has been the primary thing keeping me far, far away from it.

Really, if you're in the mood for experimentation, just use joojoobee's SDswap. It'll give you the same effect (using external SD as internal), but leaves the internal SD accessible and doesn't do any of this encryption nonsense.
[Motorola Droid 4] Shobai:
Cheers, I'd forgotten about the encryption part, and I hadn't heard of the safestrap issue. Yep, I reckon SDSwap sould be the best solution, but given that the Droid's SD card controller doesn't seem to be able to make use of the card's full potential anyway, I don't think I'll worry.
[Motorola Droid 4] KusioST:
Where can I found more information about this "joojoobee's SDswap"? I am new and I cand find anything in forum or google.
[Motorola Droid 4] Bobcus Leper:
Read the OP (original post) of this thread.

http://xdaforums.com/droid-4/development/wip-marshmallow-custom-droid-4-razr-oc-t3281830/page6