yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Original Android Development] Gundabolu SC:
Hey... [MENTION=2228410]Skrilax_CZ[/MENTION]... Could you please consider rolling back the experimental xt1250 compatibility changes? I mean not like it works for them, it atleast used to boot before.... And i have an xt1254 with unlocked bootloader and after the experimental stuff none of the Custom ROMs boot in mine either... I know i am just one person but i ask you if you can do it because i see that it does not work for xt1250 as well.! Thanksssss... :)
[Moto Maxx Original Android Development] fgl27:
Can you make a print screen? of a folder on the root of the device not in system folder above it.

print the content of fsg folder and post it here.
[Moto Maxx Original Android Development] Gundabolu SC:
Okey I am not sure how okay it would be to do that cuz of few reasons...

Anyways it has files for Verizon att sprint tmo n even some shamu stuff! :)
[Moto Maxx Original Android Development] fgl27:
I need the print screen really not joking. The support today is depending in the files on that folder. so I wanna to understand how ever-ting works, I only have a XT1225 and believe OP too, so to support other models is need support of users.
[Moto Maxx Original Android Development] Fulbring:
Any updates on CM13? Is it soon with an ETA or still to be determined?
[Moto Maxx Original Android Development] fgl27:
[MENTION=2228410]Skrilax_CZ[/MENTION]

Can you give your input on this?

I try to implement a init.c to support all models and not use that moto_config.sh, I use as base victara and made this:

init folder

I still need ro.boot.cid for xt1250 to finish it, maybe you or some user can give me that so i can test the script.

One tings i don't understand is, way use CDMA for XT1250?

[MENTION=5429992]Gundabolu SC[/MENTION] device didn't boot because the CDMA verizon config that the .sh script was setting on his device, I made a test kernel using default GSM retla setting and the device is booting OK, I know his device is a special case...

But that is not the way XT1250 is not booting, all XT1250 are CDMA?

And don't you think this init.c script is a better to support all devices and carrier?

If you wanna use this as base to make a yours do and let me know.

I appreciate the input, thanks.
[Moto Maxx Original Android Development] asuperpig:
really great
[Moto Maxx Original Android Development] mirdones:
Why today nightly has the following tag cm-12.1-20151117-SNAPSHOT-YOG7DAO1K3-quark.zip ?
[Moto Maxx Original Android Development] LuanGuima14:
Hava a Bug in Snapshot!!

