yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] joefuf:
Thanks, I didn't know about this new depth of configuration.

I went to Advanced > Settings > and checked the box that said "Use rm -rf instead of formatting"

Then I went Home > Wipe > Advanced Wipe > Checked Data > Clicked the top bar where it said "Repair or Change File System"

I noted that my current file system is ext3.

I clicked Change File System. I clicked EXT4, and I swiped to change. I get a Format Complete Successful message. I installed the ROM again.

While it is installing, I noticed that the command line text says "detected filesystem ext3 for /dev/block/system" so does that mean that my EXT4 change did not process correctly?
[Motorola Droid 4] zys52712:
Do not check the box that says Use rm -rf instead of formatting, I think what Bobcus Leper meant is not to use rm -rf. I had the box unchecked and it worked.
[Motorola Droid 4] joefuf:
Yup, that was it! Thank you both for the assist.

And just so I don't walk away knowing only what buttons to press, what is it that I just did? I understand that I made the filesystem go from EXT3 to EXT4, but why can't the ROM install apps to an EXT3 filesystem?
[Motorola Droid 4] Bobcus Leper:
Stargo issued a commit so that EXT4 needs to be the default file system for Nougat. Safestrap 3.76 and later will do this automatically for us. EXT3 had some issues with Nougat. That's all I know.
[Motorola Droid 4] Puppymang:
this might be a little late seeing as cm14.1 is in the works but ever since i started using cm13 i noticed that whenever i have data drops and it recovers it doesnt automatically reconnect to LTE or 3G it just stays without data until i turn on/off airplane mode to reset it.

this wasnt a problem in cm12.1 so im kind of bummed but cm13 feels so much smoother so i cant go back
[Motorola Droid 4] moodroid:
Does anybody know if CM14.1 can be used in the stock slot?
[Motorola Droid 4] Careless_:
so it won't connect to the cell phone network and allow phone calls yet?
[Motorola Droid 4] Bobcus Leper:
That has been fixed in the latest build(I think).

http://droid.cs.fau.de/cm-14.1
[Motorola Droid 4] moodroid:
Yeah - phone calls seem to work fine now.

Is anyone else having permission problems accessing the internal storage?
[Motorola Droid 4] zys52712:
Safestrap 3.76? Do you think it will have a newer TWRP base?
[Motorola Droid 4] Bobcus Leper:
I don't think it will. My guess is that stargo will be issuing a new version to fix Nougat compatibility.
[Motorola Droid 4] Careless_:
are we gonna get a dedicated thread goin soon?
[Motorola Droid 4] stargo:
Yes, when I get some spare time (on the weekend at the latest). Please don't create a cm-14.1 thread yet.

Cheers,

Michael
[Motorola Droid 4] Careless_:
thanks! i'll keep an eye out for it. :cyclops:
[Motorola Droid 4] Bobcus Leper:
http://droid.cs.fau.de/jjb666/Kernels/cm14/
[Motorola Droid 4] Careless_:
waiting for info thread b4 i try it.

is bluetooth fixed in nougat??
[Motorola Droid 4] zys52712:
The kernel works fine, and bluetooth file transfers work.
[Motorola Droid 4] joefuf:
Never played around with kernals before. What do you guys find the benefit being? Is it possible to overclock much on this phone without totally wiping out the battery in an hour or something?
[Motorola Droid 4] Careless_:
i mean't the broken BT audio from CM13.

i've had to restart my phone up to 4 times to get an non-stuttering bluetooth audio stream to a BT speaker.

