yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] smartass101:
Tried the new ZNH5YAO0FE snapshot with pico GApps, works well so far.

Today I noticed that a new snapshot cm-13.0-20160816-SNAPSHOT-ZNH5YAO0FE-maserati.zip was released so I decided to try it. I had CM11 with Safestrap 3.72 on it before that and I was getting tired of the phone hanging each time I activated a network connection (most likely due to pre-installed GApps apps syncing). I was hoping that a clean install with a smaller GApps base would make the phone snappier.

I followed the standard installation guide:

rooting: the phone was already rooted, so I skipped this step

I installed Safestrap 3.75. Because the old Safestrap app was already gone, I just uninstalled old recovery in the new app and then installed the new recovery.

booted into TWRP and wiped and factory reset

installed the snapshot

tried installing micro openGApps, but the /system partition did not have enough space, so I installed the pico version later. Had a bit of a hick-up here, because I booted the new CM13 ROM before installing pico GApps, so I got the "Startup Wizard has stopped" loop of hell the first time around. Resolved it by wiping and flashing CM13 and pico GApps all in one go as recommended on various sites.

So far everything works well, wifi connects automatically, bluetooth pairing works. It seems quite snappy so far. I really appreciate all the CM13 UI tweaks and improvements. Thank you very much [MENTION=3457922]stargo[/MENTION] and everyone else involved.
[Motorola Droid 4] Narevek:
No idea. I just had a bit of time yesterday and got curious about what would happen if I messed with it.

I just rebooted to see, and did end up having to toggle airplane mode before it would reconnect again.
[Motorola Droid 4] Septfox:
Really? I tried the exact same and got as far as Starting Apps before it hot-rebooted and then just endlessly bootlooped. And then found out that I couldn't switch back to the stock slot (12.1) because SS determined that I was on Slot 1 and was going to STAY on Slot 1, before being all "oh you wanted to switch to Stock you say? Here, have a pre-SS blackscreen, enjoy your SBF."

Not been a fun experience so far, this upgrading thing : |

Guess I'll uninstall all the likely-to-be-interfering stuff first before trying again. The bit I tried of cm13 did seem pretty quick on its feet.
[Motorola Droid 4] Shobai:
I haven't had any luck with the 1218 build either: I've tried a flash straight over the 1214, a delete ROM slot and and install, and now a wipe of /system from 1214 and install - I waited an hour or more in each case, but I'm just getting the CM logo flashing [as far as I can tell].

Any ideas?

[edit: as [MENTION=1472623]d.casper.b[/MENTION] says below, my issue was flashing SuperSU - if I don't add it, the ROM installs fine]
[Motorola Droid 4] d.casper.b:
Did you flash SuperSU by any chance? I found I was not getting past the cm logo when I flashed SuperSU.

Sent from my Motorola RAZR Maxx (XT910)
[Motorola Droid 4] Shobai:
I was - I'll try without. Thanks =)
[Motorola Droid 4] mauveron:
The ROM is great, I did not expect it to be so fast, it seems as smooth as the original Jelly Bean, but the battery life is really poor. On JB I get about 1 day and 10 hours of use, and with the same apps and settings I only got less than 12 hours in CM13.

I have also noticed that automatic brightness is not working.

Can I do something to increase the battery life? Some particular configuration?

Thanks for the excellent work!
[Motorola Droid 4] Careless_:
Keep an eye on any running processes that look out of place on the new CM13... This really is the first one people are starting to run, so it wouldn't surprise me if there was a background process or running service that is being overly talkative.
[Motorola Droid 4] mauveron:
I'll install a task manager and take a look, thanks. I didn't mean to complain, I know I have to be patient. But it already works so well that the short battery life has somehow surprised me. :)

I have also installed Lux and now the automatic brightness works correctly.
[Motorola Droid 4] Shobai:
So, with the 151218, I can't flash ROM+GAPPs+SuperSU, but I can flash ROM+GAPPs. If I then try to flash SuperSU, I'm back to the non terminating boot...

I guess my next question is what to do for SU. Are you guys still using SuperSU? Previously I wasn't having luck with it apart from flashing the v2.46 [or whatever] zip. Are there alternatives?
[Motorola Droid 4] lucize:
Integrated su from development options, is not working ?

You have to disable and enable it again for it to work

Regards
[Motorola Droid 4] Bobcus Leper:
Finally someone who thinks that it is stupid to flash a root application, when root is built right into the ROM. :good:
[Motorola Droid 4] Shobai:
Thanks Lucize, it is working after toggling developer options off and back on as you suggested. I was using SuperSU because Titanium Backup pops up a warning about the CM SU and suggests SuperSU instead, but if this is working when SuperSU breaks things, I guess I'll stick with it!