In the last build the sound is not working, the gestures not working, this in Moto Maxx XT-1225:eek:
[Moto Maxx Original Android Development] maximuscesar:
As the name implies, it's not a nightly, it is probably just a CM13 snapshot for the more curious to see how it is going. The actual last nightly is the 20151114 one.
[Moto Maxx Original Android Development] junior_ilha:
It is not the marshmallow . that snapshot isn't working The sound, lets wait for The next One.
[Moto Maxx Original Android Development] Skrilax_CZ:
What the hell? That should be the stable build.
[Moto Maxx Original Android Development] maximuscesar:
They are talking about that cm-12.1-20151117-SNAPSHOT-YOG7DAO1K3-quark.zip thing. BTW, what was that? So the 20151120 is the stable build huh? Very cool.
[Moto Maxx Original Android Development] Skrilax_CZ:
Yes, but "cm-12.1-20151117-SNAPSHOT-YOG7DAO1K3-quark.zip" is supposed to be the stable build. Very strange as it looks like it was built using wrong kernel for some reason, yet the git branch is fine.
[Moto Maxx Original Android Development] ChazzMatt:
So 19/20 are from stable build?
[Moto Maxx Original Android Development] fedecape:
The snapshot is the stable build? I'm on 11/02. Can I flash it on top of my nightly?
[Moto Maxx Original Android Development] Gambler_BE:
No. Read the previous page. The way I understand it, the snapshot was supposed to be stable, but something went wrong. Apparently the old kernel got integrated thus breaking some things. So until Skrilax posts an update, I wouldn't flash the snapshot.
[Moto Maxx Original Android Development] Fulbring:
Can someone explain the difference between Snapshot, Stable and Nightly builds? I know what Nightly's are but I want to know it in this context.
[Moto Maxx Original Android Development] RoPipo:
I'm on the 20151121 nightly and the Bluetooth issue still are there. I don't know if we will have solved sometime :(
[Moto Maxx Original Android Development] ChazzMatt:
I'm on that nightly too and Bluetooth works fine through my Pioneer car stereo and my ICON Bluetooth headset.

I took a 2 day trip to another state (4 hours away), streamed Pandora all the way through my car stereo as well as made/received phone calls through my car stereo. Even yesterday, I talked to my wife and my sister via Bluetooth through my car stereo system. I heard them, they heard me.

I've never had the Bluetooth problems others have complained about. It's a mystery.
[Moto Maxx Original Android Development] mirdones:
I am also having a problem with my car bluetooth where the audio skips for about a second and then comes back.

It happens about one time each five minutes.

It began hapenning a few nightlies ago. About one month.

When I am on my car, I am streaming music by Spotify, using Waze, using Torque Pro and using Radardroid Pro.

It does not happen with my bluetooth home speaker streaming music by Spotify.
[Moto Maxx Original Android Development] RoPipo:
when I'm using the phone on my car, works fine, but with my jabra Rox headphones not. And I'm not the only one, this is so strange​
[Moto Maxx Original Android Development] lko_leader:
Per CM9 / CM10 era:

Nightly -> Unstable, bugful build, released every day (or night, timezone depending);

Snapshot -> Monthly builds, tended to be a lot more polished than nightlys, but still had a few rough edges. There were, at least back on CM10's days, a few spread out over development time.

Stable -> Most stable builds available, they tended to mark the end of development on a given version (exemple: CM11 Stable is the last CM11 ROM released and means the team will now focus on the lastest version).

Nowdays, nightlys are stable enough to be used as daily drivers, so snapshots and milestones (the middle ground between snapshot and stable) have sort of lost it use. Stable still means end of dev, though...
[Moto Maxx Original Android Development] Skrilax_CZ:
From late CM10.2, generally, after the initial bringup is done, nightlies are usually stable for daily drivers (you may see a bug in here an there), which snapshot should not have. Possible instabilities after bigger changes (or rebases) are made, but these are sorted soon.

Also for the bluetooth sound not playing issues, I'll need a logcat for those, since it's possibly a missing configuration for some of them.
[Moto Maxx Original Android Development] mrkhigh:
Turbo just officially had unlock released. Will the nightlies play nice with GSM?
[Moto Maxx Original Android Development] Skrilax_CZ:
I examined support for XT1250/XT1254, looks like the reason why they don't boot is that init gets stuck at the script (possibly due to a bug in init), thus I'll use the traditional approach and do it in init.

Only the right way is to use "ro.boot.radio" and then "ro.boot.carrier" (to determine whether "reteu" or others).

[MENTION=5429992]Gundabolu SC[/MENTION] Can you do in adb "getprop ro.boot.radio" and "getprop ro.boot.carrier" and post the output?
[Moto Maxx Original Android Development] Gundabolu SC:
getprop ro.boot.radio - 0x4

getprop ro.boot.carrier - vzw
[Moto Maxx Original Android Development] fgl27:
that is the way I wanna use cid the only ting different on those especial device is the cid.

his cid is not the same as regular XT1254.

for me removing device support from the kernel is the best way.

Make a universal kernel that boot on any device, and a init script to support device on the ROM. If that init don't set the right value for Radio for some device the user can just delete or edit the script, and if deleted edit build.prop. Or give adb commands so we can understand way the device is not working.

If the init srcipt to support devices is a simple script that the user can just edit is better, but if is something that need to be compile the user will have to delete and edit build.prop.

To ensure that script is started, we add a (on property:sys.boot_completed=1, or something like this) on some init file of the kernel.
[Moto Maxx Original Android Development] ChazzMatt:
We have two November 27 nighties. Any difference? The 2nd one has no log change description.

http://www.cmxlog.com/12.1/quark/
[Moto Maxx Original Android Development] Skrilax_CZ:
XT1254 should have ro.boot.radio 0x2 instead of 0x4. That's the typical value for Verizon.
[Moto Maxx Original Android Development] Shooting Star Max:
Will it be easier to have CM13 for Quark once Victara and Shamu get more stable releases? Is it better to wait until then?
[Moto Maxx Original Android Development] fgl27:
this is the only reference I have.

https://census.tsyrklevich.net/devices/372/system_properties

in this is ro.boot.radio	0x4

Are you confusing with this?

ro.boot.cid	0x2
[Moto Maxx Original Android Development] Skrilax_CZ:
You're correct. They really share the same ro.boot.radio, both 0x4, interesting, on msm8960 we used ro.boot.radio to determine the actual model. Therefore let's use ro.boot.cid then, but differently. Interestingly ro.boot.carrier is empty for XT1254 but set to "vzw" for XT1250 (just doesn't make sense unless was overriden).

You can use "fastboot oem config fsg-id xxx" to set value which will be picked up, because it is empty originally. This can be used as an override.

XT1254 thus has ro.boot.cid = 0x2 and is sets default fsg-id "verizon"

XT1225 thus has ro.boot.cid= 0xC => then with ro.boot.carrier "reteu" carrier set it for fsg-id => emea, otherwise fsg-id => singlela, no need to differentiate any lower to individual carriers

Then based on fsg-id:

emea -> XT1225 as Moto Turbo

singlela -> XT1225 as Moto MAXX

lra -> XT1250 as Moto MAXX

lra_gsm -> XT1250 as Moto MAXX, but set for GSM

verizon -> XT1254 as Droid TURBO

verizon_gsm -> XT1254 as Droid TURBO, but set for GSM

XT1250 still needs to clarify, [MENTION=5429992]Gundabolu SC[/MENTION] , what is your "getprop ro.boot.cid" and "getprop ro.boot.fsg-id"?
[Moto Maxx Original Android Development] Skrilax_CZ:
Actually CM13 nightlies already started rolling, but didn't have time yet to look on it. So I guess during December I'll bring it up.
[Moto Maxx Original Android Development] ChazzMatt:
Over in the Droid Turbo section, computerfreek274 says he's already started working on porting CM13 for that Quark.

Whatever he does has to be posted to CM repository or whatever, right?
[Moto Maxx Original Android Development] Skrilax_CZ:
Correct.

btw. Very little devices have CM13 nightlies right now (Nexus 6 is not one of them), so it might still not be fully ready.
[Moto Maxx Original Android Development] Skrilax_CZ:
I've merged a patch to fix the actual setup for XT1254 (XT1250 atm. is only manual). It will automatically detect which radio to use from ro.boot.* properties, however if somebody crossflashed (i.e. flashed Moto Turbo radio FW to Moto MAXX), it won't be automatically picked up and you'll have to do the "fastboot oem config fsg-id ..." part (see 1st post). Otherwise you'll have no radio.

XT1254 should be automatically picked up. XT1250 is only manual - see crossflashing.
[Moto Maxx Original Android Development] fgl27:
[MENTION=2228410]Skrilax_CZ[/MENTION]

Nice work.

The last time i test CR on RR it didn't work just a error and empty file is created, when try to rec, implemented the same way, maybe is a RR problem.

[MENTION=5429992]Gundabolu SC[/MENTION] cid is 0xDEAD is really a one of a kind device.

this works perfectly for quark...

https://github.com/bhb27/android_de...mmit/92f43958c34ae8e05e292ad685b9d7c5bea39f2a

@ all

XT1254 and XT1250 need to report if the changes made effect.
[Moto Maxx Original Android Development] Gundabolu SC:
Hahaha... Yeah its definitely one of a kind... I guess it's a Motorola Prototype cuz its Bootloader says Engineering... And the Unlock Status code is 2... Instead of 3 when u unlock using Motorola or Sunshine... :)
[Moto Maxx Original Android Development] mbarry55:
I don't see an 11/28 nightly on the cyanogen download page. Goes up to 11/27. I'm ready to flash it and see how it works but I can't find it lol
[Moto Maxx Original Android Development] koftheworld:
It won't run till tonight most likely. You can always make a pull yourself though.
[Moto Maxx Original Android Development] fgl27:
I made a test kernel included the changes...

http://xdaforums.com/moto-maxx/development/kernel-bhb27-kernel-t3207526/page13#post64048147
[Moto Maxx Original Android Development] brennam7:
Getting an error on boot and while in the OS that storage space is running low. XT1254, did some reading online and found a bunch of references to the Samsung GS3 and having to delete the logs in /data/logs, but that folder doesn't exist. Followed me to RR rom as well. Any ideas?
[Moto Maxx Original Android Development] ChazzMatt:
In TWRP you wiped everything except for storage before flashing?
[Moto Maxx Original Android Development] brennam7:
Yessir, even went as far as wiping internal storage entirely and then sending the ROM to the phone and then flashing it. I did notice that the file system for /data was f2fs. Wouldn't concern me except when i went to flash my twrp backup, it gave me a warning saying that the /data partition was backed up on ext4 and might not work. Can someone with xt1254 check and see that that is supposed to be? Pretty sure it should be ext4, but not completely sure
[Moto Maxx Original Android Development] ChazzMatt:
hmmmm... Try re-flashing TWRP. THEN re-download the ROM to your phone's storage. Then wipe everything except for storage and re-flash the ROM?

Let us know how it goes, please.
[Moto Maxx Original Android Development] fgl27:
[MENTION=4352824]brennam7[/MENTION]

BTW there is a help about partitions on TWRP thread 2#post...
[Moto Maxx Original Android Development] brennam7:
Ended up being the /data partition. Got switched to fs2s somehow. Got it going g now though. Cm12 is running smooth as hell. Thanks for the work on the kernel!
[Moto Maxx Original Android Development] mrkhigh:
No 28th or 29th nightly?
[Moto Maxx Original Android Development] richii0207:
Jenkins showed that 28 failed and 29 was built a little over an hour ago. Should be up now.
[Moto Maxx Original Android Development] mrkhigh:
Just installed cm12.1 on my droid turbo latest nightly and I used the stock kernel. So far so good. Thanks [MENTION=2228410]Skrilax_CZ[/MENTION]
[Moto Maxx Original Android Development] AndroidFanMan:
Minor annoyance here. I would post in the Q&A, but I can't find a thread for it for some reason.

1) USB identifier still shows XT1225 on XT1254 variants

2) Settings>About>Device Model shows "Moto MAXX" on Droid Turbo variants

