yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] aiamuzz:
thanks Michael.

so the end is imminent it seems ... with Marshmallow turning out to be end of line for our Droid 4's !!!

:(
[Motorola Droid 4] tobby88:
It may be sad, but I am very happy this device was "supported" (offically and inoffically) for so long. It came to the market in 2012 with Gingerbread (Android 2.3) preinstalled. 6 years later and 7 major Android versions later I can't blame anyone nor anything. It will still work for maybe another year with updates for Nougat and in the meantime I hope, my Moto-Z-keyboard-mod will arrive :)
[Motorola Droid 4] own3mall:
There is no APN problem after all (because I did finally get 4G LTE to work), but does anyone else experience their 4G LTE connection not connecting / kicking in when it should?

If I walk away out of range from my WIFI, my Droid 4 never switches to a 4G LTE connection unless I reboot my device completely. The network icon shows that it has connectivity to the cell towers (and phone calls / texts work), but the 4G LTE network icon doesn't show until I reboot. Is something misconfigured? I do run a firewall (AFWall), but I white-listed the apps they recommended, and again, 4G LTE connections do work... but only after a reboot... and once the phone is connected to WIFI again, when I leave the range of my WIFI, it never switches back over to 4G LTE. :(
[Motorola Droid 4] own3mall:
I fixed it by going to "Settings" --> "Apps" --> "Android Keyboard (AOSP)" --> "Disable" and "Force Stop". I then installed Google's Gboard as a replacement from the Play Store and no longer have this issue when using my physical phone keyboard. Looks like a bug in AOSP. I might report it.

Edit: Hacker's Keyboard also fixes this problem and is much more efficient than Gboard.
[Motorola Droid 4] own3mall:
Any way to apply this patch somehow to this version of LineageOS?

https://jira.lineageos.org/browse/BUGBASH-72
[Motorola Droid 4] q765913:
BT Audio

To get BT audio to work on this ROM you need to change a2dp sampling rate from 44100 to 48000.

In the file /etc/audio_policy.conf look for the following (should be in 2 places)

a2dp {
outputs {
primary {
sampling_rates 44100

and change the 44100 to 48000. After that - reboot.

Source: (can't post the link) megi's PinePhone Development Log #020
[Motorola Droid 4] TweeterBox:
will this install onto an Android 6 TV box?
[Motorola Droid 4] hannor:
NO.
[Motorola Droid 4] TweeterBox:
so im stuck with all the google nonsense?
[Motorola Droid 4] hannor:
Not necessarily. Even if the Android on your TV box is not rooted, you can disable services (even Google services) in the Settings.
[Motorola Droid 4] TweeterBox:
this is very limited though

is there a guide to root box with android 6 ?
[Motorola Droid 4] hannor:
What is the type of your box?
[Motorola Droid 4] TweeterBox:
https://www.desertcart.co.uk/products/33706168-rbsch-m-96-x-android-6-0-4-k-tv-box-amlogic-s-905-x-kodi-16-1-fully-loaded-xbmc-quad-core-a-53-2-0-g-hz-64-bit-2-gb-8-gb-wifi-lan-vp-9-1080-p-google-mini-streaming-media-player-ott-tv-box

sorry just updated post with correct box
[Motorola Droid 4] hannor:
Well, let me repeat that the safest approach is simply disable the Google services selected by you in the Settings. If this is not enough for you, and you really WANT ROOT, then proceed at your own risk. I do not take any responsibilites, but there is a solution.

If you understand & accept the above, then rooting your tv box is possible after installing KingRoot from here: https://kingrootapp.net/
[Motorola Droid 4] TweeterBox:
thanks will give it a go :)
[Motorola Droid 4] stargo:
Hi,

Looking at the code it seems it always wants to actually partition the device (because it needs two partitions) which would corrupt the internal MMC, so I don't think this is going to work :(

I'm also not sure if I can at least add additional partitions as internal "portable" storage, as only one would get the flags needed to be seen by Android (that's exactly the flag that was missing in the 12-24 build).

Apart from that, adopting doesn't work on the devices at all currently :(

I've spent the day searching for patches from the stable linux-tree and the omapzoom kernel to at least stop it from crashing when trying to get adoptable storage up and running, but now it fails at fsck (after successfully partitioning, encrypting and formatting). I can manually mount the crypto container without a problem, so this should be solvable.

On the bright side this might have improved SD performance and fixed an SD deadlock or two.

I was also shown another bug on the 32C3: Camera currently crops images but the preview shows the full frame.

I'll make a new build if any of the bugs is fixed.

Cheers,

Michael
[Motorola Droid 4] LuH:
Thanks, but that doesn't solve my problem: enlarging /data while in system slot. I have enough free space in Internal storage (/sdcard), but not in /data. But maybe using another slot would be better? Do we know what's the performance loss caused by using other slots (so the /system and /data are not regular partitions, but emulated from SS's disk image files in Internal storage, which I guess generates some overhead)?

Well, I posted earlier that I went on with same data without a hitch, but actually I'm considering clean reinstall now. Some apps disappeared during the upgrade, including Mapy.cz and Google Maps (I think it applied to apps I had moved to SD in CM12.1) and it took serious effort to get Google Maps to work at all, including several data wipes and uninstalls and re-installs to get it started (would always crash on initial splash screen)... Weird thing is that the Street View app worked fine the whole time.

Good point, didn't realize that when going through the process theoretically... :(

Is that why also no mounting happens when connecting a USB Mass Storage device, even though it's fully operable?

Good thing to have better SD performance :) I'm afraid adopting won't be such a great thing after all though, considering it needs to be encrypted to work... AFAIK most of the performance problems we have now are due to CPU overload, which I'm afraid having half of apps' data on encrypted partition would intensify.

I can confirm that - when browsing my New Year fireworks pictures, I found out landscape is taken fine (3264x2448), but portrait is cropped to square (2448x2448). See attached fireworks in Prague :) (It's actually taken after midnight, Dropbox renames pictures on upload using UTC time, and I'm in UTC+1 time zone. Looking at the pictures, I guess I'm not on a career path of becoming a professional photographer... But it's even worse quality than it should thanks to layer of tape running over the camera lens, holding my new digitizer in place until I find some time to properly install it.):laugh:
[Motorola Droid 4] Careless_:
I see the discussion about the SDswap in the kernel thread going on here, but has anyone tried to use the Internal SD Storage feature on marshmallow to allow data to be stored there using a per-device formatted card?

I'm wondering if the sdcard will still be usable if I format and leave it in the same device, or will the device be locked out or encrypted so that it's not usable incase the phone needs to be emergency re-flashed.
[Motorola Droid 4] Bobcus Leper:
New build for Maserati!:good:

Also, new OC kernels.:good:
[Motorola Droid 4] 71evin:
I'm trying CM13 on droid 4 from few days and I think it is good.

For now I find one problem - when trying to download through stock browser, it crash (unfortunately, browser has stoped).

I try and last update 04.01. - the welcome logo miss me :( , and noticed that at previous bild 25.12. when have more than 3 app in backround, the # symbol appear at top.

Can someone tell me where is history in stock calc :))
[Motorola Droid 4] stargo:
This is the new permission-system in M, you have to grant Browser access to storage (in settings->apps->browser->permissions).

I've put the christmas bootanimation at: http://droid.cs.fau.de/cm-13.0/ (the 12-25 build contained the jpeg-version)

# means that you have an app running which uses root. It has nothing to do with the number of the apps, but I agree that the icon is confusing.

Cheers,

Michael
[Motorola Droid 4] schnick_schnack:
SELINUX (strict) prevents access to external "sdcard1" if partition is not vfat/fat32

I am using the build of 2016-01-04 and I can mount ext4 partitions but I cannot access ext4 partitions due to SELinux restrictions. I can only access my external ext4 formatted micro-SD-card when I switch SELinux (strict) to SELinux (moderate) by running "setenforce 0" in terminal. You could read more details in my the "Bug Reports" tap.

http://xdaforums.com/devdb/project/?id=12959#bugReporter

Can you really access your "ext4"-partitions in SELinux (strict)-mode?
[Motorola Droid 4] LuH:
That's the "adopting storage" feature we talked in previous posts. Stargo mentioned it working from Jan 04 build.

It unfortunately does encrypt the storage, which not only locks you out in case of system failure, but also negatively affects the IO performance.

If you back up the encryption key (from /data/misc/vold/) elsewhere though, it can be accessed from any Linux machine - see this post: http://nelenkov.blogspot.cz/2015/06/decrypting-android-m-adopted-storage.html
[Motorola Droid 4] Careless_:
honestly sounds like more work than it's worth to recover the data, and I don't like having to do that with testing various ROMS and whatnot.

thanks for clearing that up. maybe in the future i'll give it a go.
[Motorola Droid 4] 71evin:
Thank you stargo.

Everything is just you said, and the phone works great. I'm using it in Europe with 3G, and there was no need to install gsm patch like on android 5.1. Custom keybord that I use also work and new alt-key function is awesome. Only Sygic doesn't work, but it looks that the software is not compatible to android 6.

Best Regards.
[Motorola Droid 4] KusioST:
Hello

System crash after install gapps. I installed piccolo version on cm-13.0-20160106-UNOFFICIAL-maserati.zip.

Regards

Kusio
[Motorola Droid 4] 71evin:
I'm using pico version too - open_gapps-arm-6.0-pico-20151225, but on 04.01. bild and it works fine.
[Motorola Droid 4] KusioST:
CM13 works (even SMS works and this is huge succes - on older CM I could not send SMS :/), but after install open_gapps-arm-6.0-pico-20160106.zip system configuration crushed. I get communicate like configuration have arror and will stop. Any advice?
[Motorola Droid 4] stargo:
You can't officially install Gapps after the ROM has been booted for the first time without a data-wipe, because Gapps will not get their necessary permissions and crash. Try removing /data/system/users/0/runtime-permissions.xml (probably from recovery) and reboot.
[Motorola Droid 4] moodroid:
Wow - this is the best my D4 has performed in ages - thanks, Michael and CM Team.

And I've just realised we can now toggle wifi without needing a reboot - just in case it's any use to anyone.

Has anyone manged to get this working in the safe slot yet?
[Motorola Droid 4] KusioST:
I tried do it in two ways:

1. Runn Safestrap, wipe partition, instal new ROM, reboot, run Safestrap, install Gapps, reboot.

2. Runn Safestrap, wipe partition, instal new ROM, install Gapps, reboot.

Both methods fail.
[Motorola Droid 4] JLPDA:
Did you do an upgrade (dirty flash) from 12.1 or did you do a clean install?
[Motorola Droid 4] moodroid:
Clean install.

Does the dirty flash work, and if so, do I need to wipe anything before installing?
[Motorola Droid 4] mifritscher:
in /etc/fstab:

/dev/block/system /system ext3 rw,noatime,nodiratime,errors=continue,barrier=1 wait

Why is the ext3 driver used there? The ext4 can handle ext2/3 file systems as well - and with many advantages (better allocation strategie etc.) And it blocks converting it to ext4... Even if this is not possible for /system, it should be for /cache and /userdata I think.
[Motorola Droid 4] stargo:
Hi,

There are a few reasons:

Formatting cache or userdata (on stock slot) as anything else than ext3 will cause a soft-brick, as the motorola initrd will fail and the system will not get to the point were safestrap takes over.

The ext4-driver is currently at the version which was in 3.0.101 and I'm not convinced that its backwards-compatibility is completely stable. I just recently pushed a few corruption/deadlock fixes to it, which prevented adoptable-storage from working. Ext3 on the other hand was heavily in use when this kernel-version was current, so I'd rather rely on it for userdata.

When not using ext4 on userdata stock-slot (which doesn't work) then it's being used on a loopback mounted filesystem which is stored on vfat, so stuff like discards aren't working because of the underlying storage configuration. I'm not sure if ext4 would provide much benefit in this case. (fallocate is the only case I can think of which would provide a bit performance increase, but it's only used during install of software from the play store)

But feel free to experiment with ext4 :)

You might be able to convince me to change to it ;)

Cheers,

Michael
[Motorola Droid 4] mifritscher:
Hi,

the first and probably biggest problem is that I gave my Droid 4 to my girlfriend (having a Photon Q now)

I shuttered the glass with a fall of 1 meter on a rather soft PVC surface and bought both a new glass and a Photon Q, because I gave myself of 50% for a successful replace, but it worked well :)