hoping that's gone for good
[Motorola Droid 4] zys52712:
It makes your phone run smoother, for me there isn't much difference in battery life (mine can only do 1.3ghz). It drains my battery just as fast as with out the oc. :p
[Motorola Droid 4] Bobcus Leper:
The difference in day to day usage is extremely marginal. Though, you will get the added benefit of having custom CPU governors and I/O schedulers.
[Motorola Droid 4] Puppymang:
i think this might be a problem with your device. i have a cheap chinese bluetooth headset and it works great paired up with my phone. no stutters or issues
[Motorola Droid 4] wsemi:
What's the status of CM13 for our device now? It seems the official nightlies have been stopped since Monday. Will there be any more nightly or snapshot release of CM 13?
[Motorola Droid 4] Bobcus Leper:
I think that CM14.1 nightlies for supported devices have taken over.
[Motorola Droid 4] Careless_:
it's not at all a problem with the device. that's almost insulting considering the amount of discussion it's had (within this thread), and it was never repaired because it is part of CM13's "broken bluetooth" and has nothing to do with my Droid 4, or anyone's for that matter.

try playing a music/audio stream to a bluetooth speaker. it will eventually happen.
[Motorola Droid 4] Puppymang:
i was very much aware of your discussion on the subject and feared moving to cm13 because of it (along with other things) but eventually decided to bite the bullet despite seeing your discussion about the broken bluetooth. i thought it was something i could live with as i dont actually use bluetooth that often and to my surprise it actually seemed to work without a problem.

sorry if my initial post was offensive

heres what happens when i use bluetooth audio stream. i turn on bluetooth on both devices, connect to my phone, and use the headsets controls to start playing music. audio begins and continues playing normally but on the phone the player pops up saying "music has stopped working". if i press ok the music player will go on a crashing loop and the music will start and end immediately. if i dont press anything the music will continue playing.

when connect i to my pc using bluetooth the same thing happens if i click on start playing music button that pops up on the bluetooth remote control

i did notice that i had to press play a few times on my pc before the music started playing. it would crash before playing the first few attempts.

audio did not stutter at all though. i found it weird that it just kept making the music player crash so i tried another mp3 as the original mp3 i used was almost 10 years old. the second mp3 file has no crashes and the audio streams fine with the remote bluetooth controls working as intended even while transfering files and playing music at the same time. unfortunately i dont have any more bluetooth headsets/speakers so i cant test around with other devices.

i suppose i would need to test the bluetooth audio for a long time to see if the stuttering problem shows up but ill admit cm13 isnt the most stable thing in the world as ive had multiple crashes while playing video files using H/W decoder on mxplayer if i pause and resume the video multiple times.

what speaker do you use? have you tried other bluetooth devices or just your speakers? maybe your mp3 files are faulty like the one i tried?

using cm13 from 10/22 build and the OC kernel

headset i use https://www.amazon.com/dp/B00Q2VIW9M/

pc's bluetooth card https://www.amazon.com/dp/B00HF8K0O6
[Motorola Droid 4] Careless_:
there is absolutely positively no way that my mp3 files are "faulty".

and i've tried playing on about 6 bluetooth speakers now, and all my mp3 files worked fine in cm12 roms and every version before that.

it's a CM13 bluetooth stack issue, and apparently it's never going to be fixed.
[Motorola Droid 4] Bobcus Leper:
New builds!