Neither item really matters, but it seems like something we may want to keep separated. Clean flashed 11/29 Nightly and used Open GAPPS pico.
[Moto Maxx Original Android Development] mrkhigh:
Mine shows droid turbo
[Moto Maxx Original Android Development] Rixanu:
I asked this over in the Droid Turbo forums and no one seemed to be having the issues listed below. Thought I'd ask in the main thread as well- just in case. Is anyone else experiencing these issues or know how to fix them? This is on the Droid Turbo with the 11/29 nightly and default kernel. I tried a fresh install and the issues still persisted.

The recents menu is behaving very strangely. Once the app has shrunken down, the thumbnail abruptly jumps to show the lower half of the app instead of staying in the same position that was shown as the app was shrinking. I've also noticed that entering the recents menu from a game will cause the app not to shrink properly. The shrinking animation will constantly show the entire game screen, then suddenly snap to show the lower half of the app once the animation finishes.

Media audio will frequently pop as it starts playing, then it will work fine. I thought this might be because of AudioFX, but turning it off hasn't helped. I've noticed that this has been an issue with every ROM I've tried for this phone aside from the stock one.
[Moto Maxx Original Android Development] ChazzMatt:
Not an issue.
[Moto Maxx Original Android Development] mrkhigh:
I am not experiencing either issue.