Perhaps I can give it a try on slot 2 ;)

But, if I'm remembering correctly, I've already reformatted the partitions in Safe Slot 1 to ext4 because I had to touch them anyway because of too little space.

I'm quite surprised about the ext4 problems in the 3.0 kernel, to be honest. Ext4 was called "stable" in 2.6.28, and 2.6.32 was a quite widespread used kernel (both a Debian version and Ubuntu 10.04 LTS used it, besides being a LTS-kernel itself) And it was used also used to drive many ext3 partition since the beginnings.

The biggest advantages of ext4, which are working also with ext3 filesystems, are the far better allocation (delayed and better strategy) and the better/faster journalling.

One not backward compatible change of ext4 was the extends, which helps reducing the overhead.

Hmm, *wondering*... Yes, now I'm getting very, very offtopic :D

Could the built-in sdcard-partition be formatted as LVM (or a new partition being made)? I assume that would be more performant than the loopback+FAT approach, and allows using partitions bigger than 4 GB. Using LVM-snapshots for experiments etc. whould be very, very nice as well :)

And, while we are at it, we could lay a cryptdevice under LVM, which would be opened by safestrap. Yes, the handover of the password from safestrap to the new kernel (to avoid having to type in a second time) would be a problem, but solveable I think ;)

Best regards,

