yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] joefuf:
I started from scratch, wiped and reflashed the ROM and finally got it to work. Something must have been up with that last flash because I didn't even see the folder tree show up when I clicked Restore last time, but it was there right away on this round. It's restoring all 97,147 messages (so I guess this also does MMS, but we'll see), but it's going about as fast as SMS Backup & Restore did in my recollection. I guess I just have to expect this kind of wait time for restoring that size. I was impressed that the XML came out to 18mb (the SMS Backup & Restore ones are ~130mb). If this works, I might be a convert, but we'll see.

I did have one last issue with this latest flash of LOS 13. I flashed the ROM and GApps, and I cleared Cache and Dalvik and clicked Reboot System. I got a warning that there was no SU installed and I was not rooted, so I let TWRP install its SuperSu. I went back into TWRP before a boot and flashed the addonsu zip linked in the OP, and booted into the ROM to set it up. I got an error that SuperSu was not configured, so I downloaded SuperSu from the Play Store. When I opened it, it says "SU Binary occupied" and links me to their website. I downloaded Root Checker and it says I am rooted, but SuperSu does not open if I try. Any ideas?
[Motorola Droid 4] schmatzler:
Do not install su from TWRP. It's very outdated. When I tried it on CM13 a few months back, it nearly froze my system. I think it's intended for Android 4.4 or lower.

If you installed the addonsu zip from droid.cs.fau.de, you can enable root in the developer options. SuperSU is not needed on LOS13, try deleting the SuperSU app with OpenAPK if Root works:

https://f-droid.org/repository/browse/?fdid=com.dkanada.openapk&fdpage=17&fdstyle=grid
[Motorola Droid 4] joefuf:
Gotcha. I'll give that a try in a little bit. Still restoring some of the 97k messages with Super Backup to get an idea of how long it takes for my situation.

In the future, if and when I do go ahead and flash the new Official ROM to my daily drive phone, I would restore to stock. Then I am going to safestrap & root before I flash the Official ROM, then GApps, and then Michael's addonsu zip from here? Then Wipe Cache and Dalvik and I should be all set to reboot?

I think my issue was the I forgot to flash the addonsu zip and by the time I was about to reboot, TWRP doesn't offer you any options when rebooting except flash their su or reboot unrooted.
[Motorola Droid 4] joefuf:
Ended up taking about 19 hours to restore all of my SMS messages from what I can tell. Didn't take the MMS messages though, unless it's still loading those and I can't tell. I very much appreciate the tip, but if I'm committing that kind of time to a backup and restore, I'm taking my whole life with me and I'm cutting off the world for an extra 5 hours while my phone restores.

Once I get closure on the addonsu zip flashing process (and maybe do it again on my backup phone), I guess I could be set to join the Official ROM party.
[Motorola Droid 4] Shplad:
I'm new to Android, but I used to be an IT tech., so I understand computer concepts when expressed in those terms.

I just rooted my Droid 4 (running Jelly Bean 4.1.2), installed Safestrap-maserati-v3.75-unused-partitions and then flashed LOS 13 (20170603). I then rebooted and then rebooted again to Safestrap and installed gapps 5.1 2015-05-23-24.

The flash seems to have gone successfully but for a couple of things which are critical to using the phone:

1. There seems to be limited (WiFi) Internet access through some means and no access using other means. (I don't have a data plan). When I first connect to my WiFi, the phone says it's connected but that there is "No Internet access". I have no idea why. I have DNS settings configured in my router, and no other device here has that problem here. Previously with Jelly Bean, WiFi worked fine. Yet sometimes the browser works and I can get on the Web.

2. I cannot configure my gmail account without getting error:

"Validating Server Settings...

Couldn't open connection to server."

I'm guessing this could be related to #1 above, Internet issues, but sometimes it comes back with error about invalid username

or password.

3. Google Play Services keeps closing unexpectedly.

I tried to install another Google Play Services app, but I'm in a catch-22 because the Google Play Store relies on Play Services to run. I could sideload it, but most people say installing a newer version doesn't help. There's also the security risk, unless there's a secure site someone can tell me about with a hash value.

I noticed that some here are saying you should avoid flashing a ROM and then rebooting and then install the gapps. I did do exactly that, because I forgot to add the gapps to be installed immediately after the ROM and before rebooting.

I really don't want to go back to Jelly Bean. Can anyone suggest anything?
[Motorola Droid 4] schmatzler:
LOS 13 is Android 6.0. So you also need GAPPS 6.0 for that.

Or alternatively, this.
[Motorola Droid 4] Shplad:
Thanks. So the quickest option would be to what, just copy the gapps 6 folder to my phone and boot safestrap and flash the apps?

So you have any idea if that actually might fix the problem or just an educated guess?

If that's what needs to be done, do I need to erase/uninstall anything first, or just install the apps?
[Motorola Droid 4] schmatzler:
Try flashing the Android 6 GAPPS ZIP over the already existing ones. If that doesn't work, reinstall the ROM and flash the GAPPS afterwards.

You should be able keep the data partition intact.
[Motorola Droid 4] Shplad:
schmatzler:

As a newbie, I'm confused cause there appears to be multiple versions, and I want to install the right one. Which version, exactly, from which website?

Arm, obviously, but which one, there dozens from which to choose.
[Motorola Droid 4] u.b.o.o.t:
In your place, I would wipe data and system partition and then reinstall ROM+Gapps in one go.

You need Gapps for Android 6. Opengapps is one of many distributions of Gapps. There are several flavours. Pico should be sufficient (contains play store): http://opengapps.org/?api=6.0&variant=pico Larger flavours contain more google apps (like Google Now), but if you want to install to stock slot, only pico will fit in.

If you forget to flash Gapps just after the ROM and before rebooting, you just need to wipe data partition via recovery and then reboot to make it work.
[Motorola Droid 4] Shplad:
u.b.o.o.t:

Thanks. Which is the smallest one that includes Maps, or do they include Maps? I could really use that.

Thanks
[Motorola Droid 4] u.b.o.o.t:
You can install maps simply via play store.

Flashing Gapps will put everything into system partition. Stock system partition is too small for that.

Installing via play store will install into data partition which is large enough.
[Motorola Droid 4] Shplad:
Dang! I think I bricked it. I thought the upgrade process I had done previously put the old ROM in another slot, and would give me the option to boot the old ROM. I think this is not the case. TBH, the whole damn process is very confusing. What you just told me to do, unless I didn't reboot in between, it wiped the bootloader, right? So now I can't even boot to recovery mode?

Not blaming it on you, but it would be nice if there were diagrams or something to make this process less confusing and more reliable. Will RSDLite work now, or is this thing totally bricked?
[Motorola Droid 4] u.b.o.o.t:
Sorry to hear that and sorry for not being clear enough, but don't fear - due to the locked boot loader, you can't fully brick it :) If you can't get into safestrap anymore, just restore stock rom as described here and start over, i.e. root it, install safestrap, etc.: https://xdaforums.com/showthread.php?t=2207384

Regarding slots: stock-slot is the one where the stock rom resides. If you install into stock slock, stock rom will be overwritten. The other slots are safe - that's why it is called safestrap - they are simply made of image files within safestrap subfolder of your internal storage.

EDIT: there actually is a way to brick the phone: doing a stock rom restore with low battery!!! So beware...
[Motorola Droid 4] Shplad:
uboot:

The video says to boot the phone to Fastboot mode. I can't do that. I thought I made that clear above. Will removing the battery change anything (like allow me to go to a boot menu) or am I screwed?

---------- Post added at 09:20 PM ---------- Previous post was at 09:13 PM ----------
[Motorola Droid 4] u.b.o.o.t:
Removing battery won't help you. But maybe you phone is just frozen with a black screen. Try pressing Power+VolumeUp+VolumeDown simultaneously for a while - this will hard-reboot the phone.

If it does reboot, you may manage to get into safestrap again.

If not, try to charge the phone first before trying to restore stock rom.
[Motorola Droid 4] Shplad:
Yes, it does reboot the phone. But the phone never gets to any menus. Just Moto logo, then hangs at black (backlit) screen. So something is very wrong. And I followed EVERY single instruction exactly, according to the videos and HOWTOs. The only exception is that right now, I'm removing the battery to try to get the phone completely off, rather than in some sort of boot cycle. If that doesn't work, I think this phone is dead. Someone PLEASE prove me otherwise, cause if it is, then I lose a phone and these docs need some serious rewriting. Cause I did what I was told, and now, POOF!
[Motorola Droid 4] u.b.o.o.t:
Red Motorola logo = stock kernel from dedicated stock kernel partition which is locked and cannot be overwritten. It will try to boot stock rom from system partition and because you wiped it, it gets stuck there. But you still can get into fastboot mode. You just need the right timing for the key presses uppon rebooting.
[Motorola Droid 4] Shplad:
Only if I remove the battery will the hard reboot take me to a boot menu. If I select FB Tools, it vibrates, then goes to a black screen. What now?
[Motorola Droid 4] u.b.o.o.t:
No need to remove battery, You can force-poweroff via VolumeDown+Power

Can you still enter safestrap directly via boot menu as described here?

https://xdaforums.com/showpost.php?p=59944293&postcount=18

If yes -> no need for fastboot / stock rom restore.
[Motorola Droid 4] Septfox:
I've tried it in both stock and slot 1. No luck; keeping /data/ kills it no matter what I do.

So, I'm currently backing my games and other unsyncable stuff up in TB, and will just do a completely fresh install. It's been quite a long time since I last did a fresh install, anyway. Hopefully SS will cooperate when I go to make a slot, as I want to finally break out of the 3gb limit imposed by stock.

Edit: working brilliantly. Cheers stargo, and Merry whatever-you-celebrate-on-25th-of-December everyone :)
[Motorola Droid 4] EvilDragon17:
Tried the ROM as well, impressive speed and battery life :)