I factory reset, installed 11/29 cm12.1 and opengapps, then cleared cache.

So far it seems to work well.
[Moto Maxx Original Android Development] AndroidFanMan:
Any thoughts? I've formatted /system in fastboot and reflashed recovery just to cover all my bases. Did a full wipe of each partition in TWRP, but a fresh install still shows XT1225 when plugging into a Windows-based PC and shows Moto MAXX on the "About" screen.

EDIT:

From TWRP using ADB Shell

ro.boot.hardware.sku = XT1254

ro.product.model = quark

ro.product.device = quark

ro.product.name = omni_quark

ADB Shell from booted device 11/29 nightly

ro.boot.hardware.sku = XT1254

ro.product.model = Moto MAXX

ro.product.device = quark_umts

ro.product.name = cm_quark
[Moto Maxx Original Android Development] mrkhigh:
What kernel are you using?
[Moto Maxx Original Android Development] AndroidFanMan:
Stock

3.10.93-perf-gaa09ab4

clyde@cyanogenmod #1

Sun Nov 29 10:25:45 PST 2015

EDIT: Also tried restoring my TWRP backup of stock ROM and the identifier was correct. Did a regular wipe and flashed CM 11/29 nightly. Showing as Moto MAXX again and XT1225 on PC.
[Moto Maxx Original Android Development] ganggreen30:
Does anyone have link to resurrection rom for the turbo
[Moto Maxx Original Android Development] Skrilax_CZ:
What is your "ro.boot.fsg-id", "ro.fsg-id", "ro.boot.cid" and "ro.boot.carrier"? You can override for now with "fastboot oem config fsg-id verizon" to set it to verizon.
[Moto Maxx Original Android Development] AndroidFanMan:
You asking those questions just made me think of something... the device was flashed without a SIM card present. I'm guessing that has something to do with it. As soon as I post this, I'm going to see what happens if I flash again with my SIM installed (SIM was in my 6P).

