yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] schmatzler:
Usually once in two weeks my phone does not wake up anymore and pressing Power doesn't turn it on either, it seems dead but it isn't.

I have to press Power + Vol Down (or Up?) to get it back to life. So if that happens to you, too - it seems to be normal.

It has never happened while I was using it, though. I had random shutdowns before getting a new battery, so that may be the issue with your phone, too.
[Motorola Droid 4] joefuf:
Nah, that's not really my issue. I have seen it just shut off in my hand. I had a similar issue when I had a loose battery on an old Droid 4 and tightening the screws on the battery fixed the issue. In that case, it would at least go through the Powering Off message on the phone.

I just bought the phone I have now off eBay from a guy who claimed it was always in perfect condition. I'm starting to not believe that though. I posted above how the headphone jack doesn't work right (one earbud on my Skullcandy headphones and not at all on the 3.5mm FM transmitter in my car). Today when I got home I took off the back and went to see if a screw was loose (and it was, a little), but the adhesive label flap was clearly previously lifted up at some point.

Hopefully that little screw turn helps things. I'm not a fan of the broader battery issues and charging readouts on this ROM, but if this issue is resolved, I think I can manage.
[Motorola Droid 4] Careless_:
The battery screw terminals do need removal and re-tightening from time to time. I've had that issue on these phones quite a bit. (I own two). if you remove the battery completely, you can clean the brass contacts on the underside of the battery flap and it will last a good 6 months before any battery issues arise.
[Motorola Droid 4] joefuf:
I never really had this kind of issue with my other phones, and I had three Droid 4 devices over the years. The phone will literally shut right off in my hands in the middle of typing a text message, from the time it enters my pocket to the time it comes out, or sometimes when I slide the keyboard back in after sending a text message or just navigating the menus. I'll check the screws again tonight when I get home, but I have to imagine that's a software thing.

On top of that, the battery life is really hard to nail down. I tried draining my battery completely today and plugging it in while leaving it off to charge. After two hours it hit 100% and when I booted up, the phone thought it only had 20% and had to take another hour or so to charge to 100%. The reboots really don't help either because that'll take a good percentage off the projected life.

I guess I can try swapping another battery or the screws from another one of my Droid 4 phones into my newer, current one. I'm just getting close to going back to where I was stable on CM 11 so I can at least get three or four hours of Screen On Time and don't have these power issues.
[Motorola Droid 4] Careless_:
maybe the temp sensor on the battery interconnect board is failing or not making a good connection. the phone would just shut off as a preventative measure in that case.
[Motorola Droid 4] joefuf:
[IMG="Battery Comparison"]http://i.imgur.com/oadqaAi.jpg[/IMG]

So I swapped out the battery from the new phone I got off eBay and replaced it with the one from my more recent phone that had a broken charging port. As you can see in the picture, the right contact on the battery to the right is pretty badly degraded. It makes perfect sense that this guy had a loose connection. It's only been one day, but I've experienced marked improvement. NOW I see the positive experience you guys were talking about with this ROM. Gonna leave it on Airplane mode on the flight I'm about to board, but if it makes it all five hours, I'm set with this. I love this phone again. Thanks [MENTION=3457922]stargo[/MENTION].
[Motorola Droid 4] Careless_:
i love simple and apparent fixes. wish they could all be that way.

lets hope it's fixed.
[Motorola Droid 4] nomadicg00se:
So, I flashed this ROM and played around with it for a day. Installed the 1.4ghz ULV kernel for it as well. Woke up and it was frozen. Turned it off, and couldn't get it to boot to anything but the recovery menu. (Vol up+down+power) I then tried to wipe and reflash the ROM, but the phone died during the process. (Good job, me!) Now I've tried using RSD Lite to flash back to stock, and it says "failed flashing process. 20/25 flash system "system.img" -> Phone returned FAIL". I used VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml, which I believe is 4.1.2. My real question here is, how do I get back to stock when I updated to 6.0? I'm assuming that 4.1.2 isn't going to work, because I flashed this custom ROM.

Any and all help will be greatly appreciated--especially since this is an older phone.

Edit: have tried using moto-fastboot.exe to flash 4.1.2, and also to erase everything. When trying to erase within moto-fastboot.exe it yields the error "INFOCommand restricted - FAILED (remote: )"