Some issues I found:

* I couldn't get any internet connection except via Wifi. I know LTE is not supposed to work yet, but it seems for me neither 3G nor GPRS do work, it always says there's no internet connection available when an app tries to accept the net.

* Bluetooth Audio transfer has gaps. Music plays, but every few seconds, the streams breaks for a second and then continues. Music playing does not stop, only the transfer via bluetooth turns silent each few seconds.

I'm using it in Germany together with O2.

Thanks for the awesome work, can't wait to use it when these bugs are ironed out :)
[Motorola Droid 4] stargo:
Internet works fine for me on Congstar (D1) and Netzclub (O2). Check your APN settings. LTE won't work anywhere outside the US due to wrong bands.

Haven't looked at bt audio yet and I'm currently at the 32C3...

Cheers,

Michael
[Motorola Droid 4] Shobai:
I fell into the trap of turning data off during setup, expecting that it'd turn on automagically once setup was done, but that didn't seem to be the case - I had to toggle data back on manually. You've probably already checked it, but that'd be a good first check: is cellular data on under Data Usage in Settings?
[Motorola Droid 4] Jishkah:
I actually have that problem with CyanogenMod 11, as well. For me, anyway, it doesn't stop - it suddenly fast-forwards, skips around, and then goes back to where it's supposed to be. Could be related. That's just about the only issue with Bluetooth that I've had, however.