ro.boot.fsg-id = blank

ro.fsg-id = singlela

ro.boot.cid = 0x0

ro.boot.carrier = blank

EDIT: Having the SIM in during flashing did not change anything. Using the fastboot command fixed it, however. Let me know if you need anything else from getprop or logs.

After making the fastboot change, here are the getprop results:

ro.boot.fsg-id = verizon

ro.fsg-id = verizon

ro.boot.cid = 0x0

ro.boot.carrier = blank

Was also getting "cellular network not available" at first. Had to *#*#4636#*#* to change network mode to LTE / CDMA auto from LTE/GSM/CDMA auto. I was able to connect after that.

EDIT 2: Still no cellular connectivity although status bar shows LTE. Calls are unsuccessful. Seems to stay connected to the network for a minute or so then disconnect.
[Moto Maxx Original Android Development] Skrilax_CZ:
Do you have a eng. phone (seeing cid = 0)? If so, then you must set it manually as mentioned before: "fastboot oem config fsg-id verizon). That should do the trick.

If the code that determines what phone do you have cannot resolve it (doesn't mean it can't be improved), it will default to Latin America XT1225 (ro.fsg-id = singlela).
[Moto Maxx Original Android Development] AndroidFanMan:
Unless Verizon somehow sent me an eng / dev phone when I requested a replacement, then I don't believe so. First one was direct from their store and the replacement came from them under a warranty replacement.