Thanks again.
[Motorola Droid 4] d.casper.b:
I agree, but I used SuperSU since it seemed to work better and some apps refused to work - only with SuperSU did they work.

Sent from my Motorola RAZR Maxx (XT910)
[Motorola Droid 4] Careless_:
Calm down there, Leper.

It's not stupid. The switch for ROOT ACCESS in ON in developer options upon installing and enabling the hidden screen, yet root permissions are not active until the user turns them OFF and then ON again. This has been the case since CM11 as far as I can tell, and was not the case on my previous phone- which worked with root access just by flashing a root enabled ROM- no developer menu or root access control intervention required. These roms usually had a SuperSU or SuperUser application pre-installed. CM does not. This is why it's a first instinct to install such an application by many users. It seems like something is "missing" to them if they are unaware of the on-off trick.

I had to figure it out for myself, and I installed a Root application to test if the dev screen root access switch even worked at all, and I found out that this undocumented on-off step is required by accident while using a Root app and fiddling with the options. I reflashed the ROM and tested the on-off trick without the Root App, and confirmed it was working- so now I know. I would imagine others have gone through the same thing with CM roms for the Droid 4.

why does someone trying a root application for a solution that is not written within the rom help-text itself "stupid" to you? it's a rhetorical question. I don't really care for the answer.

The best solution to this little caveat of using CM roms and attaining root on the Droid 4 would be to make mention of it alongside any download links or first-post information within ROM threads if it is a requirement.
[Motorola Droid 4] Bobcus Leper:
I'm sorry for that. Thanks for the succinct argument. I wrote my post late last night, and I didn't really think about the words that I used. "Redundant," now that I look at it, is the word I should have used. My complaint is against CM for creating such a confusing system to enable root. It seems as if, sometimes, when a user flashes SuperSU, after a ROM + GApps, they end up in a bootloop. I think that your fourth paragraph perfectly sums up what should be done to clarify root access on KitKat and above. I still remember the GB days when a root application and GApps were built right into a ROM. Thanks again! :highfive:
[Motorola Droid 4] LuH:
Maybe it's worth mentioning I never tried any other than System slot - and never had a problem with it.

Weird - it always worked fine for me without this off-on trick (in all CM versions with integrated root, starting CM11 I guess), this is the first time I hear of it... Although, maybe I rebooted after first going through Settings, which I always do after upgrade and where I always allow Developer options and root for Apps and ADB.

I stumbled upon only one such app so far, developed by Chainfire. With CM's root access everything else I tried work fine for me, including these apps: Titanium Backup, Total Commander, BusyBox Pro, SQLite Editor, Terminal Emulator, WiFi Pass Recovery
[Motorola Droid 4] hearkenoath:
Build 24/12 Thanks! What a great gift!
[Motorola Droid 4] altgrr:
In case it helps anyone, my results running the latest build:

* Install in slot 1 - works without GApps. Installing GApps-pico latest version results in Setup Wizard and Google Play Services endlessly crashing.

* Install in safe slot - can't find a way to make this work (yet). With the cm12.1 ramdisk the CM13 boot screen appears and it gets stuck there; with the ramdisk edited using LuH's ramdisk-kitchen it bootloops.
[Motorola Droid 4] lucize:
cool boot animation :good: :) !
[Motorola Droid 4] stargo:
Hi,

It seems GApps currently can't be installed without a wipe on any ROM as this causes permission-problems. So it seems you have to either install GApps when installing the ROM or you have to wipe after installing them. It seems related to the ne M permission concept, where later installed GApps get no permissions at all.

Cheers,

Michael
[Motorola Droid 4] aiamuzz:
[MENTION=7388616]smartass101[/MENTION] ... thanks for the feedback, if wifi is connecting automatically, time to try it ...

a few quick questions before that ...

i wasn't able to pair this phone to my bluetooth laptop, is that working now ?

then there was the problem of external SD card permission problem, is that rectified ?

with regard to the snapshot can it be incrementally flashed over a nightly build ?

or ... a clean installation is the only way ?

thanks.
[Motorola Droid 4] smartass101:
Yes, I used bluetoothctl on Debian 8 and pairing with another Android phone also worked well.

I noticed no such problem. After first bootup it just asked me how I wanted to use, it I told it to use it as general removable media and everything seems ok.

I'm not sure, I think the nightlies are on a newer code bade, safer to wipe.

