yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] LuH:
I already *****ed about it few pages ago, where I tried USB peripherals :)

Cus :) I don't care about the widget anymore, found a different app that works fine. Unfortunately, the GSM problem still stands for me. It's probably due to clean-install on 160108 build. Thanks for the tip on building custom build, unfortunately it's a bit off my reach now – I'm basically a Linux noob, working mainly on Windows, and don't have the spare time and hardware needed to learn the necessary stuff (such as git) and get it working.

I didn't try APN yet, but don't think it will help - ping works (so I'm connected to Internet, at least from Terminal's standpoint) but apps don't load anything.

Unfortunately not working for me. I updated system first → SIM not recognized (several reboots, same behavior). Then wiped system, installed only this update (20160111-2), open_gapps-arm-6.0-pico-20160109.zip and cm-13-OC-14-ULV-2016-01-03.zip, with no further changes (no busybox nor other messing with system files) - still the same behavior: SIM not detected until restarted in airplane mode (usually don't even fully switch to Airplane before I restart it - option to turn Airplane off in the Power menu stays grayed out) and mobile data connected (ping from terminal fine, with DNS resolve successful) but no Internet access for any apps and an exclamation mark on the signal icon. Radio logcat when rebooted to No SIM: View attachment logcat-no-sim-radio.log and after pinging through mobile data (Wi-Fi off) fine with no access to Internet from the browser: View attachment logcat-no-data-radio.log

Glad I helped :)

I love these bootanimations :) BTW this bigfoot comic was the first thing on my mind when I saw it :D

Also a weird thing happened before I flashed it: I stayed late so Titanium Backup's weekly scheduled backup didn't fire automatically as the phone wasn't in the charger. When I ran it manually, phone soft-rebooted and didn't mount the external SD (dialog for newly found SD card appeared in notifications), prompting me to format it when I chose to use it as portable storage. That has quite scared me, but fortunately after a regular reboot it mounted fine (I cancelled the format ofc).

EDIT: new radio problem weirdness :confused:

As I went to try switching APNs, I noticed that in Cellular networks settings it said I had selected LTE as preferred , even though when I opened the option, selected option was Global. I switched it to LTE, which killed the network, and then it didn't allow me to switch to anything else, always reverting back to LTE about 0.5 s after changing. After first reboot, the screen was really interesting (see the first two screenshots; SIM not found as usual). Second reboot in Airplane got it working, and before switching Airplane off, I was able to switch to Global (with menu item still showing LTE as selected mode, but in the selector Global persists - other two screenshots) and cellular network works again, still without data unfortunately (last three screens).
[Motorola Droid 4] stargo:
Hi,

Just a quick reply for now: When the SIM is detected (after airplane mode), can you please try manually selecting a network mode in settings -> cellular networks? Something like GSM/UMTS preferred.

Cheers,

Michael
[Motorola Droid 4] LuH:
See edit at my previous post, I had the same idea :D

Also I switched APN from "T-Mobile Internet" to "T-Mobile CZ" as [MENTION=4842830]Cain77[/MENTION] suggested and the cellular internet connection works fine now. (Díky!) Comparing the two, proxy settings for MMS in the working profile are in Internet access in the not working one (the other proxy and port is always Not set), plus other differences. See screenshots. Maybe it'd be a good idea to remove the bad profile? Is this from the CM repo?

It's weird Internet worked from the terminal, probably ignored the proxy settings?

EDIT - got SIM to work by changing bands:

I switched the network mode to "GSM/WCDMA auto" that shows up as "GSM / WCDMA" before menu and so far so good, two test reboots and SIM found both times. Maybe it's some LTE-related problem? Anyways, workaround found :)
[Motorola Droid 4] stargo:
Hi,

I've uploaded a new (maserati-only) test-build which should fix the impossibility to switch back from LTE (you can only successfully switch to GSM/WCDMA modes, because that's all the phone supports with a GSM SIM) and has all additional things I can think of to force the phone to switch to GSM and stay on GSM (if a GSM-only SIM is inserted): http://review.cyanogenmod.org/#/c/127908