It's not every few seconds, though. More like every five minutes or so? Happens at random. I know that there was a change in the Bluetooth stack between CyanogenMod 11 and CyanogenMod 12+(?), so these may be unrelated issues. Figured I'd throw it out there, though, just in case.
[Motorola Droid 4] EvilDragon17:
Well, I never checked the APN settings, on CM12 and 12.1, it was simply working.

But I'll try to look that up.

I never tried with CM11, but I know it worked fine with CM12.1 :)
[Motorola Droid 4] Jishkah:
Cool beans. Yeah; I've only really used Bluetooth for Pandora, and it could honestly just be the dongle that I'm using (one of those radio transmitters for cars; bought it on Amazon), but I'm glad to see that it works in CyanogenMod 12.1. Sounds like the current Bluetooth issues are unrelated, in that regard. I wasn't sure if they were, though, so I was just playing it safe, lol.

I might give one of the CM13 builds a whirl before the new year, if I have the chance. Ultimately going to get a CM12.1 Nightly on my device by the 3rd of January or some such, but as a Verizon user, is there anything specific that I should look into and log? I don't really have much going on until then.
[Motorola Droid 4] EvilDragon17:
The APN was the issue!

Somehow, when I checked the APNs for my user, not a single one was there.

SImply restoring them to default settings made all three O2 APNs pop up!