BTW, there was a new snapshot released today, not sure why. cmxlog does not show changelogs for snapshots unfortunately. I'll wait for a CM blog bulletin about this snapshot and then I'll upgrade if it seems worth it.
[Motorola Droid 4] Septfox:
[MENTION=3457922]stargo[/MENTION]

I've been nosing around trying to understand some memory stuff...I still don't get a lot of it, to be honest. But something caught my eye: VmallocTotal.

It looks like VmallocUsed is about 60mb during typical usage and only fluctuates in minute amounts, but the Total is set to something like 376mb. Why such a huge value? Is it hurting us at all (staying permanently tied up), or is this only the theoretical maximum memory that could be allocated via vmalloc?

Edit: I kind of understand now; Vmalloc maps fragmented physical memory into contiguous virtual memory to use, and the probable reason for it only fluctuating slightly is the memory compactors keeping the physical memory more or less contiguous...something like that?

And another thing...I believe it's been brought up before, but I can't find it and this thread made me think of it again. Is there anything we can compromise on to gain additional headroom?

Edit: also, do we have linux's memory compaction enabled in addition to ART's compaction?
[Motorola Droid 4] wsemi:
One of the fixes is the Weather service, with the new build cLock can show the weather.
[Motorola Droid 4] Bobcus Leper:
[MENTION=3457922]stargo[/MENTION],

? taguoN 0.7 diordnA

;)
[Motorola Droid 4] JLPDA:
Unfortunately, I haven't been able to go from CM12 to CM13 due to the bluetooth not pairing with my Pioneer AppRadio in my car. I'll give the new Snapshot a try. Hopefully, the BT will work properly.

Assuming I can move to CM13, how best to move all my apps and data that are currently installed on my SD card (non emulated, but, the physical SD card)? Can they be reinstalled on the SD Card with CM13? When I went from SlimKat ROM to CM12 I merely had to use Titanium Backup to restore everything.
[Motorola Droid 4] Septfox:
Is the battery workaround for 1% increments broken in current nightlies? All I've gotten since finally updating from 2016-03-02 to 2016-08-19 is 10% increments down to 20%, where it switches to 5% increments. I tried performing a clean flash in case something in my userdata was somehow screwing it up, but that had the same result.

Titanium Backup copies the base package, and when you restore it executes a standard app installation, then restores the app's data. I think you'll have to manually move it back to the SD card after.

