yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] daniel_m:
[MENTION=3457922]stargo[/MENTION], do you know how and where CM13 mounts partitions? I would like to prevent mounting of the 2nd partition of my external SD-card (mmcblk0p2), and possibly the internal SD-card (mmcblk1p25). I would also make my external SD-card writeable to all apps.

My init.d script is a very dirty fix and does not seem to be very stable. The boot process takes ages and sometimes does not even complete. Android also complains about a corrupted SD-card.

With this script, I umount and rmdir mmcblk0p2 from /mnt/media_rw, /mnt/runtime/read, /mnt/runtime/write and /storage, and finally I umount /dev/block/vold/public:179_34. Then, I mount mmcblk0p2 to /data/sdext2.

This way, Link2SD recognises the 2nd partition and is able to link apps to it. Apps are persistent after a reboot and they function.

Preventing mmcblk1p25 from mounting is not my highest priority, but it might be nice to use the internal memory with Link2SD.

As I wrote before, Android does not handle using mmcblk1p25 as internal memory very well. In addition to problems with moving apps due to a shortage of temporary space, Android still mounts mmcblk1p25 as SD-card and apps happily use it to save their data onto mmcblk1p25. This makes things extremely messy and reduces storage space for .androidsecure.

I also tried to remove mmcblk1p25 mount points from the system with my init.d script, but that had an even more severe impact than just removing mmcblk0p2.

The other problem I mentioned before is write access to the external SD-card (mmcblk0p1). I formatted it with exfat, could this cause trouble? With FX Explorer (root), I can successfully write to mmcblk0p1. No other app (SSHelper, camera, ...) is able to write anything to mmcblk0p1. In /etc/permissions/platform.xml, WRITE_MEDIA_STORAGE is populated with 'media_rw' and 'sdcard_rw'. Are there other places to check for write access?

Edit: I finally managed to extract ramdisk.img. The first 144 bytes had to be stripped away, then I extracted the archive (gzip) and extracted the resulting cpio archive (cpio -i -F). There were errors during the cpio extraction on my Windows machine. I will try the extraction on a Linux machine soon.

Funny, after having figured out about the 144 bytes, I found an interesting thread on XDA :D

Time to take a closer look at init.rc ... find a way to re-pack everything into a boot image ... and brick my phone with it ...