$10 paypal to the one who helps me get this phone going, if it is possible.
[Motorola Droid 4] Septfox:
Sleep of death is one of the more annoying side-effects of too little voltage. Assuming you can get it going again, try a higher voltage kernel next time. And disable hotplugging, it's kind of hit-and-miss after KitKat.

The Droid 4 is kind of a pain in the ass due to its locked bootloader...everything done on it is done by booting another kernel after loading the stock one. While this workaround allows our lovely maintainer to give us nice things like...er...everything that isn't stock, it also ties his hands on some more exotic operations.

On the bright side, this means you're still on 4.1.2; Safestrap hijacks the boot process to load up a newer version of Android from a partition file on the internal SD card (a "slot"). No worries about flashing a ROM and suddenly having a stock-incompatible radio, bootloader, etc etc because technically everything is still stock 4.1.2.

If Safestrap will no longer boot (because /system is borked), and RSDLite doesn't want to complete the flash to restore /system...that might prove to be problematic; stock recovery is utterly, irredeemably worthless for anything other than wiping the internal SD. It's possible (if I recall right) to flash the firmware images yourself with ADB/fastboot, but that shouldn't be much different than what RSDLite is trying to do, if at all. Worth a try, though.

Keep in mind this is from memory, hopefully someone else will catch it if I mess a step up. Instructions:

Download Minimal ADB and Fastboot. Remember where you install it.

Open your firmware xml/zip (I think it's a generic zip, if windows can't handle it get 7zip). Pull system.img out of it and put that in your Minimal ADB and Fastboot directory (where adb.exe and fastboot.exe are).

Boot your phone into fastboot mode, and connect it to your computer.

Run Minimal ADB and Fastboot from your start menu, or MAF32.exe if you still have the folder open.

Type the following in, without quotes: "fastboot flash system system.img". Hit Enter, cross fingers.

Hopefully it'll pick your phone right up and attempt flashing manually.

Assuming it finishes without bailing, run RSDLite again and retry flashing the firmware package; it failed at 20/25 after all, which means there was still one or two more files after the system partition to flash (plus reboots between).

Here's hoping it works.
[Motorola Droid 4] joefuf:
Having a weird issue with the keyboard.

A coworker told me to try out GBoard for the portrait touch screen keyboard, and I've been using it this afternoon and enjoying. But when I went to switch to my physical keyboard and type, I noticed that I have to hold the Shift key in order to get any of the Shift characters or symbols. If I hit the ALT key, it opens the symbols and number page of the touch screen keyboard, and I'd have to hold the key in order to trigger the ALT function. I have to change back to the AOSP Android Keyboard in order to use the physical keyboard buttons as intended.

Is there any way that you guys have found that leaves those functions intact? I just want to be able to tap the Shift key and then find the next button to press, not have to press and hold.
[Motorola Droid 4] stargo:
Good news everyone!

The LineageOS build-system was finally able to produce a working build for the Droid 4 :)

You can find the official build here: https://download.lineageos.org/maserati

When migrating from CM (official and unofficial) or Lineage unofficial, flash this first and then directly flash the new image without rebooting.

This build does not include su by default. To get su back, just flash the su (arm) 13.0 addon. The official su-addon does not work on Omap4, you can find a working one at: http://droid.cs.fau.de/lineage-13.0/addonsu/

Cheers,

Michael
[Motorola Droid 4] K_Meleon:
Great news! Thank you very much for your work!

Installing this script was successful (although an error was reported). but I couldn't install the lineageos image. Do I have to wipe the system partition first before installing the image?

Best regards,

K-Meleon
[Motorola Droid 4] stargo:
Hi,

Which errors did you get in both cases? Wiping /system shouldn't be necessary.

EDIT: Did you by any chance try to also install the su addon? It seems the official addon can't be installed on omap4-devices because the update-binary uses cpu-features which are not present in the ARM-core. I've built an addon which actually works: http://droid.cs.fau.de/lineage-13.0/addonsu/

Best regards,

Michael
[Motorola Droid 4] stargo:
Hi,

The first step actually failed:

This means that your /data was not updated to the new keys and the subsequent installation failed:

Try manually mounting /data in TWRP before flashing the migration zip (which should then produce no error) and the unmount it afterwards. After that you should be able to flash the official build.

Cheers,