http://droid.cs.fau.de/cm-14.1/
[Motorola Droid 4] u.b.o.o.t:
I just updated my stock slot to latest nightly (cm-13.0-20161212-NIGHTLY-maserati.zip) via Safestrap+adb sideload from an earlier cm13 nightly and seemingly bricked it :(

Is the nightly broken?

Or was abd sideloading a bad idea?

Flashing went through fine, but after reboot, phone gets stuck after the red M-Logo, i.e. no CM logo comes up, but phone's back gets hot and backlight stays on (black screen).

Also, I cannot enter Safestrap anymore.

Where to go from here?

I am able to enter boot menu, but BP Tools don't fire up Safestrap (phone gets stuck & hot after M-Logo). If I go to stock recovery, it rejects CM13 zip file.

I'd like to keep data partition and just flash system partition to last working CM13 nightly... Is there any way to achieve this? I don't wanna go the stock rom fastboot recovery route...
[Motorola Droid 4] stargo:
Hi,

Yes, sideloading on the stock-slot removes safestrap :(

If you can still connect with adb while the phone is "booting" (it's using the Moto kernel and will not boot completely) you might be able to restore the logwrapper binary (and the rest of safestrap).

If this doesn't work then your only option is restoring factory images :(

Best regards,

Michael
[Motorola Droid 4] u.b.o.o.t:
Thanks! This seems to work! But adb locks up after a while so it may take several tries to complete.

But I didn't copy anything yet, just remounted /system as rw and looked around a but then had to reboot because adb shell became non-responsive.

But now, I cannot get root anymore in adb shell. It turned out that SUID is not set anymore on /system/xbin/su *WT?*

How can that happen!? How can I become root now? Cannot remount system as shell user...
[Motorola Droid 4] stargo:
Hi,

Hmm, good question. Maybe the Motorola ramdisk removed the s-bit somehow when you remounted rw, but that would be a wild guess...

I think that didn't happen to me when I did a sideload a year ago.

Hmm, maybe run an exploit (saferoot). But you might be out of luck now :(

Best regards,

Michael
[Motorola Droid 4] u.b.o.o.t:
...it's the only plausible explaination... Mind that stock recovery also somehow checks if 1.) the device ever has been rooted and 2.) if it is rooted currently.

Anyhow - I restored stock system partition via fastboot and it's working again...
[Motorola Droid 4] Bobcus Leper:
Stargo has been busy backing up for the end of CyanogenMod.

http://droid.cs.fau.de/Official_CM_Builds/

https://cyngn.com/blog/cyanogen-services-shutting-down

Edit: An official statement from CM themselves. LinageOS looks like it will be the future.

https://www.cyanogenmod.org/blog/a-fork-in-the-road

Edit2: LineageOS is official. http://lineageos.org/
[Motorola Droid 4] moodroid:
Hi Bobcus,

Thanks for the info - I didn't know anything about this. If you had to guess, what do you think this will mean for us?

Cheers
[Motorola Droid 4] Bobcus Leper:
Hello,

I think that the latest CM13 Snapshot will be the last CyanogenMod build for our devices. I think that stargo will continue nougat builds for our devices, until the CM source code is made into a new official ROM.

Edit: An official statement from CM themselves. LinageOS looks like it will be the future.

https://www.cyanogenmod.org/blog/a-fork-in-the-road

Edit2: LineageOS is official. http://lineageos.org/
[Motorola Droid 4] stargo:
Hi,

Spot on, but I'll not be able to build a new nougat ROM in 2016, as I'm off to 33c3. If anyone else is there, you can find me near the ICMP assembly or call me at 2746.

Cheers,

Michael
[Motorola Droid 4] mifritscher:
2016 doesn't last sooo long anymore *grin* Have a lot of fun at 33c3 :)
[Motorola Droid 4] mifritscher:
According to http://www.phoronix.com/scan.php?page=news_item&px=Linux-4.10-ARM-Tegra-More, the Linux kernel 4.10 got official support for Droid 4!
[Motorola Droid 4] _dgr:
Note: 'minimal support'. No Display or anything fancy.

patchwork.kernel.org/patch/9424287/
[Motorola Droid 4] schmatzler:
I was just surprised to see that CyanogenMod is dead now and the remaining developers moved over to be LineageOS.

Looking forward to LineageOS builds for the good old Droid4 ^-^
[Motorola Droid 4] mifritscher:
[MENTION=7955976]_dgr[/MENTION]: Yes, but is it a step forwards and a nice surprise :)
[Motorola Droid 4] Bobcus Leper:
Check the title of the thread.;) Many thanks to stargo!

http://droid.cs.fau.de/lineage-13.0/
[Motorola Droid 4] schmatzler:
Nice! I updated from the last CM13 build without any problems.

Interesting bootlogo. Haven't seen that in a long time. :P
[Motorola Droid 4] Bobcus Leper:
Yeah, that bootanimation is the default one in lollipop and above. I don't think this will be the official bootanimation for Lineage OS.
[Motorola Droid 4] Careless_:
EDIT: nevermind, wrong OS thread. thought this was 7.0
[Motorola Droid 4] tobby88:
Hi

I am trying to format my external sdcard as internal storage (or mixed). But when entering

sm partition disk:179_32 public

or

sm partition disk:179_32 private

or

sm partition disk:179_32 mixed 90

I always get:

Error: java.lang.IllegalStateException: command '14 volume partition disk:179_32 public' failed with 'null'

Any ideas?

The same card worked great as mixed storage in my Photon Q.

//EDIT: Nevermind. I didn't change anything but after the maybe 20th try it suddenly worked.
[Motorola Droid 4] schmatzler:
I was tired of waiting for new builds of LineageOS13, so I did it myself.

New build

without root

:

lineage-13.0-20170129-UNOFFICIAL-maserati.zip

MD5SUM: a3c156b563f190946f9821a8b9b4e5d0

New build

with root

:

https://schmatzler.de/motorola-xt894/lineage-13.0-20170129-UNOFFICIAL-maserati-root.zip

MD5SUM: 806eb823fab90468ac02e6312a7b5da2
[Motorola Droid 4] Mr Wolf:
Hi, I've just formatted my Droid 4 and installed CyanogenMod 13. For now, the only big issue I've found is bluetooth: I can't pair the phone with my computers and it gives problems with other devices.

I'd like to try LineageOS. Anyone can tell me if bluetooth works well?

Thanks!
[Motorola Droid 4] Bobcus Leper:
New builds by stargo are live.

http://droid.cs.fau.de/lineage-13.0/
[Motorola Droid 4] Careless_:
try turning wifi off and rebooting and making sure wifi is off when you start, and see if it connects.

sometimes bluetooth stack has an issue where it won't connect to new devices, or audio will not play properly if that's what you're using it for.

sometimes it takes one restart. sometimes it takes 3 or 4...

i have gotten it to go back to normal by stopping a bunch of services and restarting bt connections and whatnot- but its often faster to just reboot it.

problem with CM13, not this rom in particular.
[Motorola Droid 4] schmatzler:
I'm not able to pair the Droid4 with my Windows 7 PC either.

I can send the pair request from the Droid, and the PC will display a code. I can accept the same code on the Droid and it will show my PC as paired, but Windows 7 will always say that the code was wrong and fails. When initiating the pair from the PC side, nothing ever happens on the Droid.

I have no problem transferring files with Total Commander, though. Just the pairing process doesn't work correctly.
[Motorola Droid 4] JLPDA:
Same issue with pairing to my Pioneer AppRadio. Have to stick with 12.1 until this works.
[Motorola Droid 4] OGdroidster:
Have you tried to going to developer option and scrolling to usb configuration and changinging it to mtp instead of charging.
[Motorola Droid 4] u.b.o.o.t:
Beware: lineage-13.0-20170201-UNOFFICIAL Android Security Patch Level is December 1st 2016...

Google published quite a lot of security patches in January: https://source.android.com/security/bulletin/2017-01-01.html

February looks busy, too: https://source.android.com/security/bulletin/2017-02-01.html

Are there any attempts to merge these patches into Lineage yet?

https://review.lineageos.org/#/q/branch:cm-13.0+CVE-2017 lists only two patches at the time of writing (https://review.lineageos.org/#/q/st...meworks_base+branch:cm-13.0+topic:asb-2017.01)...
[Motorola Droid 4] Bobcus Leper:
They already are in LOS. Stargo hasn't backported the security patches to our device because he has been busy.
[Motorola Droid 4] dicer42:
Also be aware that a lot of security fixes do not contain a CVE id because it was often patched before one was assigned. From my experience you also can't go by patch date as commits are often cherrypicked and keep the old dates (ie the recent libopus fix, which was fixed in upstream in July 2016)

So it's pretty hard to figure out if everything has been ported.

Not sure what stargo has to port for maserati though? Most of the fixes are shared with all other devices (ie AOSP code). Only problem are the hardware driver fixes, which will probably never be fixed, since we don't have sources. Just blobs. Another reason why people hate firmware blobs.

One thing I noticed though is the kernel: Last time I checked a couple of months ago, some kernel security fixes were not ported to the maserati kernel.
[Motorola Droid 4] schmatzler:
Just made a new build.

lineage-13.0-20170211-UNOFFICIAL-maserati.zip

MD5SUM: d7fe6472f2495e88d7d03aac37c41af3

Android patch level is now January 1st, 2017. So it looks like we got our security patches.
[Motorola Droid 4] kero2005:
how to root this device ? :(
[Motorola Droid 4] sd_shadow:
RootMaster

http://xdaforums.com/droid-razr/development/computer-xt912-root-exploit-t2855364

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

or saferoot

[Root] Droid 4 (XT894) Jellybean with SafeRoot http://xdaforums.com/droid-4/development/root-droid-4-xt894-jellybean-saferoot-t2816462
[Motorola Droid 4] tobby88:
https://xdaforums.com/showthread.php?t=2207384
[Motorola Droid 4] u.b.o.o.t:
Has anyone managed to upgrade from [MENTION=3457922]stargo[/MENTION]'s unofficial lineage 13.0 builds to official nightly from https://download.lineageos.org/maserati ?

For me, lineage-13.0-20170210-UNOFFICIAL-maserati.zip -> lineage-13.0-20170224-nightly-maserati-signed.zip failed, saying something like "incompatible update".
[Motorola Droid 4] stargo:
Hi,

There are two problems with upgrading to official builds:

The official builds are signed with different keys and the migration-patches which can be used to migrate to the new keys only work on 14.1. This means you have to wipe /data/ when migrating from a CM build or one of the unofficial CM/LineageOS-builds.

The current downloadable builds are broken, as they are block-based OTAs which can't be installed on phones with locked BL and safestrap. I've requested them to be removed. I don't understand why they are block-based when built by the LineageOS build-system.

EDIT: The LineageOS build-system does not support the hacks needed for our devices with locked bootloader and safestrap (due to their use of signed-builds which require block-based OTAs). I've removed the devices from the build-schedule: https://review.lineageos.org/#/c/163953/

Cheers,

Michael
[Motorola Droid 4] K_Meleon:
Hi!

I tried to install

https://droid.cs.fau.de/lineage-13.0/lineage-13.0-20170219-UNOFFICIAL-maserati.zip

into slot1 using Safestrap 3.75 for unused partitions. Installation ends without any error. But when I try to boot, the display backlight stays on (after the Motorola logo appeared), but it seems to be stuck there, so nothing else happens! Then I tried to install it into safe slot, but safestrap reports "system partition has unexpected contents after OTA update.".

What am I doing wrong? Can somebody help me? I installed CM13 without any problems in all available slots.

Thank you very much! BR
[Motorola Droid 4] K_Meleon:
I just took a different "Droid 4", did a factory reset, installed safestrap and then LineageOS...it gets installed in safe slot, but display stays black with backlight turned on...:confused: . rom slot 1 seems to be working now on that Droid 4. Might this issue be related to what is mentioned here

http://www.internauta37.altervista....strap-375-unused-partitions-preinstall-webtop

??
[Motorola Droid 4] Bobcus Leper:
Did you install the unofficial LOS? The official LOS builds are broken. You can get the unofficial builds from here.

http://droid.cs.fau.de/lineage-13.0
[Motorola Droid 4] K_Meleon:
Yes, I tried them also first, but then I read stargo's comment in https://xdaforums.com/showpost.php?p=71250972&postcount=494. Since then I tried only the unofficial build from him. That the LineageOS build doesn't boot from safe slot is hopefully related to the uncompatible ramdisk.img, though I didn't verify it. So, the issue for the other Droid seems to be OK. But what's wrong with my first and mainly used Droid? LineageOS neither doesn't boot from virtual slots (slot1) nor from safe slot. But even http://droid.cs.fau.de/Official_CM_Builds/maserati/cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y3-maserati.zip seems to be stuck with the same error booting from slot1, so it's not LineageOS related. Since I wiped the stock slot and installed CM13 in there I was very satisfied with this solution and didn't use any other slot.

While I wrote the text above I started to re-install LineageOS to safe slot...and guess what...the error message "system partition has unexpected contents after OTA update" disappeared. :)

Since two weeks I have some issues with the battery. Sometimes it refused to charge to more than 3%. So I completely unscrewed and removed the battery today, waited 5 minutes and put it in again. Charging to 100% seems to be possible again (at least one time today). Probably my issues are related to that empty battery?
[Motorola Droid 4] Bobcus Leper:
Hi,

I'm going to guess that when you flashed the broken LOS ROM, it formatted your partitions to EXT4. Therefore, your phone will not boot. Format everything except /data to ext3, then reflash the latest unofficial build.
[Motorola Droid 4] Bobcus Leper:
Hi,

It looks like locked bootloader, omap-4 devices will once again be receiving official LineageOS 13.0 weeklies again.

https://github.com/LineageOS/hudson/commit/7aef60eff6fb527f74038a1ecc17a614695b3176

All credit is to stargo. Do not thank this post. Give the credit where it is due.:good:
[Motorola Droid 4] K_Meleon:
Good hint! But I checked the filesystems and all partitions were formatted to ext3. The main Droid 4 still doesn't boot. Do I need to wipe the internal (8 GB) flash?
[Motorola Droid 4] Bobcus Leper:
Hello again,

I would select the stock slot under the slot manager too see it the partitions show up as 0 MB. If they do, you will have to flash the stock ROM using rsdlite.
[Motorola Droid 4] joefuf:
Can these Lineage ROMs be flashed over each other like we did with CM? Can I flash the 3-2 ROM over my 2-19?

Also is there anywhere to view a comprehensive changelog or just what is in the OP on this thread?
[Motorola Droid 4] K_Meleon:
You mean the slot manager in safestrap?

Probably I have to explain the setup I am using:

After some months of using CM10-CM12 in slot1-4 I decided to wipe the stock slot for CM13 (safe slot was too small for CM13 and gapps) and let it run from there. As CM13 got too slow now and is not able to update anymore, I decided to try LineageOS without gapps. But I would like to have a fallback solution, so I'd like to use the safe or virtual slot first. I'd guess, that I didn't wipe the internal storage memory since 4 years now.

BTW: Did anyone manage to boot and use LineageOS in stock or safe slot?
[Motorola Droid 4] wsemi:
I was able to dirty flash strago's unofficial LOS13 on CM13 without any issues.

If nothing works you may reset your phone with RSDlite, but note that it will format the internal storage too and get a new label as well.
[Motorola Droid 4] Bobcus Leper:
I always install ROMs to the stock slot.
[Motorola Droid 4] joefuf:
Random issue I've been having with this ROM.

Never seen this before, but the FM transmitter in my car has a 3.5mm headphone jack and will not register on the phone as being plugged in, so the phone keeps playing out of the speaker. But if I plug in my Skullcandy headphones, it starts playing through those just fine.

Has anyone else experienced that?
[Motorola Droid 4] Puppymang:
it might be possible that the safestrap file that manages your partitions got corrupted. long story short youre probably going to have to RSD and wipe the memory

something similar happened to me when i tried to have CM12.1 and CM13 at the same time. even when i wiped and reinstalled it would bug out and eventually i realized i had to remove the safestrap folder from the storage and let it create a new one
[Motorola Droid 4] joefuf:
Has anyone experienced random power offs with this ROM? I'll put the phone on my pocket and it'll randomly turn itself off which kills my battery on reboot. Today on the train, while just swiping through screens, I witnessed the screen just go black and the device turn itself off.

Is this the ROM or a hardware issue on my end?