Michael
[Motorola Droid 4] stargo:
Hi,

Some of these problems might be arm-related. I had reproducible deadlocks and Oopses as well as data corruption. These were gone when updating ext4 to 3.0.101 from 3.0.8.

But do we want to sacrifice stability for it?

I've built an image using ext4 for the ext3 partitions now and will try that for a few days:

http://droid.cs.fau.de/cm-13.0/test/.ext4/

Currently I'm not sure if it's faster, it even seems to me that it takes longer to wake up now.

No, changing this from vfat to anything else will lead to the stock-ramdisk to not boot.

Cheers,

Michael
[Motorola Droid 4] mifritscher:
Hi,

yes, more testing (and benchmarking) for ext4 would be nice. Perhaps some sort of stress test would be useful, too? This could be done in a qemu-vm as well I guess?

About the vfat-thing: another hack would be to leave the partition table as it, but shrink the vfat-filesystem to a few hundred MB, using the rest for lvm or whatever we would like to have (luckily device mapper supports the offset-option :) )

This way, the stock rom sees a normal (but smaller) vfat file system, but we have also a fairly raw access to the rest of the partition.

Another way to archive this would a tool which try to create a continuous big file on vfat, which start-position and length is in turn given to the device mapper.

best regards,

Michael
[Motorola Droid 4] Shobai:
[MENTION=3457922]stargo[/MENTION],