Michael
[Motorola Droid 4] K_Meleon:
Great! That solved my issues! Thank you!
[Motorola Droid 4] xenomorph150:
I just flashed the migration zip, lineage-13.0-20170408-nightly-maserati-signed.zip and the addonsu from http://droid.cs.fau.de/lineage-13.0/addonsu/ - however, my droid 4 is now in a kind of bootloop, just showing the lineageos logo - any idea on how to fix that? Thanks a lot :)!
[Motorola Droid 4] joefuf:
How much free memory do you guys usually have. After a few instances where I had to force reboot my phone when using Chrome and trying to switch to a text message or Reddit, I investigated and found out I was actually using all of my available memory. After paring down the apps that Start at Boot, I managed to get about ~175mb free, but the performance still suffers.

Anyone have a similar experience with this phone/ROM? Any tips and tricks?
[Motorola Droid 4] OGdroidster:
Just boot back into safestrap and wipe that slot and flash something that will boot and work. Thats all you have to do.
[Motorola Droid 4] Shani Ace:
How well or smooth does LOS 13 run on the D4? About a year ago I had a D4 and CM12 was pretty much unusable (CM11 was running okay). The device was constantly lagging, especially when I wanted to use more demanding apps like a browser. ^^

I read the past ten pages of this thread, but nobody already covered this.

Also: Am I right in assuming that the Bluetooth issue from CM13 is fixed in LOS13?
[Motorola Droid 4] t--b:
Have never used CM11 so cannot compare, but LOS13 works fine for me and browsing is okay as well. I do understand it can take a bit longer to show a page than a more modern phone so I do not complain about that. I do not plan to use an older codebase anyway due to security updates that are implemented in the later versions. Security and compatibility is more important than speed imo.

BTW. What is the 'bluetooth' issue you are talking about?
[Motorola Droid 4] Shani Ace:
Yeah that would be important for me too.

Well if the delay is so short that it doesn't enrage the user everytime one wants to open a webpage, I think it will be fine. :)

Earlier in this thread, many users mentioned that Bluetooth audio doesn't work. Since I often listen to music via BT stereo headphones, that would be really important for me. Sadly the OP doesn't mention BT anywhere, neither in the 'working' nor in the 'not working' section, so I had to ask.
[Motorola Droid 4] t--b:
Ah, I don't use bluetooth audio so cannot test that. File transfer worked fine.

Depending on the internet pages you want to visit it might be a frustratingly long wait. You could provide a webpage you want to visit regularly and I can check if it is a struggle to get it rendered.

The sites I am visiting are usually not very demanding.
[Motorola Droid 4] Shani Ace:
Tbh I don't really remember which sites I visited back then as it's too long ago. But even just opening the Browser (Opera) without having any open pages took ages or even freezed the whole phone (so I had to reboot) with CM12. That didn't happen with CM11 though.

If I remember correctly, it happened on the stock slot and the virtual slots alike.

Since someone wrote that the performance with LOS13/14 is almost as smooth as with CM11, I guess it'll be fine.
[Motorola Droid 4] t--b:
I am just using the stock browser. Google is up almost immediately and even something like youtube pops up almost instantly and plays video fine. BBC.com news is snappy as well.

btw - I did not install gapps.
[Motorola Droid 4] Shani Ace:
Well that sounds wonderful. Definitely better than it was in the past. :)
[Motorola Droid 4] t--b:
Just wondering - I have seen folks mentioning OTA updates for LineageOS. Is that supported in this build as well or do I need to install a new image every time a new build is released?
[Motorola Droid 4] t--b:
Nobody knows the answer to this question?

Anyway, gave the 'standard method' a try so with settings-about phone - LineageOS updates and tried manually to update and got 'the update check failed. Please check your internet connection and try again later'

Internet is working fine, so is the functionality disabled in this build?
[Motorola Droid 4] zys52712:
That feature won't work if it's unofficial Lineage OS.
[Motorola Droid 4] t--b:
OK thx - I am indeed using an unofficial version. It is not clear to me what is the difference between the two though. OP doesn't mention that.

It seems like the official version is an automatically nightly build (I assume the official version will be auto-updated OTA to the latest nightly).

In hindsight It probably would have been better to download the official version then, on the other hand.. the unofficial version I am running March 02 Maserati works very well.