Also: Sorry for spamming everyone with my soliloquy (what a peculiar word!), but the space problem on our Droid 4 is seriously bothering me.
[Motorola Droid 4] Shobai:
I've missed three calls in the last week or so - my phone plays my ringtone but the display stays dark until after the call gets pushed through to messagebank. The display then lights up, showing the incoming call for maybe a second but not responding to touch input, before seemingly catching up to real time once the missed call SMS notification arrives. This is pretty similar behaviour, if memory serves, to the issue we had under CM12 for a long while. I haven't missed all calls, maybe only half [I don't receive a lot of calls].

I'm currently on the 160214 nightly, with JJB's 160215 1.4GHz ULV kernel. I'm using Kernel Adiutor to use the ondemand governor and have set the Low Memory Killer for Very Aggressive.

Has anyone else had this happen?
[Motorola Droid 4] Careless_:
Must be on the nightlies after the Feb 01 one that I'm running right now. I find it to be quite responsive with joojoo's 1.4 ULV full scale kernel.

Try bumping your minimum clock speed or your minimum screen off clock speed up to see if any of the issues go away temporarily.
[Motorola Droid 4] daniel_m:
Michael, do you know why it won't boot? I finally figured out how to edit the CM13 ramdisk.img and also found out that changes to init.target.rc won't boot. Or were you referring to the Motorola ramdisk (stock-ramdisk)?

I think I will have to revert back to CM11 if I can't get Link2SD to work and resolve Android's greediness for SD-cards/partitions... :(
[Motorola Droid 4] joefuf:
I've been sticking with CM 11 on my daily driver too. For whatever reason, that seems to be the optimal performer I've gotten on my device, after all of the wakelock and Greenify efforts I've made. Not sure what else can be done to enhance this old dog.

I did notice an improvement when I located a brand new model on eBay about a year ago and flashed the ROM to it, but I imagine that only goes so far. I'll keep my eye out for another one to have just in case. Wish there was another Android QWERTY solution out there.
[Motorola Droid 4] stargo:
Hi,

posted this in the wrong thread previously:

just a quick question for people running CM nightlies without modifications: do you sometime get data-drops where the phone is using data and after a time it won't reconnect without toggling airplane-mode?

This seems to be caused by rild somehow exiting (not crashing), but it is very hard to track down (and I can't reproduce it).

Thanks,

Michael
[Motorola Droid 4] d.casper.b:
Previous replies on this page. Posts #83, #85 & #86.

[MENTION=3457922]stargo[/MENTION] , yes it does seem to do the trick (airplane mode). Sorry, could have been more clear there. I think once it initiates a new connection it works fine again.

It will show it is connected but nothing happens until you "reset" the connection.

WiFi at home is fine so I knew it was my data connection that was a problem. I kind of just accepted it. It doesn't happen all the time, but I notice that sometimes I'll be browsing and then I suddenly can't open a page or connect to play store or something.

I actually queried this with others some time ago but no one seemed to see the same behaviour as me.

{I've tracked down my old post: Here it is.}

Daniel
[Motorola Droid 4] aiamuzz:
Hi,

Just to know ...

[MENTION=3457922]stargo[/MENTION] ... is this thread ... so we discuss issues(of CM13 builds) between the community and casually share fixes between ourselves

or

serious bugs and issues are welcome and the same is updated/communicated to within the CM team(maintainer of our device) ?

while prompt nightly build updates OTA are great, without the changelog(of what's new/fixed) kind of in a dilemma of what would be a good way to decide if flashing to a newer available update makes sense or we can give it a pass.

with the app optimizations taking a lot of time after each OTA flash and a second app optimization's after flashing Xposed zip, seems all cumbersome to carry out the update as and when available.

thanks,
[Motorola Droid 4] d.casper.b:
Post anything related to CM13 here. Issues, help, bugs, tips etc.

BTW, you can flash xposed when you flash the update and then you don't have to sit through app optimisation twice.

Sent from my Motorola RAZR Maxx (XT910)
[Motorola Droid 4] Bobcus Leper:
[MENTION=3457922]stargo[/MENTION] is our official CM device maintainer. I only flash new builds either when a new revision of Android is there Android (6.0.1_rx), or if there are any OMAP-4 changes commited by stargo.
[Motorola Droid 4] daniel_m:
You can also use an addon.d script to automatically backup and restore files in /system and delete pre-installed apps from CM13.

And old version for CM11 can be found here: http://xdaforums.com/showpost.php?p=54875485&postcount=1298 (I did not make this script, I merely modified it).

For CM13, the script has to be changed and you have to modify it to your liking. In CM13, system apps are in their own subfolder. So instead of deleting the APKs (like in my script for CM11), you now have to delete the app folders.

You can even add the Xposed toggling script to addon.d.

Every time you update CM13, the scripts in /system/addon.d are executed. It takes some effort to get these scripts to do what you want, but then you can update CM13 daily without having to do any additional work :)
[Motorola Droid 4] aiamuzz:
Thanks daniel ... going the script way ... currently difficult ...

CM13 issues ... if not already reported ...

Play Store search crashing ... nightly 23 and 27 ... however can update already installed apps from within. And for new apps have been taking the browser way on laptop ... works.

Unable to install Super SU(some apps insist on it - I would love if I can make them accept the native su manager) ... normal method fails ... recovery method ends up in boot freeze ... backup restore is the way out.

Wifi drops intermittently usually I discover it after waking my device from sleep, toggling the switch no effect. A manual connection ... Tap - Connect ... it connects so quick that it seems it was already connected and the above tap just refeshed the screen.
[Motorola Droid 4] frankijdc:
ameisin yob
[Motorola Droid 4] simonsmh:
The battery mode change opinion is not found in the battery setting so I can't change it to battery saving mode easily. I think it is a bug, and maybe someone can fix it. Thanks!

从我的 XT894 上通过 XDA Forums 发送
[Motorola Droid 4] highlandsun:
I'd like to get hold of another one, the '/' key is dead on my current one. Btw, I've replaced the battery in my Droid 4, it's pretty simple. Full instructions that I followed are here https://www.ifixit.com/Guide/Motorola+Droid+4+Battery+Replacement/12311 Lots of folks sell batteries on eBay, with the necessary toolkit as well.

Actually, the HTC Touch-Pro2's keyboard is still nicer than this, but the Droid4 is pretty good. I wish someone would put out a new phone with top-end specs and the HTC keyboard.
[Motorola Droid 4] highlandsun:
If anyone is interested in using OpenCL on these phones, I recently got OpenCL 1.1 working on my B&N Nook HD+ with CM13. http://xdaforums.com/showpost.php?p=65573806&postcount=596

That uses an OMAP 4470 with SGX544, while these phones use OMAP 4430 and SGX540. I've gotten some small OpenCL programs working on my Droid4 now too but it still crashes more often than not. I can't get a successful run of OpenCL-X benchmark yet. If you like hacking on puzzles, mebbe you can help out.
[Motorola Droid 4] lucize:
for me update to latest opengapps fixed play store crash on search box

Regards
[Motorola Droid 4] Septfox:
Currently running 20160302 (upgraded from 0215 a couple nights back), phone's running better, no new issues. Wifi's back to idling properly, which is nice since waking my phone to find it disconnected was really driving me up the wall.

3d performance still seems lacking despite scoring well; is this a side-effect of the DSS changes made for LiveDisplay? If so, would it be possible to add a jump over the added code if LD is disabled?

Sorry for being a bit late to the party, but:

I don't usually have to toggle airplane mode, turning data on/off and restarting the app that's trying to use it almost always suffices.

I've never had it drop an active connection (phone on and pulling data) except when reception is patchy and it's forced to move back and forth between LTE and EvDO. It seems fairly prone to flaking out then, but it's not crippling.
[Motorola Droid 4] kzin42:
Did I miss someone mentioning that the BT audio skipping issue was fixed? just put on 20160304 and been listening to bug free audio in the car today.:D
[Motorola Droid 4] stargo:
Hi,

If LiveDisplay is disabled and no color calibration is configured, the kernel code will not get enabled.

But even if it gets enabled, LiveDisplay (and calibration) is without performance impact as it is done in hardware (way after the gpu 3d rendering). So LiveDisplay should really not be the cause for 3d performance problems.

Hmm, then that's not the rild-crash I'm chasing on the phone from [MENTION=1070688]joojoobee666[/MENTION].

If it was fixed then I'm not responsible for it ;) I assume it was a breakage in the core cm bt-stack.

Cheers,

Michael
[Motorola Droid 4] Bobcus Leper:
Hi,

[MENTION=3457922]stargo[/MENTION], do you know why ROMs that are based on CM13 do not have color calibration working? I recently flashed Mokee 6.0.1, and the live display/color calibration does not work.

Thanks again for all of your hard, and dedicated work!
[Motorola Droid 4] d.casper.b:
And on that note (above post), is there any way it can be implemented in 5.1 (I'm also on MoKee). Just wondering really, it's no biggie.

;)

Sent from my Motorola RAZR Maxx (XT910)
[Motorola Droid 4] stargo:
Hi,

For color-calibration/LiveDisplay these commits are needed:

http://review.cyanogenmod.org/#/c/128097/

http://review.cyanogenmod.org/#/c/128125/

http://review.cyanogenmod.org/#/c/128085/

http://review.cyanogenmod.org/#/c/128159/

http://review.cyanogenmod.org/#/c/128273/

There are a few later commits which just move stuff around. But ROMs using CM13 as base should have working color calibration already...

And for 5.1 these commits would be needed, I have not pushed the to the 12.1-tree.

Cheers,

Michael
[Motorola Droid 4] Shobai:
I'm still having trouble with missing calls =/ Missed another 2 today; from my boss, of all people.

I just updated to the latest nightly this morning, and after it finished booting up I rebooted to flash JJB's 160312 Run n Gun ULV. A few hours later I was reviewing emails in Gmail when I noticed the incoming call icon flash up on the notification bar momentarily, before changing to the missed call icon. I pulled the shade down and hit 'call back'. The phone then locked up. The next thing that appeared, a minute or so later, was the SMS notification of the missed call for the second call, along with another missed call icon. At this point normal function returned and I was able to make a call.

Any ideas? Am I doing something wrong?

[edit:]

In other news, I've also been missing notifications over the last 2 weeks or so. With Clock I've had some alarms just not sound, with Gmail I've gone most days without getting an email notification only to discover that when I manually check I've had a bunch come in over the course of the day, similarly with Google's Messenger. Will this be due to a config issue at my end? Would I be better off wiping and flashing the ROM clean?
[Motorola Droid 4] Shobai:
Is anyone else getting auto-rotate issues on the 160313 nightly? It seems to handle switching to landscape upon opening the keyboard, but rarely [if ever] switching back to portrait if the keyboard is closed. If I hit the home button after closing the keyboard, when the 'desktop' is displayed [what's it called on Android? I forget...] it will draw in portrait as expected.
[Motorola Droid 4] kzin42:
I have found that auto Rotate setting seems to do nothing, and apps stay in portrait after closing the keyboard that's on 160304. If you long press on the desktop and then swipe up there is a setting "allow rotation" when this is off, closing the key board always results in portrait.
[Motorola Droid 4] Bobcus Leper:
Hi,

I have a quick question. [MENTION=3457922]stargo[/MENTION], are you going to give us the go ahead for the first CM13.0 Snapshot?

Thanks!

Edit: Never mind, I saw this changelog. You are awesome [MENTION=3457922]stargo[/MENTION]!

Finally, this is the build roster for this evening:

acclaim

angler

bacon

bullhead

cancro

crackling

d800

d801

d802

d803

deb

find7

find7s

flo

flounder

g2m

ham

hammerhead

jag3gds

jagnm

kipper

kltechn

kltechnduo

klteduos

mako

manta

maserati

otus

r7plus

serrano3gxx

serranoltexx

shamu

sprout4

sprout8

spyder

targa

umts_spyder

w5

w7
[Motorola Droid 4] Septfox:
[MENTION=2284185]Shobai[/MENTION], [MENTION=4828860]kzin42[/MENTION]

Try flashing the nightly from yesterday, it appears to have a commit addressing auto rotation "randomly failing".

Guess something lately must've unexpectedly broke it, I'm using a nightly from around the beginning of the month and haven't had any issues. Maybe I've just been lucky.
[Motorola Droid 4] Shobai:
Cheers, I'll check it out
[Motorola Droid 4] stargo:
Hi,

Sorry to disappoint you, I'll just quote what I wrote in the Razr thread:

Cheers,

Michael
[Motorola Droid 4] stargo:
And another quote ;)

Cheers,

Michael
[Motorola Droid 4] aiamuzz:
[MENTION=3457922]stargo[/MENTION] ... It says we can't flash it over nightlies ... Any idea how we can flash it as advised and yet get back our current device state from nightlies onto the snapshot in one sweep ?
[Motorola Droid 4] Bobcus Leper:
It is not possible. You must fully wipe the device, and then install the snapshot. When I mean wipe, you need to wipe everything except the internal storages. If you don't want the hassle, stay on the release builds.
[Motorola Droid 4] aiamuzz:
Oh ... so have to come in clean ?

will not restoring the data partition from the nightly nandroid backup work ?

thanks.
[Motorola Droid 4] Bobcus Leper:
Restoring the only the data partition should work. I haven't tried it yet.
[Motorola Droid 4] Jishkah:
Damn, the urge to upgrade to today's Snapshot is too strong... my phone doesn't handle anything beyond Stock and CM11 too well, since the internal hardware is failing, but I may just need to do this. Drag my phone by the ear into the present day by force, if I need to.

Is this something that I can dirty flash over CyanogenMod 11 via the CyanogenMod Updater, or would I need to wipe everything beforehand? I'm fine with either or, since I have the weekend to focus on this, but I just wanna make sure.
[Motorola Droid 4] aiamuzz:
so anybody test driving the release build ?

what's going and what's not ... compared to the nightlies ... updates/feedback appreciated.

If its great, then time to hit the stock ROM slot with the release as a daily ROM ???

unless not advised by experts from here !!!

thanks
[Motorola Droid 4] Jishkah:
Absolutely a daily driver, for sure. I clean-installed it yesterday, after worrying about whether a dirty upgrade would work or not, and it's just about as stable as CyanogenMod 11 - just about as snappy, too. So far, I haven't encountered any bugs. The dreaded cannot-remember-WiFi-settings bug seems to be gone, and my phone hasn't reset itself from overuse at all, which is surprising. I don't know what kind of dark magic Stargo performed between CyanogenMod 12 and CyanogenMod 13 to make it as stable as it is now compared to how messy it was before, but it clearly worked.

I haven't tried formatting my SD card as expanded internal storage, however. I wasn't sure if that was something that'd work, and I'd rather play it safe than sorry. I just barely have a couple hundred megabytes of storage on my phone after installing all of my apps and games, and then moving the games over to the external storage portion of the internal storage on my phone (weird, I know), but it's enough. You can try to format the SD card as expanded storage, but I don't know what the current status of that is.

If you're going to upgrade, however, I'd definitely recommend a clean install. I have my System partition set to the maximum ~1000MB, my Data partition set to ~3,500MB, and my Cache partition set to the default 10MB. I honestly don't know if the phone's Stock ROM slot would have enough space, all things considered - especially the System partition - but you can try to install it on there, though I wouldn't recommend it. CyanogenMod 13 is installed, obviously, as is the Pico GApps package from Open GApps. I set the device up as a new device, rather than importing my settings over from CyanogenMod 11 or earlier.

In short? Give it a go. :) I think you'll like it. Just make sure to dive into the Settings menu and tweak things to your liking.

EDIT: Oh! The only thing that I'd recommend that you do before installing the ROM is to add "dalvik.vm.dex2oat-flags=--no-watch-dog" (sans quotes) to the bottom of the ROM's build.prop file. This'll disable the auto-timeout feature that kicks in when it takes too long or uses too many resources to recompile an app from Dalvik to ART format, which happens every time you install an app - which you NORMALLY don't want to do, but some apps just won't install at all on the phone without disabling the auto-timeout feature, such as Facebook. Just make sure that you put your phone down and let it do its thing without doing anything else while it's installing those apps, however - the auto-timeout feature is there for a reason; your phone could soft-reset in the middle of the installation, since the safeguards to prevent your phone from overexerting itself here are basically disabled.

If you don't use the official Facebook app, then there's probably no reason to add that string to your build.prop file, as it's the only app I've found that actually throws an error message at me and times out if I try to install it without said string. In fact, if you don't use the app, I'd recommend against adding the string to your build.prop file. Lord knows the auto-timeout feature is there for a reason.
[Motorola Droid 4] martin9959:
voip calling (again...)

Is anyone successfully using voip calling with CM13 on the droid 4? Besides the problem already reported with the proximity sensor (which can be worked around using the "Keep awake while on call" function of csipsimple), I have horrible audio stuttering in all voip apps that I have tried (csipsimple, stock sip and whatsapp calling). At least csipsimple and whatsapp calling were working fine on CM12.1, but ever since I upgraded to CM13, they have become totally unusable. During the call, logcat shows lots of messages like

03-19 20:40:21.749 E/AudioHardwareALSA( 190): PB UNDERRUN
03-19 20:40:21.929 D/AudioFlinger( 190): mixer(0xb4140000) throttle end: throttle time(88)

with all three apps I have tried, csipsimple gives additionally even more messages like

03-19 20:08:28.238 E/AudioHardwareALSA( 190): PB UNDERRUN
03-19 20:08:28.827 D/libpjsip( 7832): 20:08:28.827 ec0xa1a70b00 !Underflow, buf_cnt=128, will generate 1 frame
03-19 20:08:28.979 D/libpjsip( 7832): 20:08:28.979 Master/sound !Underflow, buf_cnt=281, will generate 1 frame
03-19 20:08:29.102 D/libpjsip( 7832): 20:08:29.102 Master/sound Underflow, buf_cnt=281, will generate 1 frame
03-19 20:08:29.268 D/libpjsip( 7832): 20:08:29.268 ec0xa1a70b00 !Underflow, buf_cnt=243, will generate 1 frame
03-19 20:08:29.419 D/libpjsip( 7832): 20:08:29.419 Master/sound !Underflow, buf_cnt=228, will generate 1 frame
03-19 20:08:29.730 D/libpjsip( 7832): 20:08:29.730 ec0xa1a70b00 !Underflow, buf_cnt=243, will generate 1 frame
03-19 20:08:29.750 E/AudioHardwareALSA( 190): PB UNDERRUN
03-19 20:08:29.751 D/libpjsip( 7832): 20:08:29.751 ec0xa1a70b00 Underflow, buf_cnt=243, will generate 1 frame
03-19 20:08:29.773 D/libpjsip( 7832): 20:08:29.773 ec0xa1a70b00 Underflow, buf_cnt=243, will generate 1 frame
03-19 20:08:29.794 D/libpjsip( 7832): 20:08:29.794 ec0xa1a70b00 Underflow, buf_cnt=243, will generate 1 frame
03-19 20:08:29.814 D/libpjsip( 7832): 20:08:29.814 ec0xa1a70b00 Underflow, buf_cnt=243, will generate 1 frame

Looks like some audio problem.... the only difference of the three apps that I can see is that while *outgoing* audio is more or less fine with whatsapp calling, it suffers the same stuttering with csipsimple and native sip audio. Any ideas? Or any hints which app might work better?

EDIT: Fixed as of Nightly of 10 April (by this fix)
[Motorola Droid 4] aiamuzz:
Really !!! ... Excited ...

Would appreciate if someone posted its performance on the stock slot ...

If its stable ... then high time the stock slot was graced with a befitting ROM !!!
[Motorola Droid 4] Puppymang:
are you using cm13 snapshot 1? i was about to switch to cm13 then i saw your post and if this is still an issiue i think ill continue holding off for a little while
[Motorola Droid 4] martin9959:
I've tried various nightlies, I'm now on 20160311, it was the same for all of them. I don't want to try snapshot 1 because the switch from the nightlies doesn't seem to be easy, but I would be very interested if you could try out and post your experience...
[Motorola Droid 4] ugynok:
Hi folkz! I'm on 20160317 NIGHTLY (but not snapshot), and it seems like fine. I can use GPS, can receive calls, battery is cold and has normal discharge rate.

I have the common wifi issue: I have to connect manually to SOME saved wifi networks, but most networks are connecting automatically. Mobile data networks are working.

I had this recent issue: Hangouts, I want to make a call, hangouts freezing, then I make that call again, then the phone is restarting... :( After that I cannot enable wifi networks.