It seems that the move to toybox has gone poorly for Kernel Adiutor - whenever I load it, it tells me there's no busybox and asks me to download a busybox app from the Play Store. My guess is that this is probably because the KA bloke specifically looks for "busybox", rather than the specific functions needed. I've emailed him about it, but just wanted to check with you to see whether there might be a particular busybox part that toybox doesn't provide that might be causing the problem. What do you reckon?

Thanks again for your work on the Moto devices, I really appreciate it!

[edit: heard back from the developer]

Oh, bother. Does this mean I'll need to install busybox anyway?
[Motorola Droid 4] stargo:
Get /system/xbin/busybox from a previous build and put it in the current one. This is all that is needed.

Maybe someone can make a flashable zip for that.

Cheers,

Michael
[Motorola Droid 4] stargo:
Hi,

I'm back to ext3 now, ext4 was just too bad. Felt worse than cm12.1...

Cheers,

Michael
[Motorola Droid 4] Bobcus Leper:
Hi,

Here is a flashable zip that I made that enables busybox on the 01/08/2016 build, and also future builds that include toybox. I tested it with kernel auditor, and it works perfectly.

https://mega.nz/#!cQkR3bJI!DCguG4jW_ZUGJ5Tz6OBwpLl0rMqiMPOIBAp1TlNUoOQ
[Motorola Droid 4] KusioST:
I tried do it in two ways:

1. Runn Safestrap, wipe partition, instal new ROM, reboot, run Safestrap, install Gapps, reboot.

2. Runn Safestrap, wipe partition, instal new ROM, install Gapps, reboot.

Both methods fail.

So I neet to install ROM, then install gapps, delete file in path: "/data/system/users/0/runtime-permissions.xml " and then make firs reboot?