Will give the official a try on another D4 first.
[Motorola Droid 4] Jwikoff99:
How does one root after installing this rom?
[Motorola Droid 4] t--b:
pretty easy

Steps you need to follow :

STEP 1:

Go to Settings. Click on About phone and then Tap Seven times on the Build number.

Here is a link explaining How to Enable Developer Options on Android or Lineage OS or any other Custom ROMs.
STEP 2:

Now to enable ROOT access, open Developer options and then scroll a little bit down on the Developer Options settings and look for the Root access setting, which must be showing Disabled.
Just click on the Root access and set it to Apps and ADB or Apps only or ADB only, as per your need.

see http://www.cyanogenmods.org/forums/topic/how-to-root-lineage-os-13-14-1-marshmallow-nougat-rom/
[Motorola Droid 4] Jwikoff99:
Well, I did that, and root checker and superSU still say it's not rooted. I enabled it for apps and adb.
[Motorola Droid 4] tobby88:
Theoretically: flash this after your ROM: https://mirrorbits.lineageos.org/su/13.0/addonsu-arm-signed.zip

In practice: That zip has in incompatible flasher-binary for our Droid 4.

You need to replace the META-INF\com\google\android\update-binary with the one from the lineage-rom-zip.

Or take this flashable zip where I already did it: addonsu-arm-maserati.zip (Droid 4, Lineage 13.0) (md5: cc57c5af9dc964634b01d56cf933bf9c) Don't enable to check the signature when flashing it, that will not work. But the signature/signature-check seems to be broken when flashing the rom-zip anyway.

This is correct for the "old" CyanogenMod ROMs. But not for Lineage. They don't include root/su.
[Motorola Droid 4] K_Meleon:
Have a look at Post #520
[Motorola Droid 4] t--b:
I've installed the unofficial version and I am pretty sure I used the 'old' method and it is working fine - so maybe the unofficial version has some additional features the official version does not provide?
[Motorola Droid 4] tobby88:
Yes, that's possible. Haven't really used the unofficial builds. But that's somehow why they are called "unofficial" - because you can do/change/include whatever you want with these before releasing them. :)
[Motorola Droid 4] tobby88:
Hmm, since two or three builds my bluetooth isn't working anymore. But I can't find anything related in the changelog. Wiped everything, reinstalled Lineage + OpenGApps and still the same. Blutooth is off and can't get activated.
[Motorola Droid 4] t--b:
Probably not helping but I can confirm bluetooth is working with the 2017-03-02 unofficial build (tested file transfer)
[Motorola Droid 4] tobby88:
Did another full wipe. Tried it again. Couldn't activate it. Rebooted again. Was able to activate it, but no devices were found. Another reboot, now it's working.

Crazy stuff. Two full wipes with clean flash, another two reboots - until its working again. Let's see how long :D
[Motorola Droid 4] belrei:
bluetooth

Can anybody confirm that bluetooth audio (e.g. for car hands free calling) is working? :confused:

I just bought a Droid 4 and I'm trying to check out which ROM to use

Many thanks!
[Motorola Droid 4] joefuf:
Any comments on how recent builds of the ROM have been? I'm still running a manual build from 3-25, and I haven't tried any of the builds once we moved to Official Lineage builds. I finally have enough time off work to flash a new build if recommended.

Am I correct in understanding the following as how I would go about upgrading?

* I would need to wipe data and cache because this is a different build from the manual builds

* I would need to first flash the Lineage Migration Signed zip linked here, and then I would flash a Lineage build, and then a Pico GApps zip. I would do it in that order and without rebooting.

* The official su-addon does not work, so I will need to flash the addonsu-arm.zip found here on Michael's site.

Missing anything else? Any caution I should observe in the process?

EDIT

I seem to be having an issue flashing this ROM. I pulled a backup phone out of retirement (one running a CM 13 build) to give the flashing process a try because I always seem to have issues somewhere along the lines, and this one happens to be no exception...

I downloaded the four files I mentioned above - the migration zip, a Lineage build from the official site, a Pico GApps, and the su-addon zip. I rebooted into TWRP, and I wiped data and cache. Then I flashed the migration ZIP. I get an error that says "Error: packages.xml not found. Exiting..." but it says Successful after it finishes flashing.

I next tried flashing the LineageOS build from the official site, and that gets a whole host of errors before I get a Failed message...