I checked again and ro.boot.cid is still 0x0. It's almost 2am EST. Shoot me a PM with what else you'd like me to try and I can try it in the morning.
[Moto Maxx Original Android Development] ChazzMatt:
it's in the Development Section of this forum. Very easy to find. This is the Original Development section.
[Moto Maxx Original Android Development] uveequis:
Ambient Display

I can not get Ambient Display to work at all. I allowed all notifications on lockscreen and I tried turning it off and on with no success. I factory wiped and re-flashed the ROM with the same result, also tried Ressurrection Remix but got the same problem. I tried a couple of apps from the Google Play Store which have the same functionality but did not work neither.

Any idea on how to fix this? This is a feature I would really miss.

I apologize if this is not the proper place to post my query.
[Moto Maxx Original Android Development] mlw4428:
I didn't read through the 50some pages of text, but will there be voLTE support eventually? Data while on a call is rather important to me. Otherwise, this looks excellent!
[Moto Maxx Original Android Development] ChazzMatt:
see post below.
[Moto Maxx Original Android Development] ChazzMatt:
These are the settings that affect Ambient Display in CM12.1. Check your settings on these THREE pages:

__________

__________
[Moto Maxx Original Android Development] uveequis:
Thanks. I checked those but nothing changes. I realised after reset factory it works well before I restore DATA from TWRP backup. I thought that only restored apps and media but it must change something else, what am I missing?

I will back up the apps using a third software and begin from scratch from factory reset I guess that will solve the problem.
[Moto Maxx Original Android Development] Gundabolu SC:
You shouldn't restore DATA from TWRP backups to a different ROM! Best way is to use Titanium Backup n backup all user apps and after flashing the new rom just restore them back! :)
[Moto Maxx Original Android Development] duowing:
Are you setting up your phone to have a Password/PIN/Other form of lock? I had issues in the past while playing around and realized that if you have basically any security settings other than Swipe/None then you won't see the Ambient Display.
[Moto Maxx Original Android Development] uveequis:
I would not like my device to be without any lock. Anyway I tried, nothing changed.

I thought that was common practice to keep the apps. I will use Titanium to back up my apps then, and start from scratch, thank you.
[Moto Maxx Original Android Development] ChazzMatt:
NOT TRUE. You are doing something wrong. My wife and I have Pattern Lock Secure screen and we still have Ambient Display. That 3rd screenshot I posted is above is the key to that. You have to allow notifications even on Locked Display.

---------- Post added at 03:15 PM ---------- Previous post was at 03:15 PM ----------

You can have secure lock and have Ambient Display. Do NOT listen to anyone who says you cannot.
[Moto Maxx Original Android Development] IonAphis:
Quick question:

I have tried all CM-based ROMs and always get the same issue with LTE/4G signal. While on the Stock ROM, my Moto Maxx will default to 4G wherever available, it seems CM ROMs avoid LTE whenever it can. I usually have to go into the *#*#4636#*#* menu, switch to LTE only, watch the signal change from H+ to LTE and switch back to LTE/GSM(PRL) and LTE signal will stick, but eventually it falls back.. I have tried this with Mokee, CM12.1, RR and all of them have the same behavior. I have installed CM12.1 and tried using it without modification and tried flashing my stock radio after installing the custom ROM. I have tried changing APN info and even copied exactly all the info from stock ROM and manually entered the parameters in the custom ROM, have tried changing "prefer LTE" in settings and I still get this situation where it seems the ROM avoids LTE like the plague. Is this how Cyanogen-based ROMs are coded, or is there something that can be done to change this behavior?

Thanks
[Moto Maxx Original Android Development] mrkhigh:
I haven't seen this issue, and it is not how cm acts.

My turbo on cm12.1 is using lte right now.
[Moto Maxx Original Android Development] AndroidFanMan:
What's your ro.boot.cid? I'm betting 0x2.

There are numerous users reporting this issue, but mostly on the DT, not the Moto MAXX, like the previous post mentioned. I believe the dev is working to resolve these issues.