Sorry for double post but menu with quote buton and other things don't apear in my browser.
[Motorola Droid 4] LuH:
Over the weekend, I clean-installed the 2016-01-08 build (with Open GApps Pico and JJB's OC 1.4G ULV kernel - same setup as before with old data from 12.1), restored most of my apps with data using Titanium and found several problems:

Mobile data don't seem to work anymore (GSM - T-Mobile CZ)

Every reboot, the phone fails to recognize the SIM. I need to put it to airplane mode and either toggle it back off airplane, if possible from the Power menu, or reboot while in airplane mode to have the phone detect SIM.

Trebuchet got locked in some state and won't remember any added desktop icons on reboot. This used to happen to me before on CM12, but usually due to lacking space in /data - now there's 1 GB free - and after longer time using the rom, not a day after a clean install.

The namedays (Svátky) widget showing today's and tomorrow's name I used to use in 1x1 setting (whixh is the only one this app should provide AFAIK) now only works in 4x4. Maybe this is related to Android version (previously worked in dirty-upgraded data) or DPI (used to use lower density, I think 220 dpi, now trying default setting), app itself hasn't been updated since 2011.

I'm most bothered by the data not working now, as I didn't find a workaround yet. Logcat saved shortly after reboot after trying to connect: View attachment logcat-mob-data.log As you can see in the attached screenshots, the phone is given an IP address, but that's all. I can ping both IPs and domains (DNS is resolving, or cached; ping avg ~300 ms on Edge), but apps don't connect. Tried Browser - "net::ERR_TIMED_OUT" when connecting to google.com and XDA Labs just say "No items to show." after trying to connect for some time (XDA should be in logcat). APNs are fine. Everything works when on Wi-Fi, I didn't restrict background processes or any essential services. No toying with mobile network settings whatsoever.

With SIM I also have no idea what's the problem. Second logcat View attachment logcat-airplane-toggle-worked.log shows a situation where, after rebooting to the No SIM state, I managed to switch airplane mode on and then off, resulting in SIM being recognized. It happen when airplane on finished I think and asked me for PIN, then cell connection worked right away when I switched airplane mode off.

Additional modifications I have done to the system (same as before on fully working installation of 01-04 build with old data): replaced hosts file to block ads by this: View attachment hosts.zip, auto-installed busybox by BusyBox Pro and mc by Nativnux Installer (requires busybox's awk to install). Maybe there is some conflict between busybox and toolbox?
[Motorola Droid 4] LuH:
If you don't need to retain your data, I'd suggest:

Wipe system, data, cache, and dalvik-cache

Flash CM and GApps

Reboot :)
[Motorola Droid 4] Cain77:
Hi (nebo spis cau), for me is last build works perfectly fine (no mobile data problems - Im on tmobile gsm too, sim is ok, desktop icons working fine, I don't have svatky widget so I can't confirm that problem )

If I remember correctly I had problems with mobile data after first install, but issue got resolved by changing APN (T-Mobile Internet -> T-Mobile CZ), maybe try restore default apn settings.

If nothing works you could give a try to never build (there are daily changes in cm repo, if you don't want to build it yourself you can download one current rom I builded for myself: http://krilip.cf/download/ )
[Motorola Droid 4] stargo:
Hi,

I think I know what's going on here and should have a new build up later today.

This only happens on "new" installs.

EDIT: build is up, I hope this fixes it.

EDIT2: If you see radio-problems, please provide a logcat of the radio buffer (logcat -v time -b radio), the relevant info is not in the main log.

EDIT3: Could reproduce the missing SIM with the newest build once (in about 20 reboots), maybe I'm just not kicking the modem hard enough when switching from CDMA to GSM...

Cheers,

Michael
[Motorola Droid 4] Shobai:
Kernel Adiutor got an update yesterday, adding support for toybox - I haven't checked yet, but I wonder whether Bobcus' zip is necessary any more? [edit: updated KA, wiped /system, flashed the 160111 [+GAPPS, +jjb's kernel, but not Bobcus' zip] - KA works upon reboot]

[MENTION=3457922]stargo[/MENTION], thanks for fixing the mouse pointer! I tried my lapdock over the weekend and noticed it wasn't working properly, but forgot to mention it - thanks for fixing it in spite me forgetting! =P
[Motorola Droid 4] Bobcus Leper:
My zip is no longer necessary for kernel auditor, but it is still necessary for apps that haven't been updated for toybox.
[Motorola Droid 4] KusioST:
I want to thank you for help. Before this day I made basic wipe from Safestrap: "Wipe data cache, and dalvik-cache". This time I made "Advanced Wipe" and check all 4 option that You told me about (system, data, cache, and dalvik-cache). After this I installed new ROM and Gapps. The was some problem with boot because now I have some crazy start screen animation, but except this problem everything works perfectly. Even GSM have better signal :]
[Motorola Droid 4] stargo:
Hi,

[MENTION=566662]LuH[/MENTION] and other GSM-users, I've just uploaded a new test-build 20160111-2 just for maserati which seems to fix all radio-problems on GSM for me and doesn't break LTE/CDMA.

A yeti trying to eat the Moto logo is not crazy!

EDIT: Deleted the maserati-only build, changes are included in 20160113

Cheers,

Michael