Any suggestions?

EDIT 2:

I ended up just starting from scratch and flashed stock Jellybean and then flashing the LineageOS ROM after rooting. Looks great.

The new nightly from today must have been pushed after I started the process though, and when I finally got everything up and running, I was prompted for the OTA update. I went and tried to do it, but after rebooting and when I hit Menu to go to Recovery, it was unable to find the update zip to flash. I tried bouncing around to a few folders (it looked like it was supposed to be in /data/data, but there was no second data folder when I went into /data) but I gave up and just did it manually. Does the OTA update work on this phone/recovery?
[Motorola Droid 4] OGdroidster:
What I did was skip all that and manually added the su files and binary into system where they belong. Then I wiped a full wipe then I flashed. If your using windows you might have to unzip to do that then rezip I'm not to sure. I know on the older versions you had to.
[Motorola Droid 4] joefuf:
Oh was that really all that is necessary? I could've just replaced a few system files manually? Maybe when I get another chance to do my daily driver I'll go that route.

The biggest pain for me is restoring my SMS messages. I probably have close to 90,000 to restore at this point. Last time, when I upgraded from CM 11 to LOS 13, it took almost 24 hours for the phone to restore everything. Wish I could just wrap it into the flash of the ROM process.

What's your overall experience been with the lastest builds? I see they managed to kick the reboot after hotspot bug.
[Motorola Droid 4] OGdroidster:
Why so many. You can try to make a flashble zip and see if that works.
[Motorola Droid 4] joefuf:
I've kept backups since like 2011. I just like having everything. Sometimes it's fun to jump back in time to a random day talking to someone and remember everything that was going on that day, even the little things.

I don't know why I never thought to try and make a flashable zip before just now. I see here someone said the sqlite database files are located at "/data/data/com.android.providers.telephony/databases/mmssms.db" so I am going to try and see if I can add that folder tree and file to the ROM. I'm grabbing a few other folders that look relevant, but if that works, that would be an AMAZING time saver for me. I always put off flashing ROM updates for months because I don't have the time commitment to let me phone sit on airplane mode for a full day while it restores.

If you have any other ideas of how I'd do this, let me know.
[Motorola Droid 4] schmatzler:
There is an app called "Super Backup SMS and Contacts" in the PlayStore. I find it very reliable, even for thousands of messages.
[Motorola Droid 4] OGdroidster:
SQL data base is located in data/data then scroll to folder that says MMS look for SQL database you'll need the app to open it or just pull data from it. You could just try an MMS app to back your MMS up to sd card then use same app to restore.
[Motorola Droid 4] joefuf:
Thanks for the tip. I did a backup of all 97,000 of my SMS messages, and it only came to 18mb, which is insane compared to SMS Backup & Restore, the app I've used since 2011. I have to imagine it doesn't do MMS, right?

I tried to move the backup XML to my backup phone (which is having issues of its own right now on the latest nightly) but Super Backup doesn't see the backup file to do a recovery. I even made a new directory and sent an SMS from that phone to make a backup locally to know there's a proper file for it to find, but it doesn't see anything.

I guess I'll keep working on it or just stick with SMS Backup & Restore. I imagine I will be able to flash over the ROMs now rather than having to do a complete wipe before flashing now that we're on Official Nightly releases. Before this with the whole nightly vs milestone release thing, I only ever put myself through the burden when I caught a nightly right after a milestone. Hopefully now I should be safe to go nightly to nightly from time to time.
[Motorola Droid 4] belrei:
I'm having similar problems :(

flashing linage-migration-signed.zip fails:

....

Verifying zip signature...

ERROR: package.xml not found. Exiting....

flashing the latest ROM fails:

...

Verifying zip signature...

E:Zip signature verification failed: 1

Error flashing zip ...

I also get E:Unable to mount '/osh' at the end

Any suggestions?

Many thanks in advance!

Regards R.

Problems solved:

migration.zip: forgot to mount /data

ROM: turned off zip signature verification
[Motorola Droid 4] schmatzler:
Make sure you keep the directory structure intact. It's a bit tricky sometimes. I had to use it on a Samsung phone last week and it would only see the xml files on EXTERNAL_SD/SmsContactsBackup/sms/FILENAME.xml.

Try putting the directory on the external SD or internal SD, one of them should work and the app should see the backup file.