Yes, it's from CM, I'll try to get that fixed.

EDIT: Re-uploaded the image with a fixed APN configuration. [MENTION=566662]LuH[/MENTION], can you please test and reset APNs to default (three dots menu in access point names) and see if it still works?

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

Cheers,

Michael
[Motorola Droid 4] LuH:
Yes, works fine - the bad profile is gone and the good one still connects me :) Thanks!
[Motorola Droid 4] jaqjacek:
Hi, with cm13 i have problem with my xiaomi bt headphones. Problem is that after peer and playing something there are sound for 2 seconds, 4 seconds silence and another 2 second of sound. On cm12.1 all is ok. I've check original and OC kernel. Can it by that's because cm13 is on slot 1 ?

My bt headphones don't play good with any rom in slot1. Time to put cm13 on stock slot
[Motorola Droid 4] stargo:
Hi,

Starting tomorrow, the official nightlies will be CM13: http://review.cyanogenmod.org/#/c/129192/

Cheers,

Michael
[Motorola Droid 4] Bobcus Leper:
The maserati nightly is out! Thanks [MENTION=3457922]stargo[/MENTION] for your outstanding dedication to our devices!:good::svetius:
[Motorola Droid 4] Jishkah:
Just curious, but do we still need to add the watchdog line to our build.prop file to be able to install the Facebook app? Or does installing the app not time out, anymore?

I'll probably be installing the Nightly later tonight. Thanks a ton, Stargo, for the work that you've put into keeping our phones kicking for that much longer.
[Motorola Droid 4] daniel_m:
Are you guys running the XPosed framework and XPrivacy on Android 6? I'd like to switch from CM11.2 to CM13, but only if XPrivacy is working.

When I have some spare time in a few weeks, I will try it myself. But if anyone here has XPrivacy already working on CM13, I would appreciate some feedback and I would have a strong incentive to "mess up" my Droid 4 a little sooner :D
[Motorola Droid 4] Cyber-Logic:
[MENTION=3457922]stargo[/MENTION] Is it possible to upgrade from cm-12.1-20160120-NIGHTLY to cm-13.0-20160121-NIGHTLY while keeping existing apps and data? Should Gapps be flashed right after installing the CM13 zip file?