I don't know why there was nothing in there to begin with, but it's a simple thing to return them.

Nice, I'm using it now as daily OS and will post anymore issues I find :)
[Motorola Droid 4] Jishkah:
Does this persist across reboots? If not, could be permission-related.
[Motorola Droid 4] LuH:
I'd suggest going for CM13 right away instead, works for me way better (on upgraded system from 12.1 - I clean-installed /system, but kept /data) - as long as the Verizon data issue is sorted out by then (maybe it already is, didn't check lately). On GSM I have zero problems.

Bluetooth A2DP audio was laggy already on 12.1 for me (with my old Bluetooth 2.0 Jabra BT3030 handsfree from 2008 I guess), I suspect it's because the A2DP playback providing process gets stalled when system is busy, which is pretty much always in my case :) It never played right with screen off, having frequent dropouts and sometimes stopping completely. This behavior got worse in CM13, I think it's because of Marshmallow's more aggressive power saving system.
[Motorola Droid 4] Careless_:
So on the What's Not Working list, is Data to be removed now that some users got it working fine via APN refreshing/default settings?

Also, any news on the Reboot to Recovery option in the latest nightlies?
[Motorola Droid 4] JLPDA:
I'm excited to give CM13 a test drive! Does HDMI out work? I use ARUR to mirror my phone to my AppRadio3 HU...using CM12.1. Is there a clean and easy method to "upgrade" my CM12.1 while keeping all my data intact without having to do a complete wipe and system install and then a Titanium Restore?
[Motorola Droid 4] Jishkah:
You can make a backup of your current ROM Slot via Recovery. That's what I'd recommend that you do, anyway... backup your existing ROM Slot, wipe (I'd actually recommend outright deleting the ROM Slot and then re-creating it, which gives you the option of resizing partitions to your liking), install CM13, test it out. If it's not to your liking, you can wipe the ROM Slot again and restore the backup.

You'll just need to backup /Data/ and /System/, at the very least. Cache and Dalvik Cache can be rebuilt upon restore. Correct me if I'm wrong; I've never used that feature before.

I don't think that, at this point in time, a dirty flash is safe. It might be safe enough, but it might also cause some stability issues. You can try it out, but I can't guarantee that it'll work flawlessly.
[Motorola Droid 4] LuH:
Come to think about block devices, could we make unused ones, namely cdrom, preinstall and webtop, appear as USB device to enable Marshmallow to adopt it as an internal storage? [MENTION=3457922]stargo[/MENTION] ? That would be a dream workaround for the locked partitioning of the internal storage for me :) It's almost 2GB potential increase of userdata space in total:

root@maserati:/mnt # df

df

Filesystem 1K-blocks Used Available Use% Mounted on

tmpfs 429736 100 429636 1% /dev

none 429736 12 429724 1% /sys/fs/cgroup

tmpfs 429736 0 429736 0% /mnt