And in CM13+, you need to adopt external SD cards to make them eligible for the built-in App2SD, which if you choose to do, reformats them and essentially makes them non-removable (e.g. if you take it out and turn on the phone, it's not going to appreciate it). It's kind of a pain. You can move apps to the fixed internal storage right off the bat, though, so there's still that.
[Motorola Droid 4] JLPDA:
Thanx for the clarification. Mute point, just did a clean flash of the latest snapshot and BT still won't connect with my Pioneer AppRadio SPH-DA210. Guess I'm stuck with CM12 until I decide to switch devices.
[Motorola Droid 4] Careless_:
July 22nd build date installed.

Bluetooth stuttering is still an issue in recent builds after it was supposedly fixed.

I use bluetooth to listen to music every day, and have tried 4 speakers now. I went back to CM12 and didn't have any issues, tested for 3 days.

Sometimes have to restart more than once to get it to work.
[Motorola Droid 4] fokkewolf:
Anyone tried the latest snapshot (Aug 20)? Is bluetooth audio stuttering resolved?
[Motorola Droid 4] Careless_:
apparently it was resolved long before the July 22nd I am currently using- but I still get it, and often.

are you experiencing the stuttering in your current build too? which one?
[Motorola Droid 4] Careless_:
i guess this phone's support is now dead, as it's been a while since someone else posted in here.

does anyone recall which CM13 build did NOT have the Bluetooth stuttering issue? I'd like to go back to that version. all the latest builds have the same issue. tested on multiple BT devices.
[Motorola Droid 4] Bobcus Leper:
No. CM13 is the problem. Bluetooth has borked in the CM13 code, not just for our devices.

The RAZR and D4 aren't dead. CM13 is in the finished stage. I'm sure someone like stargo is seeing if we can get nougat on these phones.
[Motorola Droid 4] Careless_:
I was unaware. so it's not a problem plaguing only our phones. At least that's somewhat comforting. lol

thanks for the update, Bobcus.

i am also awaiting some nougggg- as is everyone!
[Motorola Droid 4] Septfox:
Yea, you've gotta keep in mind that stargo has a life and all, and isn't paid to do this stuff. I wouldn't be surprised if he's taking a breather from tearing his hair out trying to get the remaining performance issues tamped down.

I've been and-and-off testing the CM13 nightlies for the Amazon Fire HDX 8.9", one of the things they're having difficulty with is getting bluetooth working right.

Not saying that it's the same issue as ours, but it suggests that enough things changed in the BT stack between Lollipop and Marshmallow to cause problems and not just be a straightforward upgrade.
[Motorola Droid 4] Careless_:
dude lol... i know people have lives outside of android development. i'm not even sure why you had to mention that. im not forcing anyone to do anything or demanding it be fixed. im just wondering which version doesn't have the issue.
[Motorola Droid 4] Septfox:
Wasn't directed specifically at you. More of a general add-on to Bobcus' post.

Sorry if I came off sounding snippy, wasn't intended.
[Motorola Droid 4] Careless_:
it's just something that goes without saying, I'm not sure why it ever even gets mentioned in a public forum.
[Motorola Droid 4] juan_oso:
Miracast

Hi, another droid 4 user here. I have an issue . I want to do screen mirroring with a DLNA/MIracast dongle similar to chromecast. And while I'm able to play my files trough dlna mode (with bubbleupnp), It's impossible to find my device with miracast mode in this phone. When I go to Settings - Display - Cast , It is supposse to be there a 3 dot menu with the option "Enable Wireless Display", but there's nothing (I want to post images, buy i can't because I'm new here ).

So my question is, Is there a way to enable wireless display (miracast) in this ROM? , is a CM bug?, or is a hardware related issue?
[Motorola Droid 4] Bobcus Leper:
Hi,

I believe that our OMAP-4 devices do not have the proper hardware support to cast to a smart dongle. Therefore, the devs have not enabled software support for it, because it won't work.
[Motorola Droid 4] wsemi:
Call recording

Hi guys,

Do you know if call recording is working on our devices? I've already tried several apps, but wasn't able to make it work so far :(
[Motorola Droid 4] Careless_:
i have not had luck with call recording after CM11 i believe.
[Motorola Droid 4] carlosirai:
Si,

Enviado desde mi E2104 mediante Tapatalk
[Motorola Droid 4] dicer42:
Are security bugs in the kernel fixed?

Looking at the android security bulletins for the last couple of months I'm wondering whether remote kernel exploits get fixed in the kernel shipping for Droid4?

I'm asking cause I was under the impression, that every device has their own kernel tree in the cmod repos? Is that correct?

Stuff like this:

https://git.kernel.org/cgit/linux/k.../?id=23c8a812dc3c621009e4f0e5342aa4e2ede1ceaa

https://git.kernel.org/cgit/linux/k.../?id=34b88a68f26a75e4fded796f1a49c40f82234b7d

As referenced here:

https://source.android.com/security/bulletin/2016-10-01.html
[Motorola Droid 4] u.b.o.o.t:
Correct! Ours is based on linux kernel 3.0 and resides at https://github.com/CyanogenMod/android_kernel_motorola_omap4-common/

Therefore, kernel security fixes have to be (back)ported to our kernel by someone and committed to review.cyanogenmod.org

For the second fix you mentioned, I didn't find any commit that adds them to our kernel and socket.c definitely seems to need that patch: https://github.com/CyanogenMod/android_kernel_motorola_omap4-common/blob/cm-13.0/net/socket.c

But I'm not sure if our kernel version is actually affected by the other one you mentioned... There is no /lib/asn1_decoder.c and I didn't find another place where the patch would fit in...
[Motorola Droid 4] cuppm:
I'm trying to load the latest nightly (2016-10-06) and the latest pico open gapps, but when it goes to install the gapps I get an insufficient space error. I've attached the open gapps install log. I'm using the 3.75 version of safestrap and installing to the stock slot. Is there something I should be doing differently?

I've also noticed that I can't wipe the /sdcard partition, says it doesn't have permissions.

EDIT 1: I tried flashing the last snapshot (2016-08-20) with pico and it completed fine. There's a difference in size between the NIGHTLY and the SNAPSHOT of a little over 15 Mb.
[Motorola Droid 4] Bobcus Leper:
Hi,

As of September or later, the 700MB system partition is not large enough to contains the ROM and the GApps. You are not doing anything wrong.
[Motorola Droid 4] Careless_:
So anyone using September or later needs to create a larger rom slot, is what you're saying?
[Motorola Droid 4] Bobcus Leper:
Yes. That is exactly what I am saying. I am sorry for the confusion.
[Motorola Droid 4] Bobcus Leper:
Hi,

I think that I have found the smallest working 6.0.1 Gapps for our small stock system partition - A-Gapps.

https://docs.google.com/uc?id=0B4rcO7KguyMaOE94a3BUZzNYWVU&export=download
[Motorola Droid 4] stargo:
Hi,

I can remove some dictionaries and the HexoLibre theme from the build, which should hopefully make enough space for Pico gapps again.

EDIT: removed HexoLibre for now, maybe this is enough. If you want to install it to /data/ again, you can get the apk here: http://droid.cs.fau.de/cm-13.0/HexoLibre.apk

Cheers,

Michael
[Motorola Droid 4] schmatzler:
Damn. I really loved that theme :( Do I really have to compile it by myself now? :crying:
[Motorola Droid 4] Jishkah:
Just curious, but is the 700MB max /system/ partition size a limitation of the filesystem used? Or is that something that a tweak to Safestrap/TWRP could fix?
[Motorola Droid 4] stargo:
Hi,

The partition table is signed and the signature is checked by the bootloader during boot.

Cheers,

Michael
[Motorola Droid 4] Puppymang:
well i feel a little stupid. i tried installing cm13 on rom slot 1 with my stock slot having 5.1

used latest nightly and pico gapps then i booted and the android gave me some error about encryption and that it needed to factory reset. i just tapped around on the screen trying to exit the encryption screen and it did its "factory reset" then got stuck on telling me the same thing afterwards so i thought id go back to safestrap and wipe the rom slot but somehow all of this messed up safestrap. whenever i tried to access it all id get was a black screen

figured i ****ed everything and decided to RSD and start over but after the DROIIIDD sound it just gets stuck with the boot animation and goes nowhere
[Motorola Droid 4] schmatzler:
That's not a big problem. You can still put the device in Fastboot mode and unbrick it with this tool:

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

Afterwards, install Safestrap on the stock ROM and try again.
[Motorola Droid 4] Puppymang:
ill give this a shot. getting pretty desperate here to the point where i cant even sleep

edit: well it boots now but for some reason rooting keeps on failing. better than nothing though

ill figure out the rest

thanks m8
[Motorola Droid 4] Bobcus Leper:
What's Android 7.1?:confused:

http://droid.cs.fau.de/mystery.jpg
[Motorola Droid 4] u.b.o.o.t:
It's Nougat reloaded, but still beta ;) https://en.wikipedia.org/wiki/Android_Nougat
[Motorola Droid 4] Bobcus Leper:
Guess what stargo and joojoobee666 have whipped up.

http://droid.cs.fau.de/jjb666/cm-14.1-20161102-UNOFFICIAL-maserati.zip
[Motorola Droid 4] moodroid:
Thanks stargo and jjb - all the basics seem to be working:)

I know it's rediculously early to be asking questions on this, but I couldn't seem to get it to work in the stock slot - is that what we'd expect, or did I mess up?

Also, would the CM13 kernels work with this?

Thanks again.
[Motorola Droid 4] schmatzler:
Wow! It already runs absolutely amazing, apart from some graphical glitches here and there.

Thanks to everyone involved for making this happen. It's amazing to see that this device came out with GingerBread 2.3 and now goes up all the way to Android 7.1! :good:
[Motorola Droid 4] Bobcus Leper:
Wow! I didn't expect the first build to have all of the basics working. I have a RAZR, so i'll have to wait until stargo releases a build for the xt912.:good:
[Motorola Droid 4] stargo:
I assume nobody tried to make a phone-call ;)

It will come, but I haven't tested on xt910 yet. I'll need to fix the major bugs first before I look at the three other devices (from which I can only test 2, I have no VZW Razr, only the UMTS one).
[Motorola Droid 4] Bobcus Leper:
Its here!

http://droid.cs.fau.de/cm-14.1/
[Motorola Droid 4] schmatzler:
cm-14.1-20161105-UNOFFICIAL-maserati.zip: My GSM SIM is not recognized anymore :P Worked in the previous build, at least data.
[Motorola Droid 4] moodroid:
It recognized my GSM SIM ok, and phone calls work now too:)
[Motorola Droid 4] joefuf:
Might be meant for the next thread, but has anyone that installed the new cm14.1 and the Pico GApps experiencing any issues with downloading apps from the Play Store? I get Error Code 963 if I attempt any downloads. Granted this was the first time I ever created and installed to a ROM slot that wasn't stock, everything else seems to be running fine except that one aspect.
[Motorola Droid 4] zys52712:
Format the data partition in safestrap to ext4
[Motorola Droid 4] joefuf:
Is that just a simple Wipe of the Data partition or is there something that must be done to make is ext4?
[Motorola Droid 4] Bobcus Leper:
I posted this in the RAZR thread.