(Also, I'm choosing to flash Pico instead of Nano because I get an "insufficient space in /system" error).
[Motorola Droid 4] Septfox:
Xposed works fine, though it may or may not slow the phone down somewhat. I didn't run MM for very long before installing it, so I can't say for sure. Some popular modules, like Gravitybox, are also up to date with MM support.

Xprivacy hasn't been brought to Marshmallow yet, unfortunately. Privacy Guard and MM app permissions are the best we've got.

[MENTION=3457922]stargo[/MENTION] If you find the time, could you have a look at the compass functionality, please? It worked in CM11, but was broken in CM12 and remains that way; instead of indicating the phone's orientation relative to magnetic north, it instead "points" NW and changes based on how much the phone is tilted vertically. At a guess, it seems like it's taking some of the accelerometer's output and trying to use that. The behavior is identical between the quicksettings compass and third-party apps.

Also, the Wifi picker via the quicksettings panel is acting weird.

Using the inline/dropdown list to connect to an already-configured AP pulls you into the Wifi Settings screen and prompts for a password. If you're not already connected to a network, the phone will happily auto-connect to the network that it's prompting for in the background, while the password prompt is still in the foreground; otherwise you have to cancel out of the prompt and manually select the desired network again to connect. I can't remember for sure, but I don't think this was a problem in CM12.
[Motorola Droid 4] stargo:
Hi,

Yes, that should work. Just do not reboot between installing the ROM and Gapps.

Yes, I know (but always try to forget it). This is because the binary blob from Motorola no longer works and the phone is now using an open source implementation for accelerometer, orientation and compass.

I've tried for a few hours to fix the compass, but couldn't get it to work.

According to the kernel-source, this should be correct, but it obviously isn't:

https://github.com/CyanogenMod/andr...map4-common/blob/cm-13.0/ak8975fs/main.c#L207

Kernel side:

https://github.com/CyanogenMod/andr...mmon/blob/cm-13.0/drivers/misc/akm8975.c#L348

I have no idea, why it doesn't work :(

EDIT: As I now also have a targa which uses the same opensource-driver I know why it doesn't work: The open source version doesn't know about the magnet in the D4 which is used to detect an opened keyboard.

Yes, known problem in CM base.

Cheers,

Michael
[Motorola Droid 4] Septfox:
Unfortunately this is all a bit Greek to me...but it's what's supposed to be initializing and splitting/"translating" the various sensor outputs to integers in a format for applications to use, right? Sort of a frontend for the AKM8975 to make it effectively three sensors instead of just one.

Using a sensor test app, it can be seen that the magnetic "sensor" is active and spewing out information, and apparently indicating magnetic orientation (N/S/E/W have distinct, reproducible combinations of values). So the problem is that somehow that information isn't being pulled by actual compass applications, despite the above linked source being apparently correct? Or are the reported values getting overwritten on the way to them somehow with the information from other sensors?

Assuming for a moment that the compass is for some reason getting information from the accelerometer or orientation "sensors", instead of magnetic as it should be: what happens if you remove those from the source, and only have it bring it up as a magnetic sensor? Does it start working properly?

I really have no idea here, just stabbing blindly at it a bit. Sorry for my ignorance : \

Edit: disregard, I guess, as I didn't see your edit until after the fact.
[Motorola Droid 4] Jishkah:
So far, so good. The phone is running pretty well. The only issue that I've found that I think is Droid 4-specific is that WiFi is disabled after rebooting (well, a soft reboot - I had to perform a soft reboot after tweaking the DPI settings), though I'm going to assume that that's something that'll be fixed by a Dalvik/Cache wipe. I'll do that after I have everything up-and-running, I think.

Otherwise, the only other quirks that I've found seem to be with CyanogenMod, itself, and not specific to the phone. And it's nothing phone-breaking, either.

Exploring the Settings menu is... interesting, to say the least. A lot has changed between CyanogenMod 12.1 and CyanogenMod 13, for sure; things are in different locations, and you can definitely tell that a lot of it is still a sort of work-in-progress. Some newer settings are added, but still disabled; you can't toggle them on or off. I haven't really found much functionality missing between CM12.1 and 13, in terms of the Settings menu, which is pretty rad. I do like that LiveDisplay is finally functional, though I haven't gotten a chance to test it out throughout the day. Only just installed the ROM, really. I found a setting in the Developer Options menu that allows you to keep data enabled alongside WiFi for faster hand-off, which I think would work really well with our phones, considering how system-intensive WiFi-to-Data (or vice-versa) hand-off can sometimes be.

All-in-all, it seems to be working rather well. More-or-less the stability of what we currently have in CyanogenMod 12.1, with the performance somewhere between 12.1 and 11, and the "feature set" of a still-WIP system. But that's to be expected from an early Nightly, of course.

I'll update this post if I find anything else that's broken, though I'm not expecting anything major at all, from what I've seen so far.
[Motorola Droid 4] Cyber-Logic:
I did that... but I get com.android.phone has stopped after rebooting. Even trebuchet won't work. I installed CM 13 and then flashed Gapps.
[Motorola Droid 4] joefuf:
So when I first upgraded to this phone from the Droid 3, I went through the typical assimilation of keyboard evolution, and I decided not to adapt. I had no use for the Caps Lock key and I missed the ALT key, so I added them back by fiddling with some files.

I spent my morning making a .zip of the keyboard for CM13 Android Marshmallow. Everything works the same as with CM11, which is where I started this project.

For some reason, the emoji keyboard pops out when you hit what's labeled the Shift key, but what I changed to the ALT key. Not a terrible nuisance, but maybe someone knows a solution. It's a great layout, especially the reintroduction of the ALT key, which can be clicked and combined with backspace to delete a whole line, good for those late night texts you should really think twice about before sending, or normal days.

Extra add ons include the following, courtesy of [MENTION=4200167]3diord[/MENTION]:

Enjoy.
[Motorola Droid 4] Jishkah:
I don't know if this is related, but while I was messing with the phone's settings, I noticed in the "Advanced" section of the AOSP Software Keyboard settings that there's an option to use the phone's physical ALT/SYM (not sure which) key as a key to pop up the Emoji window, and it was enabled by default. Could be what's causing the issue.

I'm also not sure why it's in the software keyboard settings instead of the hardware keyboard settings, but *shrugs*. Try disabling the option; see if that fixes the issue.
[Motorola Droid 4] joefuf:
As Clay Davis would say, "Shiiiiiiiiiiiiiit."

Well done man. That fixed that ALT and Emoji issue. Here's to being curious.

Now I guess it's worth mentioning that the digital keyboard does pop up on me when I slide out the physical keyboard. Does that happen to anybody else? Any way to disable that?
[Motorola Droid 4] stargo:
Hi,

Hmm, then upgrading is broken again, it seems :(

I'll try to look at it on the weekend, I assume it is something in CM base which is responsible for that.

It's not doing that for me. Try toggline Settings -> Language & input -> Current keyboard -> Hardware (Show input method).

Cheers,

Michael
[Motorola Droid 4] KusioST:
If I use this trick I will be able to connect to the WiFi network which I save before? I have this same problem because I use 3 different WiFi network and always when I change one to another I must enter a password :/.
[Motorola Droid 4] lucize:
I tried an update fron cm11 ->12.1->13 and it was the same, the error would stop but no sim card detected. unfortunately is not working with dirty update

Regards
[Motorola Droid 4] joefuf:
Looks like that might have done the trick, turning off the Show Input Method.

Has everyone been having okay battery life? I'm not sure if it's just my phone, being on Wifi the whole time (I haven't activated 4G/LTE on this phone yet, still using CM11 on my daily driver), or or maybe just an old battery.
[Motorola Droid 4] Cyber-Logic:
Yeah, [MENTION=3457922]stargo[/MENTION] says upgrading might be broken in CM13 and it's something in CM base which is responsible for that. He's looking into it, don't worry. :)

I currently have CM 12.1 installed in Stock ROM Slot and CM13 in Slot 1. I'm thinking of migrating by backing up important app data using Titanium Backup from CM12.1 and then restoring that on CM13.
[Motorola Droid 4] stargo:
Hi,

Unexpected things might happen ;)

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

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

https://github.com/TheMuppets/propr...mmit/2726b00f295736b9f832d37aac12e927f673bf51

Cheers,

Michael
[Motorola Droid 4] daniel_m:
Hm, according to Marcel, XPrivacy works on Marshmallow (CM13) (http://xdaforums.com/showpost.php?p=64957257&postcount=16802).

Looks like I will have to spend some time on finding out more next weekend :D Maybe I can report back something positive here :)
[Motorola Droid 4] Careless_:
Seeking clarification on this bit of info from the first post:

I was looking for a post in this thread around December 25th, but didn't see anything of note. :cyclops:
[Motorola Droid 4] Septfox:
Saw them last night. Flashed this morning.

I have another phone here, and there's a consistent 10 degree difference between them (no idea which is actually correct, the other is pretty old), but aside from that everything seems to be working just fine.

Thank you for revisiting it. I know it's probably a minor/unneeded thing to most people, but it's nice to have a fully-working toolkit :)

It's not really a "trick", connecting manually from Wifi Settings always works properly in my experience.

I guess if you want to call it something, it's a "shortcut" to get to the settings screen slightly faster...but to do that, you would be better served by long-pressing on the quicksettings icon.

And looking back through the thread, it seems other people have confirmed it. So I guess we do have Xprivacy after all.

Don't know why I didn't look into it more beyond the front page (which still quite clearly states that it's up to 5.1.1).

Previously, storage didn't mount quite right, iirc internal user eMMC was inaccessible and all that was mounted at boot was the external SD card.

Anyone upgrading from nightlies of that period needed to go delete that file (the built-in File Manager in root mode is adequate) and reboot, resetting storage preferences to baked-in defaults and having MM mount internal storage as "MOT".

Then, the phone will ask you (again) whether you want to render your SD card useless in other devices or keep using it as an SD card should be used ("Adoption as Internal Storage" vs "Portable Storage").

Assuming the latter, it'll then mount the SD card as Lollipop and earlier did, and you'll have almost exactly the same storage arrangement as Lollipop. Presumably, you can then turn around and apply joojoobee's SDswap, if that's your thing.

Since stargo fixed it, current nightlies are perfectly fine from the outset, no mucking about needed on our end.
[Motorola Droid 4] daniel_m:
Marcel changed his thread and GitHub entry and mentions Marshmallow now. As far as I remember, XPrivacy is not guaranteed to work on any non-AOSP ROM like CM13. Hopefully, I will find out in a few days :o
[Motorola Droid 4] Careless_:
Thank you for the very clear and informative answer.

Perhaps a note of this on the main post would be ideal (on the same line, maybe "nightlies need no manual file system changes")
[Motorola Droid 4] doener:
Im thinking about giving the CM13 nightlies again a try. Currently im running CM11-11-29150901-Snapshot, which is not really stable (random reboots) but in compare to CM12.1 I don't get any ANRs, and the UI stays responding to input. Not as in CM12.1 where the UI startet to hang from time to time for minutes.

How is it with the current CM13?

Apps Crashing ANRs, Here Maps?

Other annoying things?

Is the GSM patch also not needed in the CM nightlys?
[Motorola Droid 4] stargo:
Hi,

I've changed it a bit.

Yes, the GSM patch is no longer needed at all. Changed that in the first post, too.

Cheers,

Michael
[Motorola Droid 4] mo0n_sniper:
Could the ramdisk from Mentor to have the ROM in the additional partitions in SafeStrap be included in the official links?

Link here
[Motorola Droid 4] Septfox:
It's quick and mostly stable. I've only had one hot-reboot happen, and I think that's because I forgot to switch hotplugging back off.

ANRs happen every now and then, but for the most part it's been alright. Keeping more memory free (tweaked minfree and/or process # limits) avoids ANRs for the most part; they seem to usually happen when the foreground app is trying to do something and the phone decides at that moment to try and clear something big from memory.

There're still long pauses here and there (with a "frozen" UI to go with it), but overall there's less waiting around for things to happen than in Lollipop.

The only annoying thing I can think of at the moment is the wifi quicksetting bug, but devs are aware of it and it's only a matter of time before it gets sorted.

Definitely worth making a slot and giving it a try. I would say we're still not at KK levels of performance yet, but Marshmallow was a big step forward, and stargo is still tirelessly working on optimizing things.

--

Speaking of performance, though...has anyone noticed reduced graphics performance lately? I'm going to load up a backup from a few nightlies back tonight to make sure, but it seems like 3D performance is noticeably choppier. Yet, benchmarks are around the same. It's a little odd, and I suppose it might be the specific apps I'm running.
[Motorola Droid 4] Bobcus Leper:
I've had the strange 3D issues too. Ever since I installed the 01/26/2016 nightly, the 3D performance seemed to take a significant hit.
[Motorola Droid 4] d.casper.b:
[MENTION=3179801]Careless_[/MENTION]

I'm still on the build of the 24th and now I guess I'll stay on it longer.

Regarding the weird naming of your storage... I've seen it like this since stargo's first CM13 build for my phone.

What I do for rom-slot sizes is: /system: 800mb (so that it's as close as possible to the stock /system partition - well that of the XT910).

/data: 2500mb or more depending on app space requirements.

/cache: leave it at 10mb - anything more is a waste of space and wool not be utilised.

Sent from my Motorola RAZR Maxx (XT910)
[Motorola Droid 4] Careless_:
Our phone doesn't make use of the Cache partition?

The only problem is that I can't access any of the data on the sd card. it won't let me use the File Manager and I can't use any apps that need to search the sdcard1 partition to restore any of my sms data that's backed up.

UPDATE: Managed to get access to my data. I don't know what I did, but it's working now. Would be nice if the SD drives didnt have weird names.