/dev/block/mmcblk1p25 8393576 2254952 6138624 27% /ss

/dev/block/mmcblk1p20 651935 578737 73198 89% /system

/dev/block/mmcblk1p24 3152724 2262272 890452 72% /data

/dev/block/mmcblk1p21 1032088 34160 997928 4% /cache

/dev/fuse 8393576 2254952 6138624 27% /storage/3769-0AF1

/dev/fuse 62351456 58270016 4081440 94% /storage/877E-0AF1

root@maserati:/mnt # mkdir cdrom preinstall webtop

mkdir cdrom preinstall webtop

root@maserati:/mnt # mount /dev/block/cdrom cdrom

mount /dev/block/cdrom cdrom

root@maserati:/mnt # mount /dev/block/preinstall preinstall

mount /dev/block/preinstall preinstall

root@maserati:/mnt # mount /dev/block/webtop webtop

mount /dev/block/webtop webtop

root@maserati:/mnt # df -h

df -h

Filesystem Size Used Avail Use% Mounted on

tmpfs 420M 100K 420M 1% /dev

none 420M 12K 420M 1% /sys/fs/cgroup

tmpfs 420M 0 420M 0% /mnt

/dev/block/mmcblk1p20 637M 565M 71M 89% /system

/dev/block/mmcblk1p24 3.0G 2.1G 870M 72% /data

/dev/block/mmcblk1p21 0.9G 33M 975M 4% /cache

tmpfs 420M 0 420M 0% /storage

/dev/block/loop7 3.8M 1.0M 2.7M 28% /pds

/dev/block/vold/public:179_25 8.0G 2.1G 5.8G 27% /mnt/media_rw/3769-0AF1

/dev/block/vold/public:179_25 8.0G 2.1G 5.8G 27% /mnt/secure/asec

/dev/fuse 8.0G 2.1G 5.8G 27% /mnt/runtime/default/3769-0AF1

/dev/fuse 8.0G 2.1G 5.8G 27% /storage/3769-0AF1

/dev/fuse 8.0G 2.1G 5.8G 27% /mnt/runtime/read/3769-0AF1

/dev/fuse 8.0G 2.1G 5.8G 27% /mnt/runtime/write/3769-0AF1

/dev/block/vold/public:179_33 59G 56G 3.8G 94% /mnt/media_rw/877E-0AF1

/dev/fuse 59G 56G 3.8G 94% /mnt/runtime/default/877E-0AF1

/dev/fuse 59G 56G 3.8G 94% /storage/877E-0AF1

/dev/fuse 59G 56G 3.8G 94% /mnt/runtime/read/877E-0AF1

/dev/fuse 59G 56G 3.8G 94% /mnt/runtime/write/877E-0AF1

/dev/block/mmcblk1p16 89M 89M 0 100% /mnt/cdrom

/dev/block/mmcblk1p22 598M 16M 582M 3% /mnt/preinstall

/dev/block/mmcblk1p23 1.2G 1.0G 227M 83% /mnt/webtop

I know adopting the SD is easier, but that would disable it for use with Windows computer when pulled out of the phone, and I'd lose all the data upon system failure as it not only re-formats it to ext4 fs, but also encrypts upon adoption. (Yes, I could backup the encryption code elsewhere upon the setup and then recover using a Linux box, but that's a lot of fuss I don't want to go through – I don't like my data encrypted at all).

I suppose the adopted media have to be present at system boot time, so system alteration is needed for this, not just some third-party init script, right?

Is there a way to disable the encryption, even just to get rid of this unnecessary CPU hog if used with SD after all?
[Motorola Droid 4] Oggie7797:
Good job [MENTION=3457922]stargo[/MENTION] on the cm13 port! Gonna be running my droid 4 for the next couple of months and am glad this thing still has development. Keep up the good work man
[Motorola Droid 4] Jishkah:
I mean, don't get me wrong. I'm going to use CyanogenMod 13, eventually. I just don't think that I'm going to do so until it hits Official status. I'm less so worried about performance and more so worried about stability, and it seems like there's still a few things to iron out. Looks like it's progressing really smoothly, though.

Just a personal preference. It's probably stable enough to use on a daily basis, and no different in terms of stability from being an official Nightly, but I'd just prefer to only use it when it hits official CyanogenMod channels. CyanogenMod 12.1 is pretty tried and true, anyway - no Milestones on our device, but it's basically feature complete.

I'm gonna be traveling in the next week, anyway, so I need something that I know'll be (mostly) stable, anyway, lol.
[Motorola Droid 4] LuH:
I'd personally still use CM13 in your case as well - for me it's been a pleasure so far, much more stable (way less system hangs and no missed calls due to system overload) with same data, which is what I look for in my phone when travelling :) I understand your point of view though and if 12.1 turns out fine, good for you. I guess my system is mainly suffering from too much installed stuff, even though I stripped it down a lot coming from CM11 to CM12 (mainly dismissing Facebook, LinkedIn and few other accounts to free up some resources and make contacts, dialer and messaging less laggy) :)
[Motorola Droid 4] joojoobee666:
You don't need to adopt it. Have a look at my kernel thread here.. There is a link there for the SDSwap. This basically mounts your external SD Card to /sdcard which makes this the primary storage (default for downloads, pictures and obbs files). No need to reformat or use the encryption.
[Motorola Droid 4] Septfox:
Well, it's still Not Working in the sense that it doesn't work out of the box.

As of the latest, still need to toggle Airplane Mode to get it to connect up, and in my case (on Tracfone, might not be so for "proper" Verizon) I had to switch from Global to CDMA+LTE/EVDO before even that would work.

Apparently, if you can get it to work, it's fine. If it doesn't work (e.g. bootlooping after the Android is Upgrading screen), you'll have to manually backup+restore.

The latter is what I had to do. It wasn't as daunting a task as it seemed like it would be, though, and the end result was worth the trouble.

Well...

I agree wholeheartedly with this. On average, it's faster and smoother than CM12, calls/texts come in as they should, and I personally haven't suffered a single crash that I didn't prompt (accidentally applying a CM12 theme got me a loop of insta-crashing SystemUI, woops). Haven't even gotten it to soft-lock trying to do something, which is nice.

If you can dirty-flash it, give it a try, in another slot if you want to be safe about things. Marshmallow itself is still lacking some things (notably SuperSU and Xprivacy), but aside from those it's an almost pure upgrade over Lollipop.
[Motorola Droid 4] Shplad:
No, not accurate. I only get to a boot menu if I remove the battery first. The menu seems like the choices are in a different order than before I wiped those two partitions. To answer your question, yes, I can select it, and then the phone vibrates and the screen goes black.

u.b.o.o.t said that "due to the locked bootloader..." I thought that became unlocked as soon as one rooted the phone?

Here's a photo of the boot menu I'm seeing (but I have to remove the battery each time).

Let me guess....RSDLite using AP Fastboot mode?

See photo.

BTW, how do I make a photo full screen, or is there no way to do that?
[Motorola Droid 4] Shplad:
EDIT: Phone just needed more charging, I guess. Back to the same above. This is really getting annoying having to remove the back cover, unscrew the battery screws, remove them, leave the battery out and reverse the whole process every time I want to boot to a boot menu.

Wow, I'm just blessed with bad luck today. I can't even get the phone to turn on on now. No power, it appears. Now, the battery was at about 98% when I did a few boots to the boot menu and a few that went to nowhere. So I ran no OS, no apps. I opened up the back and used a multimeter to test the battery. It read 3.3V. Is it normally that low? I'm charging it again to see what happens.
[Motorola Droid 4] wsemi:
3.3V is very low, maybe 2-3%. Google "li-ion discharge curve". If the battery loses its charge rapidly then it may needs to be replaced.